Pricing & licensing · PG-13 # Open-core licensing, quote-led commercial terms What is free and what is commercial, stated before the price list exists — because pricing architecture is still being finalised, and a marketing page is the wrong place to guess. Ledgerbook's core engine is open-core and source-available, per the stance recorded on 2026-09-19: the ledger primitive itself — double-entry semantics, chain-hashing, the Provisional → Final lifecycle, as-of reads and the ingestion contract — is the free, self-hosted part. Commercial value sits in enterprise support, deployment assistance, and module SKUs licensed separately. No price points are published yet, and this page will not invent any; the full pricing model arrives with GA and is labelled Roadmap until then. In the meantime, access and commercial conversations are quote-led, and the waitlist carries priority. Deployment is not tiered by licence either: self-hosting, HA clusters and the offline air-gap bundle are deployment classes of the same core, not premium editions. Verified 2026-09-19 · licensing stance recorded (OI-12) · pricing architecture deferred (OI-19) ## What the core covers The source-available core is the ledger primitive, not a demo build. These are the PH-1 surfaces a self-hosted deployment runs. ### Ledger and invariants Double-entry engine with live accounting-equation enforcement, integer minor units, per-currency partitions and no implicit netting. Multi-entity by construction: intercompany moves are explicit paired entries, FX conversion is a posted journal with the rate locked at posting. FR-106–115, 126–134 · PH-1 ### Immutability and verification Chain-hashing on every Final entry, enabled by default and not disableable by writers; verification online or offline, and a signed export you can replay into a fresh deployment. FR-118/119/121/813 · PH-1 ### Interfaces REST plus batch ingress, CLI, and an MCP read/propose surface with the same semantics and error taxonomy as HTTP — including air-gapped deployments with your own local model. FR-343 · PH-1 read/propose; full tool surface Roadmap ### Governance and provenance OIDC identity, scoped credentials and row-level access; agents propose but cannot approve, finalize or correct — enforced at the credential. Every mutation carries who/when/where as an event. FR-800–803/805/807, FR-208/234–238 · PH-1 ### Lifecycle and as-of Provisional → Final with one-way finalization, typed corrections in three forms — reversal, adjustment and restatement — and interactive as-of reads: the balance at a date, and the balance as it was believed at a past instant. FR-200–211, FR-500–515 · PH-1 ### Deployment One process on a VM or a bare-metal HA cluster, plus an offline bundle with zero egress for air-gapped sites. Self-hosting is a deployment class, not an enterprise upsell. NFR-6 · PH-1; embedded class and multi-region Roadmap ## How commercial access works Three commitments we can already state, and one we deliberately cannot. | Commitment | What it means | Status | |---|---|---| | No per-transaction metering on the base | Writes, agent calls and validations are not metered on the base licence. A credit meter would price against validation, hashing and provenance — the properties the ledger exists to provide. | ✓ Recorded | | Quote-led enterprise access | Commercial terms are quoted per deployment, not per call — matched to topology, support needs and scale, with self-hosting as the default assumption rather than a premium tier. | ✓ Recorded | | Enterprise escrow | Escrow provisions sit in the commercial agreement (MSA) for enterprise customers. | ✓ Per MSA | | Module SKUs and the published pricing model | Pack and module licensing is to be confirmed, and the full pricing model is published at GA. | ◇ Roadmap | **No prices appear on this page, and none are implied.** Price points publish only with the pricing document, at GA. If you need commercial terms before then, the waitlist is the route — and we will tell you plainly what is and is not decided. ## Pricing FAQ No price list is published yet. The pricing architecture is deferred to the pricing document, and the recorded shape is quote-led enterprise access with module SKUs later — not per-transaction metering. Commercial conversations are quote-led today; joining the waitlist sets priority for design-partner access and first commercial terms. It is an open-core accounting ledger: the core engine is source-available under the recorded open-core stance, with the exact licence text published before commercial launch. Pack and module licensing is still to be confirmed. We use the qualified term 'open-core' deliberately — it is the accurate description, and licence details will be published, not implied. No credit meter ships, and no per-transaction metering is planned for the base licence. That is a deliberate design difference from per-operation pricing in this market: the ledger exists so every entry can be validated, chain-hashed and provenanced, and a meter would price against exactly those properties. If pricing changes, this page changes with it. Design-partner access, a side-by-side evaluation pack, and priority for commercial terms when the pricing model publishes at GA. Waitlist conversations are about deployment shape and evidence needs — not a sales motion. There is no hosted console or sandbox to sign up to pre-launch, and this page will not imply one. ## Get terms when they exist The waitlist is the route to design-partner access and first commercial terms — no pricing promises before the pricing document.