RailCall Builders Contest — $1,500 Winner + Top 10 Suggested Vendor Bench - RailCall is a founder-seeded local automation company looking for serious developers, QA testers, and automation builders. Build a real RailCall workflow, submit a signed receipt,

Pending

Prize:

$1,500 USD

Entries Received:

28 days, 20 hours to award

RailCall Builders Contest $1,500 winner · Top 10 runner-ups selected for suggested vendor bench Build something real. Prove it with a receipt. Help shape a local-first automation product before enterprise rollout. RailCall is a local-first automation platform built for governed workflows that run on the user’s own machine, not inside another rented automation cloud. It turns plain English into useful flows, keeps sensitive work local by default, uses dry-run governance, and produces signed receipts that can be verified offline. This is not a generic “submit an idea” contest. We want builders who will actually install RailCall, use it, test it, break it, document what works, and show us what needs to change before broader enterprise deployment. Prize and opportunity One winning entry receives $1,500. The top 10 runner-ups will be selected as RailCall suggested vendors for future paid QA, workflow-building, implementation, and client-support opportunities. Suggested vendor selection is not a guaranteed contract, employment offer, equity grant, or exclusive relationship. It means you are selected into our first trusted outside builder bench as paid opportunities become available and fit your skills. Founder background RailCall is founder-seeded, not VC-backed. The founder has previously raised approximately $75 million and completed a $60 million exit to private equity. RailCall is being built without the venture treadmill: no VC board, no growth-at-all-costs mandate, no plan to turn local automation into another rent-extraction SaaS trap. The company is founder-backed with a $10 million founder-seeded commitment, and enterprise clients are already waiting for qualified implementation and testing capacity as the product clears launch QA. We are using this contest to identify the builders, testers, and implementation partners who should be in that first vendor bench. What RailCall is RailCall is local-first automation. Instead of forcing users to send private files, logs, credentials, customer records, and workflow logic into a cloud automation platform, RailCall runs useful flows on the user’s own machine. The operating idea is simple: Agents draft. You approve. Receipts prove. RailCall is built around: - local execution - dry-run by default - human approval for sensitive actions - signed receipts - offline receipt verification - honest usage-based flow accounting - user-owned data, keys, and logs What you can submit You can enter through one or more of these categories. 1. Best Program Build the strongest working RailCall workflow or small program. It should be useful, reproducible, and documented clearly enough that we can understand what you built and why it matters. Examples: - local invoice triage - file routing - internal reporting - CSV cleanup - database sync - local QA workflow - compliance/audit checklist - developer workflow - customer follow-up workflow - operations workflow 2. Best Use Case Show us the most valuable real-world use case. We care about boring, useful workflows as much as impressive ones. A local workflow that saves time every week is better than a flashy demo nobody would run twice. Explain: - what problem it solves - who would use it - what cloud/manual process it replaces - why it should run locally - what data stays on the user’s machine - what the business value is 3. Best Feedback Give us the sharpest product audit. We want honest, reproducible feedback, not flattery. Tell us: - what broke - what confused you - what was slow - what felt dishonest or overclaimed - where the install or first-run experience failed - what the docs did not explain - what would stop a real customer from adopting it Strong feedback includes exact reproduction steps, expected behavior, actual behavior, screenshots or logs where useful, and severity. 4. Material Change Find something that causes us to ship a real fix or improvement. If your finding changes the product, that is one of the strongest possible entries. We are especially interested in issues involving: - installation - first workflow creation - signed receipts - local execution - dry-run behavior - verification - dashboard usage meter - security language - confusing copy - product claims that do not match reality Entry requirements To qualify for judging, you must actually use RailCall. Your submission must include: 1. Your RailCall account email Create a free account at: https://railcall.ai No card is required. 2. Proof that you installed and used RailCall Install RailCall: curl -fsSL https://railcall.ai/install.sh | bash Then open RailCall Studio and build at least one real workflow in plain English. 3. Your signed receipt JSON RailCall produces signed receipts. Your receipt is your proof that you actually used the product. Every valid entry must include the receipt JSON from a workflow built on your own install. We verify receipts offline using: railcall verify <receipt.json> If the receipt does not verify, the entry does not count. 4. Your actual submission Submit one of the following: - a workflow/program write-up - a real use-case write-up - a numbered feedback/audit report - a bug report with exact reproduction steps - a material improvement proposal backed by product evidence 5. One paragraph explaining RailCall’s mission in your own words This matters. We are looking for people who understand the product, not people submitting generic AI automation ideas. If you cannot explain RailCall after using it, you probably have not tested it deeply enough. Suggested submission format Please structure your entry like this: 1. Name / Freelancer username 2. RailCall account email 3. Category: - Best Program - Best Use Case - Best Feedback - Material Change 4. Receipt JSON attached 5. What you built or found 6. Steps to reproduce 7. Expected result 8. Actual result 9. Screenshots/logs if helpful 10. Why this matters 11. What cloud/manual workflow this could replace 12. Why local-first matters here 13. One paragraph: RailCall’s mission in your own words How we judge We will score based on: Real usage Did you actually install and use RailCall? Does your receipt verify? Usefulness Would someone actually run this workflow again? Reproducibility Can we follow your steps and get the same result? Clarity Is your write-up specific, understandable, and technically useful? Feedback quality If you report an issue, is it precise, reproducible, and prioritized? Material impact Did your submission cause us to change the product? Local-first advantage Does your workflow show why running automation on the user’s own machine matters? Examples include local files, local databases, internal logs, local development tools, private business data, BYOK workflows, or workflows that should not be sent to a cloud automation provider. What we are not looking for Do not submit generic AI ideas without using the product. Do not submit fake usage. Do not submit a wrapper around a public API and call it a workflow. Do not include private keys, passwords, secrets, customer data, or confidential files in your submission. Do not run destructive automations. Do not attempt live sends against systems you do not own. Do not attack systems you do not control. Do not try to bypass the product’s approval rails. If you find a governance issue, report it safely as feedback. Prize One winner receives $1,500. Top 10 runner-ups are selected for the RailCall suggested vendor bench. The winner and selected runner-ups may be invited into future paid testing, workflow-building, QA, implementation, and enterprise-support work as RailCall grows. All prize payments and contest communication will follow Freelancer’s platform rules. Important note on future work Suggested vendor selection means you are on our shortlist for future paid work. It does not guarantee a specific contract, amount of work, employment, equity, exclusivity, or a continuing relationship. Future work, if any, will be scoped and paid separately. Why this matters Most automation tools became cloud rent. RailCall is different. We are building useful automation that runs where the work already lives: on the user’s machine. That means sensitive files, logs, keys, and business logic do not have to be shipped into another cloud platform just to automate basic work. This contest is how we find the first outside builders who understand that mission and can help us test, harden, and deploy RailCall for real customers. Start here 1. Create a free account: https://railcall.ai 2. Install: curl -fsSL https://railcall.ai/install.sh | bash 3. Build a workflow. 4. Save your receipt JSON. 5. Submit your receipt and write-up here.

