Railfort · non-custodial treasury OS

How crypto teams run treasury without sharing keys.

Crypto treasury without the CEO bottleneck.

A non-custodial operating system for teams running daily crypto payouts. Run payouts, approvals, and reconciliation across your team. Keys never move.

A short call with our team, then you're running.

Signed in as

Your send limit Unlimited

railfort.io / approvals Keys not moved

Pending payouts

Friday cycle · 72 recipients · $142,450 USDT

1 of 2 signed
policy check · all within limits

Pick a role. Co-sign. Approve. Keys never move. Illustrative console — figures are sample data.

  • Up to 50%lower gas vs standard TRC20
  • Same dayto your first payout
  • Non-custodialkeys never move
Screening TRM · Chainalysis · Elliptic
The 11pm reality

Grow without being the bottleneck.

Your team runs the daily payouts inside your rules — you hold every key, and the blame stays off you.

Today 23:47

A payout's stuck. Someone texts: "Can you approve?" You're the only one who can — and the seed's in a group chat. Again.

With Railfort 23:47

You're asleep. Your team ran the batch inside the policy you signed this morning — in 8 seconds. Keys never moved.

single point of failure off the hook

What you get

Three promises. One system.

Freedom

Delegate operational authority, not the keys.

Today Seed phrase shared with 5 people
Railfort One on-chain policy, signed once — you still approve.

1 signature, not 100 a day

No more 3-hr close

Run the daily payout cycle without manual reconciliation.

Today 3 hours · 3–5 people on a call
Railfort One button, 30 minutes

200 payouts / 30 min

Sleep at night

Limits on the chain, not just on the server.

Today A server-side promise
Railfort A hard cap on the chain

$50,000 cap stays $50,000 — even if we're hacked

Up to 50% lower gas — you pay only when you save.

up to 50%

Your keys never leave your hands.

Recognise yourself

If any of these read like this week — keep going.

This week 6 unread
  • A teammate sent a payout to the wrong address — second time. $4–5k gone.

    Mon 23:14
  • Visa froze the merchant account in your vertical. Third time in six months.

    Wed 09:02
  • A regulator wants a five-year audit trail. Day three of manual reconstruction.

    Thu 02:40
  • The 25th contractor is waiting on payroll — and the only signer is on a plane.

    Fri 17:41
  • Five people share the seed in Telegram. Every share is a security incident.

    Sat 11:20
  • CFO burnout — the bottleneck on every payment, can't take a vacation.

    Sun 21:05
How it works

Four outcomes. Twenty moves. One screen.

Each outcome ships with four to five moves. Below is the working surface — not the full feature catalog.

Outcome 1 · Team runs it — you hold the keys

Your team runs the payouts. You keep every key.

policy · send limits On-chain
Operatorup to $5,000
Financeup to $50,000
CEOunlimited
Policy signed once · on-chain✓ enforced
Move 1.1 · Policy engine
CFO signs the policy on-chain.

The policy is signed once — not re-approved on every transaction.

Move 1.2 · Group approval for big payments
Two or more people sign off before money leaves.

Treasury does not move without a group. A single compromised account cannot drain it.

Move 1.3 · Access revocation
Departing staff blocked instantly.

No "ex-employee still holds the keys" risk.

+ 2 more moves
Move 1.4 · Send limits per role
Operator $5K. Finance $50K. CEO unlimited.

Routine payments do not require executive approval. Large ones still do.

Move 1.5 · Auto-route by amount
Small payments clear instantly. Big ones route up.

Operator approves routine sends below their limit. Larger amounts flow to finance — then to the CEO only if a higher ceiling is crossed. The founder stops being the bottleneck on every $200 payout.

500 recipients per cycle. 30 minutes, not 3 hours.

Where this lands you

What it feels like the morning after the switch.

Three outcomes, three after-states. Emotions on top, the literal image below.

Confidence.
Outcome 1 · Loss prevention

The CEO sleeps through the night with a hot wallet that holds working capital. The morning dashboard says the same thing every day: nothing leaked. An anomaly surfaces a red screen with context, one click to freeze.

Freedom.
Outcome 2 · Same team, more output

The CFO takes a two-week vacation. The payroll cycle ships on schedule — the on-duty approver signs in one tap. The audit trail is clean. No one called the CFO. A five-hundred-recipient cycle goes out in thirty minutes.

Stability.
Outcome 3 · Rail reliability

