Skip to content
stratldocs
Open the portal
Early accessNow open to teams with a real agent

Stratl documentation

Know what your AI did. Prove it later. These pages explain how, from the first principle to the last endpoint, for whoever you are.
What is Stratl?Developer documentation
How Stratl worksFrom source event to independent evidence
01
Ingest

SDKs, OpenTelemetry, provider exports

02
One record per subject

what the AI saw, did, who allowed it

03
Custody

signed, chained, checkpointed, timestamped

04
Evidence

bundles, packs, notices, offline verification

Choose your path

Who are you?

Every page says who it was written for. Start where you are; the concepts are the same everywhere, only the depth changes.

01Executive
I run the businessWhat Stratl is, what it costs to adopt, what it will not do, and the questions to ask before you rely on it.The one-page brief
02Compliance
I answer to regulatorsThe decision record field by field, notices, retention and legal holds, subject requests, and how to verify evidence without trusting us.The decision record, explained
03Operator
I use the portalEvery screen, every button, in order: sign in, connect a source, read a decision, send a notice, export a pack.Sign in and set up
04Engineer
I write the codeLocal setup, the SDKs, connectors, the record format, hashing and signing, custody on your cloud, and the API.Set up a local Stratl
Most read

Six pages that answer most questions

If you read nothing else, read these. Together they take about an hour and cover what a customer, an auditor or a regulator will ask.

  1. 01Compliance·12 minThe decision record, explainedNine fields a regulator asks about, in plain words, then the same fields for engineers.
  2. 02Everyone·8 minVerify evidence without StratlOne command, no account, no network. What each of the twelve checks proves.
  3. 03Compliance·8 minCustody, explainedWho holds the storage and the key, the four permissions Stratl has and the five it does not.
  4. 04Portal·8 minGet started in the portalFive steps from an empty workspace to a record anyone can verify.
  5. 05Compliance·10 minAffected-person noticesDraft, approve, send, withdraw. Deadlines by framework. What the person receives.
  6. 06Compliance·9 minFrameworks and packsColorado ADMT, the EU AI Act, ECOA, NAIC, ISO 42001 and NIST, and what a coverage gap means.
One paragraph, for anyone2 min

Companies now let software make and carry out decisions about people and money: a refund, a claim, a loan, an account closure. When one of those decisions is questioned, months later, by a customer, an auditor or a regulator, someone has to show what happened. Logs are not that proof: they can be edited, they are scattered across vendors, and they say nothing about who was allowed to act. Stratl collects what every AI system did, turns it into one record per decision keyed by the person or thing it affected, keeps that record signed, chained, checkpointed and timestamped in storage the customer controls, and produces the things people ask for: the evidence bundle, the audit pack, the notice to the affected person, the export for a data-subject request. Anyone can check a record with a free tool and no account. That last part is the point: the proof does not depend on trusting Stratl.

Read the full explanation The twenty words Stratl uses