Skip to content
BitExactdocs
Documentation
On this page

What's in the customer documentation#

Licensed customers get the full documentation at docs.bitexact.dev, behind a sign-in we grant when you buy. It covers everything below. To see it during an evaluation, contact sales@bitexact.ai.

Getting started#

  • Installing BitExact: the editions, platforms and what each install needs.
  • Quick start: from a fresh install to a verified record of your own agent.
  • Integration surface: the two-line start, every framework adapter, the recording proxy, OpenTelemetry and OpenInference, and the HTTP API.
  • Model providers: each supported provider and how its calls are recorded.

Deploying and operating#

  • Deploying BitExact: every deployment shape, the full settings reference, and the production checklist.
  • Distributed recording: collectors on each host, one recorder, and how a run stays whole across machines.
  • PostgreSQL backend: the database store, its roles and its operation.
  • Administration from the command line: the operator's everyday tasks.
  • Command reference: every command and option.
  • Viewer API reference: every route of the inspector's API.
  • Ops health, alerts, and capacity: what to watch, what alerts mean, and sizing.
  • Event delivery: sending BitExact's events to your SIEM or webhook.

Security and keys#

  • Hardening: recorder integrity and the signed supply chain, step by step.
  • Recorder-key custody: keeping the signing key in a file, an HSM or KMS.
  • Key management and rotation: rotating each key without breaking a record.
  • Identity, access scoping, and the access log: sign-in, single sign-on, roles and who can see what.
  • Supply chain: what ships, and how a dependency is admitted.

Recording and evidence#

  • Capture controls: what is kept, masked or withheld, field by field.
  • Capture coverage: what each recording path sees, stated honestly.
  • Redacting sensitive data, and Retention and redaction lifecycle: removing what must go while the record stays verifiable.
  • Transparency log: the append-only log your runs are anchored in.
  • BitExact compliance pack: what an evidence pack holds for an examiner.
  • The collector protocol: the wire protocol between collectors and the recorder.
  • Licensing and license provenance: how the license works day to day.

Investigating and fixing#

  • Regression suites: replaying recorded runs as a CI gate.
  • The inspector, for compliance and audit staff: a guided tour of the viewer.
  • SDK guide and What replay means: recording, replay and forking in depth.

Also#

  • Engineering principles and the Changelog.

Public on this site, for anyone: the open evidence format, verifying evidence as an auditor, the regulatory mapping, the security posture, the licensing terms and support.