The balance engine for tokens, points, and quotas.
AI token budgets, in-game currencies, SaaS quota limits, loyalty points — a counter in a database isn't enough. Trancent gives every balance the correctness guarantees of a bank account.
Sound familiar?
A player files a ticket. They bought 1,000 gold coins. They have 347. You dig through logs for an hour and still can't explain the gap.
Can you prove your balance is right?
Your SaaS customer insists they didn't use their full API quota. Your counter says otherwise. You have no way to show them every deduction, in order.
Can you prove your balance is right?
An AI API customer claims your token ledger is wrong. Their audit says they were charged twice after a retry. You can't rule it out.
Can you prove your balance is right?
Your balances are drifting. You just don't know it yet.
A counter column in a database isn't a ledger. Without the right infrastructure underneath it, balance drift is inevitable.
A request fires twice due to a timeout. Your counter increments twice. Your user now has double the credits.
Your upstream fires the same event twice. No deduplication layer. The second one lands silently.
Two concurrent requests read the same balance, both deduct, both write back. One deduction disappears.
Someone fixes the balance with an UPDATE statement. The history is gone. If a user asks, you have no answer.
These aren't edge cases. They happen to every system built on a plain counter. The only way out is a proper ledger.
Banks solved this 500 years ago.
Double-entry bookkeeping is why you trust your bank statement. Trancent brings that same model to every balance in your product — tokens, points, quotas, credits, gold.
Every credit has a matching debit. The sum is always zero. No balance can appear from nowhere, and none can silently vanish.
Records are appended, never updated or deleted. A balance is always the sum of its history — every state is reproducible from first principles.
Quota resets, monthly rollups, and credit expirations are explicit, auditable operations — not silent counter overwrites.
If a user ever disputes their balance, show them every event that touched it, in order, forever. Immutable by design — not as a feature, as a guarantee.
Everything the ledger enforces for you
These aren't configuration options. They're invariants. Trancent enforces them at the infrastructure level so your application code never has to.
Idempotency is enforced at the ledger level. Retrying the same transaction with the same key is a no-op. No double-credits, no double-debits, no matter how many times your client retries.
Every transaction is appended to a permanent, ordered log. Records cannot be updated or deleted — only reversed with a proper counter-entry that itself becomes part of the history.
Every journal entry must balance to zero before it is accepted. The invariant is checked at write time, not at query time. A balance that doesn't add up is rejected before it lands.
Monthly quota resets, credit expirations, and rollover grants are first-class ledger operations with their own audit entries — not background jobs that silently rewrite your counters.
Run unlimited ledgers across unlimited tenants. Each is fully isolated — a bug or balance issue in one tenant cannot affect another. Unlimited orgs and ledgers on every plan.
A clean REST API deployable globally with sub-millisecond latency. No cold starts. No egress fees. Integrate any economy into any application in minutes.
Simple, transparent pricing
Per transaction. Not a percentage of what your users spend. Your economy is yours.
Unlimited orgs and ledgers on every plan.
For developers and side projects
50,000 transactions/mo
No credit card required
For production apps and growing teams
500,000 transactions/mo
+$0.08 per 1,000 over limit
For scale, compliance, and custom requirements
Unlimited transactions
SLA · SOC 2 · Named support engineer
No sales call. No credit card for the free tier. If a user ever questions their balance, you'll have every answer.