Licensing terms, in short#

The commercial terms an evaluator asks about first. The Master Service Agreement itself is provided during procurement; this page states what it says about the things that shape a deployment.

One license per deployment. A license is an offline-validated signed file bound to the recorder key your deployment signs with. It is not metered per seat, per run or per event; recording more evidence never costs more. A second deployment needs its own key and its own license.
Editions, sized by production agents. 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. A production agent is a distinct agent identity seen recording in your production runs over the last 90 days. An agent is its agent_id, or its principal when it states no agent_id; a run is production when its environment is prod or production. Agents in staging, development and every other environment are free, and nothing is priced per seat, run, event or gigabyte. A band changes only at renewal.
Counted, never enforced. bitexact license usage shows the count beside your band, and so do bitexact health and the inspector's License settings. Going over the band is a notice, never a refusal: recording is never stopped, slowed or degraded by it. The count leaves your deployment only inside the renewal request you send us, signed with the rest of the request, as figures and never as the identities themselves.
One annual contract. The contract runs for a year and renews yearly; the 90-day renewal below is a license-file exchange inside it, not a second term. A pilot is a fixed-term license, 60 to 90 days on one deployment, on production traffic with direct engineering support; the pilot fee is credited against the first annual license if you continue.
Expiry is read-only, never dark. A license keeps recording for a grace period after it expires (14 days unless the license names another), with a warning in the recorder's log, so a late renewal is not an outage. When the grace ends the deployment stops producing: nothing new records, replays or forks - but your agents keep running, their calls passed through unrecorded. Everything already recorded stays listable, verifiable and exportable for as long as you keep it, and the standalone verifier needs no license at all. Your legal obligations are never held hostage to a renewal: placing and releasing a legal hold, and redacting personal data, keep working whatever the license's state. Alerts and other events keep reaching the destinations configured before expiry; a destination added after it waits for renewal. A lapsed subscription never puts your own record out of reach. Licensing and license provenance gives the command-by-command split.
Renewed every 90 days, by file. The license carries a renewal date within 90 days. You run bitexact license request and send us the file; we send back the renewed license. A missed date never stops recording: the deployment keeps recording and its 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.
Unmodified software. Every release lists every file it ships, signed. A deployment whose files differ records nothing, passes your agents' calls through, and says why. The agreement prohibits reverse engineering and modification, and gives us an audit right on reasonable grounds.
Nothing phones home. License validation and renewal are offline. The product has no telemetry and makes no outbound connection of its own; your evidence never touches our infrastructure.
The verifier is Apache-2.0. Anyone you hand a bundle to - an auditor, a regulator, a counterparty - verifies it with the open verifier and no relationship with us.
Security and data-protection exhibits (security description, DPA, support terms) are negotiated per engagement and attach to the MSA as exhibits. Ask for the ones your review needs.

Questions: sales@bitexact.ai.