Sized by your production agents. Never by your evidence.

How you buy it

A fixed-term pilot, then an annual license in one of two editions: Department, for a band of production agents, or Enterprise, for unlimited production agents. The third part, the verifier, is free for everyone.

1. 1 · Start

   A design-partner pilot

   A full production deployment recording real traffic, with direct engineering support, under a fixed-term license. Continue and the pilot fee is credited in full against your first annual license. End it at the close of the term and nothing further is owed.

2. 2 · Run

   An annual license, in two editions

   Department: one deployment, a band of production agents, unlimited non-production agents and auditor use. Enterprise: unlimited production agents across up to three deployments (production, disaster recovery, a second region), with key custody in your HSM or KMS, a premium SLA and a named engineer. Further deployments, and an air-gapped build, are added to either. Each deployment's license is bound to the recorder key it signs with.

3. 3 · Verify

   The verifier, free for everyone

   Auditors, regulators and counterparties check your evidence bundles with the Apache-2.0 verifier on their own machine. No BitExact license, and no relationship with us.

What it costs

The price depends on the edition, the band of production agents and the deployments in scope. A production agent is a distinct agent identity recording in production; BitExact reports the count itself, so the band is something you can check, and retries, staging and verification are never counted. Tell us what you are recording and we will give you a number and the terms behind it in one conversation, with no discovery gauntlet.

How the license works

• Offline, and nothing phones home. The license is a signed file, validated with zero network calls. The product has no telemetry and makes no outbound connection of its own; your evidence never touches our infrastructure.
• An annual contract, with the license file renewed every 90 days. You sign once a year. Within that contract, the license file itself is renewed offline every 90 days: you run bitexact license request, send us the file, and we send back the renewed license. There is one term, the annual one; the 90-day renewal is a file exchange inside it, not a second contract. A missed renewal date never stops recording; the deployment's health says the renewal is due. The request carries a TPM 2.0 attestation of the recorder host, so a TPM reachable from the recorder is a deployment prerequisite.
• Expiry is read-only, never dark. After the license expires, recording continues through a grace period (14 days unless the license names another). When it ends, nothing new records, replays or forks, but your agents keep running, their calls passed through unrecorded. Everything already recorded stays listable, verifiable and exportable, and legal holds and redaction keep working.
• Licensed use only. Without a valid license nothing records or replays, and an expired license does not lapse into a working mode. A license binds to a deployment's recorder key: one deployment per key, and a further deployment gets its own key under your edition.
• Self-hosting is the product, not a discount lever. Your data never touches our infrastructure, architecturally rather than contractually.

Talk to us

Sales and pilots: sales@bitexact.ai. Security reviews: security@bitexact.ai. The licensing terms are public; the agreement and the security documentation come with procurement.

See also the compliance mapping, the guided demo and the replay taxonomy.