Earn on‑chain. Spend in fiat. One ledger.
For companies that earn on HyperCore and pay people in euros and dollars: builder fees in, contractors and cards out, and books your accountant can close.
Chain read every 5 min · reconciled, never auto‑adjusted
Every move, on the ledger.
The same double‑entry ledger as Alato Personal, in integer minor units: USDC to six places, HYPE to eight, euros to two. Chain, off‑ramp and cards post through ports; a rule is a few balanced entries you can read.
Decide once. The ledger does the rest.
Four rules cover most treasuries: convert above a threshold, keep a fiat runway, keep a card float, sweep what is idle. Each one proposes a movement; above the limit, people approve it.
Example balances · USDC 184 320.55 · burn €31 000 / month · rate 0.9212
Pay people, not addresses.
Contractors send an invoice from their own page. You approve it; the ledger pays it; the journal records it.
Contractor invoices
A contractor gets a page of their own: upload the invoice, see its status, download the receipt. Every invoice carries a cost centre.
Monthly payout limits by jurisdiction, enforced server‑sideCorporate cards
Virtual cards per person or per vendor, with a limit per purchase and per month. A hold lowers the float at once; settlement for a different amount posts the difference.
Same Cards port as Alato Personal · physical cards plannedAccounting
A journal CSV any accountant can import today; a sync layer for Xero and QuickBooks behind it. Statements and receipts as PDF and CSV.
Xero and QuickBooks adapters: built as stand‑ins, connections plannedAttribution
Revenue is attributed to where it came from — builder codes, addresses, products — so the P&L reads by line of business, not by wallet.
Up to ten watch‑only addressesStake hedge
A hedge against staked HYPE, sized from the position the chain reports and re‑checked on every read.
Runs on the internal adapter; mainnet orders plannedCost centres & reporting
Spend by team, by vendor, by month. The numbers come from the ledger, so they match the statement to the cent.
Interface in English, German, French, RussianMaker, checker, and a server that keeps count.
Four roles. One approval below the threshold, two above it, each with step‑up authentication. The person who asked can never be the one who approves.
| Can… | Admin | Approver | Operator | Viewer |
|---|---|---|---|---|
| Request a payout or conversion | Yes | Yes | Yes | — |
| Approve someone else’s request | Yes | Yes | — | — |
| Approve their own request | Never | Never | — | — |
| Change rules and limits | Yes | — | — | — |
| Issue and freeze cards | Yes | Yes | — | — |
| Read the ledger and export books | Yes | Yes | Yes | Yes |
Until KYB is approved, payouts, conversions, rule runs, cards and invoice approvals are refused with 403 KYB_REQUIRED. Viewing and settings keep working, so a team can set everything up before the first transfer.
What runs today, what is planned.
No client funds are held or moved. Mainnet writes are disabled; only testnet writes are built. Nothing here is regulated or protected yet.
Built
- Double‑entry ledger, balanced per currency at commit
- HyperCore read every 5 minutes; testnet writes
- Attribution, rules, stake hedge on the internal adapter
- Maker‑checker approvals with step‑up; roles; limits
- Contractor invoices and self‑service page; cost centres
- Journal CSV, statements and receipts (PDF, CSV)
- Reference rates: Frankfurter, Kraken, FRED
Planned
- Mainnet transfers and hedge orders
- Banking and off‑ramp provider; corporate card issuer
- Tokenised T‑bill fund for the sweep rule
- KYB provider and sanctions screening
- Xero and QuickBooks connections
- Passkeys, single sign‑on, audit export
- Physical cards; dedicated production environment
Bring your builder code. We’ll bring the books.
Entities in the first partner’s jurisdictions onboard first. Tell us where you are incorporated and what you earn on‑chain, and we’ll say what is possible today.