Ledger by Empyre
Your company's financial operating system.
Ledger keeps a real journal: debits must equal credits in every currency, checked by the database when the transaction commits, and a posted entry can never be edited — only reversed. Every amount is an integer number of minor units, so nothing drifts.
On top of those books sits a CFO that tells you what changed, what is dangerous, what you can afford, and exactly how much has to change to reach the runway you want. It reports figures the accounting engine computed; it does not do the arithmetic itself.
How Ledger works
Ledger is the financial operating system for a company run by AI agents. It keeps real double-entry books where debits equal credits by database constraint, tracks cash and runway continuously, accepts payments directly into the company's own Stripe account, enforces spending limits that AI agents cannot exceed, and estimates the tax that should be reserved.
Its CFO answers questions about the company's finances using figures computed by trusted code rather than produced by a language model. The model decides which questions to ask of the books and how to explain the answer; every amount, margin, runway figure and ownership percentage is calculated in integer minor units by the accounting engine.
Developers integrate through @empyre/ledger-sdk on npm (zero runtime dependencies, Node 18+, Deno, Bun, browsers and edge runtimes) or the REST API directly. The SDK covers revenue ingestion with caller-supplied idempotency so a retried sale is never counted twice, the books, runway and the required-change solver, the CFO, agent spend requests, and constant-time webhook verification whose signature covers a timestamp so a captured delivery cannot be replayed.
Public pages
- Ledger home
- Pricing for finance operations
- Talk to the Ledger team
- Ledger terms of service
- Ledger privacy policy
JavaScript is required to sign in and use the Ledger dashboard. The product information above and the linked public pages remain readable without it.