Pricing

Pricing Tied to How Your Data Is Isolated

Not a seat-count tax. What you pay for is where your ledger actually lives.

Every tier runs the same event-sourced ledger core and the same RBAC/audit controls described on the architecture page. What changes across tiers is physical data isolation — because that's the thing that actually has infrastructure cost and actually matters for a compliance engagement.

Free / Dev

Free

Data isolation: Shared D1 database, row-level tenant_id scoping

Domain: yourcompany.ledgerwriter.com subdomain only

For: Evaluation, small engagements, solo practitioners testing the platform against a real chart of accounts before committing

Start free

Most engagements start here

Paid

Contact us

Data isolation: Dedicated D1 database per tenant, provisioned via Workers for Platforms

Domain: Bring your own domain (BYOD) — CNAME/A record, provisioned as a custom hostname

For: Any engagement where a client or auditor needs assurance that your data isn't sharing physical infrastructure with anyone else's

Talk to sales

Enterprise

Custom, contract-negotiated

Data isolation: Same dedicated-database foundation as Paid, plus customer-specific TLS certificates and custom business logic scoped per contract

Domain: Custom domain with dedicated TLS

For: Firms or companies with negotiated compliance, data-residency, or custom-workflow requirements beyond a standard tenant

Contact sales

The append-only event store, RBAC enforcement, write-time balance validation, and audit trail are the same on Free/Dev as they are on Enterprise. Upgrading tiers changes where your data physically lives, not whether the controls exist.

Pricing FAQ

Questions About the Tiers

Why isn't there a price on this page?

Because we haven't finalized public list pricing yet, and a placeholder number would be more misleading than useful to you. Talk to sales and we'll give you a real number for your situation.

Can we start on Free/Dev and move to Paid later without re-onboarding?

Yes, but it's a real migration, not a toggle — moving from shared-DB row-scoping to a dedicated database is an explicit data-export/provision/import/cutover process, not an instant flag flip. Talk to us before you're up against a deadline that requires it.

Does Free/Dev meet SOX 802 retention requirements?

The append-only event store behaves identically on every tier — nothing is ever purged. What differs on Free/Dev is physical isolation (shared infrastructure), which some audit engagements require you not have.

Talk to Us About Your Engagement

Tell us your isolation and compliance requirements; we'll tell you which tier and what it costs.