Preview deployment. This hosted instance does not yet persist data across restarts or redeploys and may be reset without notice. Self-hosting with a mounted volume (FLIGHTRECORDER_DATA_DIR) is durable. Do not enter real customer, patient, or payment information.
Flight Recorder

Migrating from Langfuse

  1. Keep Langfuse for tracing/debugging if you like it — Flight Recorder is not a tracing replacement, it's an evidence layer that can run alongside it.
  2. Wrap your OpenAI-compatible client with flightrecorder.Recorder().wrap_openai(client) instead of (or in addition to) Langfuse's callback handler.
  3. Langfuse traces are mutable JSON in a Postgres table; Flight Recorder records are appended to a hash-chained, Ed25519-signed ledger that a `flightrecorder verify` run can prove was never altered.
  4. When you need to hand something to an examiner or auditor, use GET /v1/export for a self-contained regulator pack (records + signed checkpoints + public key + MAPPING.md) instead of a database dump.

See the SDK README for the full Recorder API.