Featured

Guaranteed

Top Contest

Skills Required

API Testing

JavaScript

Python

Software Testing

Technical Writing

Test Automation

Testing / QA

Usability Testing

Website Testing

Workflow Consulting

Accepted File Formats

gif, jpeg, jpg, png

Clarification Board
No spam, self-promotion or advertisement is permitted.

Amit -.

@amits673

24 hours ago

Dear Client, As you said you will also select top 10 runner ups. I wish I will be in top 10 suggested vendor bench. Kindly review my entry #64, I faced issue in generating receipts, otherwise everything is fine. With due Regards

Royan M.

@rtxid

1 day ago

#89 json files on the image

Ovik B.

@codeovik

1 day ago

This is totally a fake contest. I think all are planned from beginning and awarded to first entry.

Shahanshah C.

@shahanshahc9

2 days ago

please check my entry #92

Andrija R.

@ChocolateCookies

2 days ago

NEVER DOWNLOAD ANYTHING ONTO YOUR COMPUTER. THIS IS LIKELY A SCAM!!!

Amit -.

@amits673

2 days ago

#64....Please have a look. I genuinely wants to support this work. I have many things to try out using Railcall. Regards

Jay J.

@jayyx03

2 days ago

Hi Patrick, I've submitted my entry which contains a security and cryptographic audit of the station-v0.1 engine. I found four major vulnerabilities, including a Cyrillic homoglyph bypass in chat_guard, a signature nullification exploit in dual_control.py, a webhook bypass on the integration test path, and the python3 MS Store alias crash on the Windows installer. All verified with my signed Ed25519 execution receipt. Looking forward to your review! #48

Contest Holder

3 days ago

NEW + already logged [@ZahidBangash123]: sharp one - /api/chat has no session gate while /api/build + /api/wf_compose do, so chat is an ungated local path that can burn flows / use BYOK keys. Confirmed real - session-gating it next (same _require_session guard + CSRF as build/compose), and I'll confirm here the moment it ships. Your account-dropdown idea (group Theme + Sign out + remaining-flows status in one menu) is a clean UX call too - queued. Every fix is credited by name; keep the sharp, reproducible reports coming - this is exactly the depth we want.

Contest Holder

3 days ago

ROUND-6 SHIPPED + verified - re-run: curl -fsSL https://railcall.ai/install.sh | bash (fresh Studio + re-notarized app). - PACKAGING LEAK CLOSED [Sami]: the install no longer ships internal files (red-team corpora, internal specs, security-findings dumps, dev scripts, tests) - the download is runtime-only now, verified (server 404s on them, secret-scan clean, boots clean). - Receipts no longer overwrite [Sami]: build/UI/flow receipts each persist to a unique timestamped file under receipts/ - no run replaces a prior proof. - audit REJECTS non-CSV/system files like /etc/passwd instead of '0 PII' [Sami]; dashboard shows the auto-detected Ollama model [Sami]; build errors on a missing dataset path instead of silently sampling [Sami]; native Windows install.ps1 confirmed working [Juned]. - Sign-out IS present on the shipped Studio /v2 - if it looked missing, that was the old ui/ React source (doesn't ship); re-check the running /v2.

Muhammad Z.

@ZahidBangash123

3 days ago

Instead of inlining header actions, we should use a user/account dropdown for Theme and Sign out. This will reduce header clutter and group personal/session actions in a more standard place. If possible, also show remaining flows in that dropdown (e.g., 90/100) as a status item