Cut the cloud bill. Run on the compute you already own.
RailCall moves execution into your own secure environment and puts your organization’s idle machines to work — roughly 80% of that hardware does nothing while you pay cloud rent. Machine to machine, human-approved, signed, verifiable offline. Free forever — $0, unlimited machines.
TCP/IP connected computers so they could move packets — through someone else’s servers. RailCall connects machines that act on each other’s behalf, peer to peer, with no hub in the middle. Every link is a human-approved, signed handshake instead of a request to a stranger’s data center.
Machines tethered to a central server. Data flows in to the middle. You trust the hub.
Machines linked directly to each other. Work stays where the hardware is. You trust the receipt.
Your machines talk to each other, not through us. Nothing routes through a RailCall server, so there is no middle to seize, meter, or breach.
Every action carries an Ed25519 receipt anyone can verify offline. You do not have to trust the machine that ran it — or us.
This is an accountability fabric laid over existing networks. Nothing to rip out, nothing new to cable — install it and your machines can transact.
Git didn’t win because of one interface — it won because anyone could build one. RailCall works the same way. Install the protocol and RailHub Studio comes with it, free. Don’t like it? Build your own. Sell it on the marketplace if it’s good.
Machine-to-machine transactions, human-approved, Ed25519-signed, verifiable offline. Free forever, unlimited machines. This is the part that never changes and never costs anything.
Our reference client — ships with the protocol at no cost. It is one way to drive RailCall, not the only way, and nothing depends on you using it.
Build a client that fits how your team actually works — then list it on the marketplace and keep 95%. Studios, modules, integrations: anything on top of the protocol is fair game.
Run it, fork it, wire it to anything, build and sell your own studio. Nothing here is gated, metered, or seat-counted — and it stays that way.
Centralized payments, org-wide audit, company kill switch, evidence packs, compliance attestation, fleet compute routing. The protocol will never do these — it is local and peer by design, and these need a coordinator. That coordinator is RailHub.
Git was free and ran on your machine; GitHub charged the organization for the shared layer on top. We drew the same line — for the moment machines, not people, do the work.
Individuals and teams never pay. The org pays when it wants proof at company scale.
Every job hops to a machine with headroom, runs there, and mints a signed receipt that follows the work. Watch the ledger fill — and watch the cloud column stay at zero.
Every workload you send to rented cloud gets paid for twice — once in hardware you already own, again in someone else’s margin. RailCall runs the work where the hardware already is.
Three steps from zero to accountable agents. All of it on hardware you control.
One command. Local from the first byte. No account, no card, no meter.
$ railcall install ✓ protocol ready — $0, forever
Wire agents to 139 integrations and 33 MCP tools. Every action stops at the airlock until a human approves it.
airlock deploy-fix → HELD approve? [y/N] y — released
Every approved action mints an Ed25519-signed receipt on your machine. Verify it offline — no server, no trust required.
$ railcall verify --offline ✓ receipt valid · ed25519 · local
Your machines form one fabric. When one box is busy, the protocol hands the job to an idle one — machine to machine, no cloud in between — and the Ed25519 receipt follows the work wherever it ran.
$ railcall route embed-batch → fleet scan · 3 machines on the mesh → build-rig-2 · 12% · cool · AC power — selected → handoff over the protocol · airlock approved ✓ receipt 84c2…f19a · minted on build-rig-2 · verify offline
▸ job received ← mac-studio.local ▸ executing · lowest-priority tenant ▸ owner touches the keyboard → instant preempt ✓ done · result returned to mac-studio
Publish and sell modules, integrations — even whole studios — free. 5% seller fee, 10% buyer assurance. That’s the whole take.
Support and community live on Discord. Publishers, protocol questions, module reviews — ask in the open, get answers from people who run it.
Join the DiscordThe protocol is $0 — unlimited users, unlimited machines, local forever. Your org pays only for RailHub. Publishers keep 95%.