A card processor closes the merchant account. Stablecoin payouts keep flowing. A regulator asks for a 90-day report. One click. CSV. Done.

If you're worried about

Every fear answered with a mechanism. Not an adjective.

The questions CFO, CTO and Ops ask before signing. Each paired with the architecture that closes it.

Where your money lives — and where Railfort cannot reach
YOUR CONTROL
Your wallet keys = yours
Smart contract rules live on-chain
RAILFORT
Railfort server signals only · no keys
FUNDS LIVE HERE — the boundary funds never cross. A Railfort breach is downtime, not loss. custody: none
TRM Labs Chainalysis Elliptic Tier-1 audit Bankruptcy-remote
R-01 STRUCTURAL custody: none What if Railfort gets hacked?
Railfort does not hold keys. If our servers are compromised, the attacker still cannot move funds — on-chain limits and the smart-contract policy still hold. The worst case is operational disruption, not loss of funds.
R-02 STRUCTURAL custody: none What if Railfort closes as a company?
Your money never sits with us. It sits inside the smart contract — code on the blockchain we cannot reach. If our company disappears tomorrow, your wallets are still your wallets, your keys are still your keys, your rules still execute on the chain. This is the structural answer custodial competitors cannot give.
R-03 MITIGATED What if a team member goes rogue? per-wallet caps · role send-limits · revoke in one tap · rules live on-chain
Per-wallet daily caps, send limits per role, per-amount approval thresholds, instant access revocation on offboarding. Any wallet access revoked in one tap. The rules live on the chain — we cannot override them either.
R-04 STRUCTURAL What if we get deplatformed? not a custodian · no authority to freeze your funds
We are not a custodian. We have no authority to freeze your funds. Explicit acceptable-use stance for the verticals every other vendor avoids. Visa exited the vertical. We remain.
R-05 STRUCTURAL Are you a regulated entity? How does compliance work? non-custodial · TRM / Chainalysis / Elliptic screening · one-click audit trail
No — and that is the point. Custodial competitors are regulated because they hold your funds. We do not. Your wallet stays yours, your seed phrase stays with you, your smart-contract rules execute on the chain. That keeps us out of money-transmission scope, and keeps your compliance posture in your hands.

What we add on top: address screening via TRM Labs, Chainalysis and Elliptic. Sanctions-list hits surface before you sign. One-click audit trail your regulator can read. We surface the signals. You make the call.
R-06 ROADMAP How do funds get from USDT to a bank account? BYO OTC desk today · native SEPA / SWIFT off-ramp in Phase 2
Today: bring your own OTC desk or off-ramp partner — we hand off cleanly with a full audit trail. The point of Railfort is removing fiat-processor dependency from your daily cycle, not adding one. Native off-ramp integrations (SEPA / SWIFT) ship in Phase 2 of the roadmap.
R-07 MITIGATED Slow onboarding kills my migration window. guided setup · same-day · first payout fires the same day
Guided setup with our team. Same-day setup. First production payout fires the same day, not the same month.
R-08 MITIGATED I do not understand how pricing scales at my volume. flat subscription tiers · no per-transaction surprises · calculator before signup
Pricing is public on launch. Transparent subscription tiers — flat, no per-transaction surprises. The savings calculator shows your monthly number before signup.
R-09 MITIGATED Our CTO will block the deal on security review. tier-1 audit ready · emergency-withdrawal docs · bankruptcy-remote design
Public tier-one audit is ready at the first call. Emergency-withdrawal docs. Counterparty KYC documentation. Bankruptcy-remote design ready for the compliance memo.

Our team gets you live — first payout the same day.

Versus the others

Six other ways to do this. One reason to choose this one.

Each "but" is a structural difference — not a feature gap that a competitor patches next quarter.

  • Your seed phrase is in Telegram. One leak, and everything is gone.
  • Your CFO is the bottleneck. They cannot take a vacation without a missed payment.
  • Your reconciliation is manual. Three hours of CFO time every day.
  • Your audit trail is a phantom. When the regulator asks, it is three days of manual reconstruction.
09 / Next

Crypto treasury without the CEO bottleneck.

Start your first payout in under an hour. A short call with our team, then you're running.

What you get

  • Twenty early-customer slots
  • Public pricing on launch
  • Guided setup
  • Founders' direct line for the first thirty days
Pre-launch
20 early-customer slots First batch closes when twenty active contracts sign.

  1. Reserve
  2. Short call
  3. You're running
Non-custodial — we never touch your keys or funds.

No spam. One email from a human.