Skip to content
BitExactdocs
Documentation
On this page

Support and supported versions#

Getting help#

  • Licensees reach support through the channel and contacts named in their Order Form, with the severity levels and response targets of the support terms attached to their agreement (Exhibit B).
  • Security vulnerabilities, from anyone: security@bitexact.ai, as reporting a security issue describes. Do not open a public issue.
  • Before you buy: sales@bitexact.ai.

When you open a case, include bitexact version, the output of bitexact health --json, and - for anything about a verdict - the exact line the verifier printed. Never send a run's payloads unless asked: the evidence is yours and stays in your environment.

What every release keeps, supported or not#

These hold for every release, whatever its support status, because they are properties of the evidence rather than of a support contract:

  • A run verifies under the standalone verifier, which is Apache-2.0 and needs no license.
  • An expired license leaves a deployment read-only, never dark: everything recorded stays listable, verifiable and exportable (Licensing (customer docs)).
  • Collectors, SDKs and the recorder speak one collector protocol, which has one form and carries no version (Collector protocol (customer docs)).

Which releases are supported#

The releases your agreement supports, and for how long, are set in your support terms. Fixes ship as new releases: upgrade to the release that carries the fix; a release is never changed after it ships.