Money
Wallets, payouts, escrow, marketplace settlement, balances in several currencies.
Ledger by RODMENA · free today
Ledger is a hosted double-entry ledger with an API. Every transaction balances, every entry is permanent, and every balance can be proved — rules the database itself enforces, not just our code. Free to use today.
112
automated tests
101
database certification probes
54
live probes against the running service
4
internal audit gates
194,432 / 0
requests served / errors in the ten-minute load test
Figures re-counted from the ledger repository on 2026-09-05; every audit was internal, by an independent internal auditor. How the numbers are produced.
In one paragraph
Ledger keeps books the way a bank’s core ledger does: every movement of money, credits or stock has a source, a destination and a permanent record. The rules that protect the books are enforced inside the database, so neither a software bug nor an insider can bypass them. It has passed four internal audit gates and repeated adversarial re-audits, with every finding fixed and re-verified, and it is checked continuously by live probes against the running service.
What it keeps books for
Wallets, payouts, escrow, marketplace settlement, balances in several currencies.
API credits, prepaid packages, loyalty points, gift cards, entitlement units.
Goods on hand, warehouse transfers, seats and licences.
How it works
1
Create an asset type for each thing you keep books of — pounds, credits, seats — and the accounts that hold it, each with its own floor.
2
Every movement names where the value comes from and where it goes. If the two sides do not match, the ledger refuses it before anything is written.
3
Put a hold on funds or stock, complete it when the sale goes through, or release it. Anything you forget is released for you when it expires.
4
Current balances, balances at any past moment, and a statement that never shifts under you — the same records an auditor would ask for.
The getting-started guide shows every request and response, captured from a running instance.
What the database enforces
Six of the twelve. Each names how it is enforced and which live check guards it.
What leaves one account arrives in another, for each kind of asset in the transaction. A transaction that does not balance is refused before anything is written.
Entries are permanent. Nobody can change or delete them, including us. A mistake is corrected with a new, visible transaction that reverses it.
Money, credits and stock are counted in whole minor units, so nothing is ever rounded away. Amounts travel as text, never as approximate numbers.
Every account declares its floor: zero for a customer wallet, a negative limit for an agreed overdraft. A movement that would breach it is refused, even when many requests race for the same balance.
Every write carries a key you choose. If your connection drops and you send the same request again, you get the original answer back and nothing moves a second time.
Your credential is your boundary. Records that belong to someone else do not exist as far as your requests are concerned, and a request without a valid boundary is refused rather than answered.
Who it is for
The books cannot go out of balance, cannot be edited after the fact, and can be reconciled at any time. Corrections are visible entries, not quiet fixes.
One API, exact amounts, safe retries and holds. The hard problems of a ledger are solved once, in the database, so your team never has to solve them in application code.
Give each of your own clients an isolated ledger under your account, mint their keys, suspend and restore them, all through the API.
No surprises
Accurate as of 2026-09-05
Pricing
The free plan includes 10,000 API calls a month with a burst allowance for busy moments. There is nothing to pay, no card to enter and no trial that expires. What it does not include — an uptime commitment, self-service sign-up — is stated plainly on the pricing page.
Pricing in fullQuestions
No. It keeps books for money, for credits such as API credits, loyalty points and prepaid packages, and for stock such as goods, seats and licences. Anything that is counted and must not be created or destroyed outside a recorded transaction belongs in it.
Yes. Balancing is checked separately for each kind of asset in the transaction, so a sale can move goods out and money in as one record. Both sides settle together or neither does.
Metering counts consumption. A ledger records ownership: units that were purchased, can be refunded and can be disputed, where every movement has a source, a destination and a permanent record.
Only if you give it a negative floor on purpose, as an agreed overdraft. Every account declares its floor, and a movement that would breach it is refused by the database itself, even under heavy concurrent traffic.
Send it again with the same key. The ledger either completed the write and replays the original answer, or it did not and the retry does the work. There is no state in which money moved but you were never told.
Nothing today. The free plan includes ten thousand API calls a month. There is no uptime commitment on the free plan, and access is provisioned personally by RODMENA.
An independent internal audit team at RODMENA, working adversarially, through four stage gates and repeated re-audits. No external body has reviewed the ledger. The full history, including the findings, is published on the assurance pages.
Tell us what you keep books of and we will set up a tenant, mint your first key and walk you through the tour.