01 / 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.

Self-serve. No demo required.

02 / Aha-moment

Two ways to feel it before you sign anything.

No sales call required. The smallest useful experience is on us.

1 Self-serve sandbox

Send your first real payout today.

Sign up. Set the policy. Approve the first batch. Most teams ship in under an hour — at your own pace, no call, no setup script.

Reserve a slot
2 Savings calculator

See exactly how much you save — before signup.

Type your monthly USDT volume. We show your gas savings versus standard TRC20 rate — no signup, no email gate.

You save per month $0

Math: standard TRC20 gas ≈ 1.2% of volume. Railfort pooled energy ≈ 50% lower → effective 0.6%. You save the difference.

03 / Value

Four simple promises. One system.

Every claim is paired with the outcome it answers and the move that delivers it.

01
Outcome · Delegate authority

Delegate operational authority, not the keys.

The CFO signs the policy on-chain once. The team executes within the rules. Keys never move. This is the difference against every custodial competitor and every approval workflow that lives only on the server.

02
Outcome · Run cycle

Run the daily payout cycle without manual reconciliation.

Today: spreadsheets, screenshots, three to five people on a call. With Railfort: auto-reconciliation runs in the background, shortfalls surface before the run, one hundred to two hundred payouts go out in thirty minutes instead of three hours.

03
Outcome · Enforce limits

Limits on the chain, not just on the server.

A server-side limit is just a promise. If our servers are hacked, that promise breaks. Railfort writes hard limits into the smart contract itself. If your daily cap is $50,000, no one sends $50,001 — not an attacker, not us, not anyone. The chain enforces the rule even when nothing else can.

04
Outcome · Reduce per-tx cost

Per-payment cost drops the more you send.

We pool energy and route every send through the cheapest path. Twenty to forty percent lower cost per payment versus retail. Most of the saving passes to you. Aligned incentive: you pay only when you save.

4 simple promises. 1 system. 0 keys in our reach.

04 / Recognise yourself

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

Three outcomes you want. Four triggers. Two emotions. Three pains. The buyer language is verbatim.

Outcome 1
Manage money flow without loss from mistakes or attacks.
Outcome 2
Scale operations without scaling the headcount that runs them.
Outcome 3
Pay everyone reliably — regardless of external changes.

Triggers

  • A teammate sent a payout to the wrong address for the second time. Four to five thousand dollars gone.
  • Visa froze the merchant account in your vertical. Third time in six months.
  • A regulator requested a five-year audit trail. Day three of manual reconstruction.
  • The twenty-fifth contractor is waiting for payroll — and the only signer is the founder, on a plane.

Emotions at point A

  • Constant anxiety that the next seed-phrase share in Telegram will be the last one.
  • CFO burnout — the bottleneck on every payment, unable to take a vacation.
  • Quiet exhaustion from a reconciliation cycle that never finishes by lunchtime.

Pains at point A

  • Five people share the seed phrase in Telegram. No audit trail. Every share is a security incident.
  • The card processor exited the vertical. Every fiat off-ramp adds 3 days, $20 per wire, and one more company that can shut you down.
  • Thirty to fifty thousand dollars per month in gas leaks across fragmented wallets. The CFO cannot see per-transaction.
05 / How exactly

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 · Delegate authority without delegating keys

Delegate operational authority without delegating control of the keys.

Move 1.1 · Policy engine
CFO signs the policy on-chain.

Delegation happens once. Not 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.

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

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

Move 1.4 · 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.

Move 1.5 · Access revocation
Departing staff blocked instantly.

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

Outcome 2 · Run cycle without manual intervention

Run the daily payout cycle without manual intervention.

Move 2.1 · Bulk batch send
One hundred to five hundred recipients per cycle.

An eight-hour cycle compresses to thirty minutes. One operator runs a five-hundred-recipient cycle solo.

Move 2.2 · Reconciliation module
Daily close as a button.

Finance freed from sixty to one hundred eighty minutes per day of data entry.

+ 2 more moves
Move 2.3 · Scheduled batch prep
Monday's batch ready at 9. One tap to approve.

The schedule prepares the cycle. A human still signs off — every time. No payment ever moves without approval.

Move 2.4 · Smart retry routing
If one wallet runs dry, the batch keeps going.

