The core of Stratl works end to end today: capture, signing, custody, checkpoints, verification and evidence. It has not carried production workloads for years, and parts are missing. This page tells you exactly which, so you can decide whether now is the right time.
Shown once. Agents use it to write, never to read.
A few lines with the SDK, or an OpenTelemetry collector.
Plain-language summary, lineage, integrity, coverage.
Merkle root, signed, timestamped by a third party.
In your browser or from the command line.
Early access suits some teams well and others not yet. Better you find out here than after an afternoon of integration.
This is the whole integration for a first record. The guide inside the product shows the same code with your own key filled in, and watches for your first record to arrive.
export STRATL_API_URL="https://api.stratl.ai"
export STRATL_API_KEY="sk_stratl_..." # from your workspace, shown onceYou get the ingest key when you create a workspace. It is shown once, it can only write, and you can revoke it at any time from Settings.
import stratl
with stratl.decision(agent="support-bot", subject=("order", "48213")) as d:
d.input(ticket)
d.model("openai", "gpt-5", prompt, response)
d.policy("refunds_above_100_require_approval", version=7, result="human_required")
d.approval(required=True, approver="priya@example.com", decision="approved")
d.action("refunds.issue", target="order/48213", result="executed")
d.outcome(adverse=False, category="refund")
print(d.last.decision_id, d.status) # "recorded", or "spooled" if offlineContent is fingerprinted on your side. If Stratl cannot be reached the record is spooled to disk and sent later, so your agent never waits on us.
stratl verify DEC-01J8ZK3Q....stratl.zip
# ✓ record hash matches, RFC 8785 + SHA-256
# ✓ signature valid (ES256 over canonical bytes)
# ✓ record included in checkpoint root (RFC 6962)
# ✓ RFC 3161 timestamp imprint matches
# Record integrity: VALIDDownload the evidence bundle from the record's page, then check it. Nothing in this step talks to Stratl. The same check runs inside your browser on the Verify page.
Kept current by hand. If something here is wrong, that is a bug, and we would like to hear about it.
Last reviewed 21 September 2026
You should know where everything lands before you send anything. Stratl is never in your agent's request path, and raw content never enters the search index.
The SDK fingerprints prompts, responses and tool payloads on your side.
your infrastructureNormalises the events into one decision record per business subject.
after the decision, not duringSigns the record with your workspace's key. The key cannot be exported.
every signature in CloudTrailStores the record and any originals. Every version kept, no delete permission.
India (AWS ap-south-1)Fingerprints and metadata only, so you can find records by subject.
one location for all workspacesEvery feature listed as working, with no usage caps and no charge during early access. A direct line to the engineers, and a real say in what gets built next.
Point Stratl at an agent that makes decisions someone may later question, even in staging. Tell us what was confusing, what was missing and what you would not trust yet.
Your records stay verifiable without us whatever happens to Stratl. We will tell you before pricing or terms change, and you can export everything at any time.
Signing keys are held in AWS KMS and cannot be exported, records are stored in Amazon S3 with versioning on, and the service has no permission to delete either. That said, Stratl has no SOC 2 report and no service level agreement yet. Many teams begin with a staging agent or a low-risk workflow, and that is a sensible way to start.
Records, original content and your signing key are created and kept in the custody region you pick at sign-up. Live today: India (AWS ap-south-1). The search index, which holds fingerprints and metadata such as subject identifiers and agent names, runs in one location for all workspaces. If you need everything inside one jurisdiction, tell us, because that is a separate deployment.
The SDK fingerprints content on your side, and the record carries only the fingerprints. If you also send the originals so they can be re-hashed later, they go to the custody bucket under their fingerprint. They never enter the search index.
No. Stratl is not in the request path. The SDK submits after the decision is made, and if Stratl cannot be reached it writes the record to a local spool and sends it later.
No, and we will never say so. Stratl keeps evidence and shows which fields a given framework asks for and which a record lacks. Whether you meet a legal obligation is a judgement for you and your counsel.
They remain verifiable. The record format and the verification steps are documented, every bundle carries its own public key and proof, and the verifier runs without any Stratl service.
Export evidence bundles and period packs for whatever you need to keep, revoke your ingest keys in Settings, and stop sending. Every bundle you exported keeps verifying without us.
Pricing is not set. Early access users will hear about it first, with notice, and nothing you have recorded will be held back to make you pay.
Create a workspace and record the first one today. If you would rather talk it through first, write to us.