A real ledger under your product
Triple-entry postings on a perpetual GL, with each of your customers on an isolated tenant database. Your product gets accounting that ties out by construction.
Developers
API-first ERPon your tenant
Extend the perpetual ledger with tenant-scoped REST APIs, custom subledgers, and event-driven posting — the same surface area Luca and the web app use internally.
OpenAPI spec, module-scoped keys, and isolated tenant databases on cloud today.
trial-balance.sh
curl "https://app.triplebooks.com/api/ledger/trial-balance?entityId=<uuid>&bookId=<uuid>" \
-H "Authorization: Bearer ak_..."TripleBooks Platform
Embed TripleBooks in your product
Fintechs and vertical platforms build on the rails we built — the ledger, balance pools, and reporting run under your product, so your customers get real accounting under the hood.
Balance pools for segregation
Track customer funds and company funds separately at the ledger level. Segregation holds on every posting, and proof-of-reserves attestations generate from the same data.
Reporting your customers can inspect
Trial balances, financial statements, and sealed-period certificates generate through the API — every figure traces to the postings behind it.
Cloud or your infrastructure
Most teams integrate on cloud first. Enterprise licenses add private registry delivery when you need data residency or full stack control.
Cloud
Start building today
Sign up, create an entity-scoped API key, and call the same routes the product uses. Prepaid credits meter writes on cloud.
- OpenAPI catalog and sandbox-friendly keys
- Isolated tenant database per workspace
- Luca, webhooks, and module APIs on one origin
Enterprise
Run on your infrastructure
Regulated teams and air-gapped environments get compiled container delivery, private registry access, and upgrade playbooks with the license.
- Versioned container images from your private registry
- Same API, encryption, and tenant isolation as cloud
- SELF_HOSTED=true bypasses cloud credit metering
What you can build
Automate finance, embed ERP primitives, or extend the ledger for domains the core modules do not cover yet.
Tenant-scoped REST API
Call the same JSON routes the web app uses. Bearer API keys pin one entity, enforce module scopes, and run against your isolated tenant database.
API keysCustom subledgers
Register domain-specific detail ledgers and batch-post into GAAP control accounts with reconciliation to the GL.
SubledgersEvent ingestion & posting
Record financial events, run the DSL posting engine, and read back journal lines on the perpetual ledger.
EventsModule automation
Drive invoicing, purchasing, CRM, treasury, inventory, and projects programmatically on one chart of accounts.
API catalogWebhooks & subscriptions
Subscribe to outbound webhooks when invoices post, periods close, or subledgers drift.
WebhooksVerification & sealed periods
Export trial balances, issue sealed-period certificates, and verify audit-chain integrity from scripts or partner portals.
Periods & closeDocumentation
Start with the API guide, then drill into modules your integration touches.
Browse all docsEnterprise self-hosting
When cloud is not an option, we deliver compiled container images through a private registry with migration checklists, upgrade playbooks, and optional VPC deployment support.
Compiled container delivery
Production runs from standalone Docker images with traced server bundles — delivered through a private registry with your license.
Same API and tenant boundary
Entity-scoped API keys, isolated tenant databases, and the same `/api/...` routes as cloud on your Postgres.
No cloud credit metering
SELF_HOSTED=true bypasses prepaid credit checks on writes. You control capacity, backups, and network policy.
Proofs and ops
Core ledger and subledger flows run on your stack. Period-close ZK proofs use a prover-gateway sidecar or dedicated worker.
Same encryption, tenant isolation, and audit controls as cloud. Security overview
What ships with your license
- 1
License and onboarding
Scope your deployment, receive registry credentials, and get an environment checklist tailored to your Postgres and network.
- 2
Deploy a versioned image
Run the compiled web app and API against your control plane and tenant databases — same standalone build we ship to cloud.
- 3
Migrate and verify
Apply bundled Drizzle migrations, configure secrets, and smoke-test sign-in, API writes, and subledger reconciliation.
- 4
Operate and patch
Follow release notes for image tags, schema updates, and optional prover-gateway sidecars for period-close proofs.
Registry credentials and image tags are provisioned per customer. Source review under NDA is available for vendor security assessments.
Shipping a vertical or partner integration?
We work with fund admins, lenders, and implementers who embed TripleBooks as their system of record. Tell us about your tenant model and we will point you at the right scopes and subledger pattern.