The send falls back to the next wallet automatically. A batch never half-fails because one source ran out.

Outcome 3 · Enforce on the chain, not just on the server

Enforce limits and policies on the chain — not just on the server.

Move 3.1 · Non-custodial smart contract
Keys never on our servers.

A structural architectural commitment. Not a policy promise.

Move 3.2 · On-chain enforcement
Rules live on an immutable contract.

Tamper-proof. Server breach does not bypass the ceiling.

+ 3 more moves
Move 3.3 · Kill-switch in one tap
Containing a compromise is seconds, not minutes.

Revoke any wallet access in one tap. Blockchain-enforced. We cannot override it either.

Move 3.4 · Fake-address detector
Red warning before you sign a bad address.

Every USDT recipient is checked against the real contract. A $4-5K spoof loss does not happen twice.

Move 3.5 · Per-wallet daily caps
Bounded hot-wallet exposure automatically.

Combined with one-click freeze. The worst case is contained.

Outcome 4 · Reduce per-transaction cost

Reduce per-transaction cost at volume.

Move 4.1 · Pooled energy staking
Up to 50% lower gas cost on TRC20.

Pre-staked TRX pool absorbs energy cost. A mechanism no competitor matches — and the savings stay with you.

Move 4.2 · Savings calculator
Concrete monthly savings before signup.

The prospect sees the number before signup. No marketing-hand-wave numbers.

+ 2 more moves
Move 4.3 · Per-wallet gas analytics
Attribute gas cost per wallet or business line.

The CFO sees per-transaction. The finance team sees per-cost-centre.

Move 4.4 · Gas-margin revenue share
Aligned incentive — you pay only when you save.

Margin is embedded in the routing, never billed as a separate line.

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

06 / Point B

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.

07 / Risk

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.

Fears

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.
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.
What if a team member goes rogue?
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.
What if we get deplatformed?
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.
Are you a regulated entity? How does compliance work?
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.
How do funds get from USDT to a bank account?
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.

Barriers

Slow onboarding kills my migration window.
Self-serve onboarding. Same-day setup. First production payout fires the same day, not the same month. No sales call before the product opens.
I do not understand how pricing scales at my volume.
Pricing is public on launch. Self-serve subscription tiers — flat, no per-transaction surprises. The savings calculator shows your monthly number before signup.
Our CTO will block the deal on security review.
Public tier-one audit is ready at the first call. Emergency-withdrawal docs. Counterparty KYC documentation. Bankruptcy-remote design ready for the compliance memo.

Self-serve. No demo gate. First payout fires the same day.

08 / 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.

You could go to Fireblocks, but… +
  • They are custodial. They hold your funds. If they are compromised, the funds are gone.
  • Floor pricing starts at eighteen thousand dollars per year. Mid-market operators cannot justify it.
  • Compliance bundled into pricing. We integrate the same vendors (TRM, Chainalysis, Elliptic) and let you choose your posture — without a custodial-license dependency.
  • Generic copy. Not named for iGaming, adult, or dating. Grey-economy operators do not get an acceptable-use stance.
You could go to Stablerail, but… +
  • You cannot try the product without a thirty-minute sales call. A six-week migration window does not survive that.
  • Generic crypto treasury copy. Not named for your vertical.
  • Standard gas economics. Pooled TRX energy plus revenue-share alignment is not on offer. Your customers save less.
You could go to Bithide, but… +
  • Their custody assumptions are ambiguous in public materials. If you actually evaluate the architecture, an explicit non-custodial statement is the gap we close.
  • Same CIS roots, but the pooled gas mechanism does not match.
You could go to Safe, but… +
  • Safe is EVM only. It does not support Tron. Ninety-five percent of stablecoin volume in your vertical is on Tron.
  • Safe is foundation, not an operating system. No batch payment, no audit trail, no role-based limits, no reconciliation.
You could go to Privy / DFNS / Turnkey, but… +
  • They are components, not a treasury operating system. They give you signing capability — you assemble the rest yourself.
  • Railfort evaluates them as vendor partners under the hood. Not competitors.
You could stay as-is — MetaMask + Telegram + Sheets, but… +
  • 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. No demo required.
First twenty early-customer slots get the founders' direct line and priority feature requests.

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