Stratl has one job: keep trustworthy evidence of what AI agents decided, so that months later a company can answer for it.
Chain intact. Each layer names the fingerprint of the one beneath it.
An agent can refund an order, turn down an applicant or change a production system in the time it takes to read this sentence. Each of those is a decision about a person or a system, and each can be questioned long after the agent, its prompt and its model have all been replaced.
When the question comes, the account of what happened is spread across tools that were built for other jobs. The trace sits in one place, the approval in a chat thread, the policy version in a repository. Each is kept for as long as that tool happens to keep it, and each can only vouch for itself.
We think a consequential decision deserves what a payment or a signed contract already has: one record, made at the time, kept in custody, that a stranger can check. Stratl is that record layer and nothing else.
order/48044Today: five tools, five retention windows.With Stratl: one record, made at the time.
The name. Strata are layers laid down one on top of another. You can read what happened from them because nobody can slip a layer in underneath without disturbing the ones above. A chain of decision records works the same way.
When a decision is questioned, these are what a customer, an auditor or an incident review ends up asking. Here is where one example record answers each of them.
What did the AI see?
The record answers withinputThese are constraints on the product, written into how it is built. They are not aspirations, and none of them is switched off for convenience.
Each workspace's key is generated inside AWS KMS and cannot be exported by anyone, us included. Our service may ask for a signature and read the public key. It may do nothing else with it.
kms:Signallowedkms:GetPublicKeyallowedA record says how it was captured: observed, attested or enforced. Storing a record carefully does not make it stronger evidence than it was, so the level never moves up.
RFC 8785, SHA-256, ES256, RFC 6962 and RFC 3161. Nothing in the integrity design is our invention, which is what lets a third party check it with their own tools.
Prompts, responses and payloads are fingerprinted before they reach us. The search index holds fingerprints and metadata. Originals, if you send them, go to the custody bucket under their own fingerprint.
Please refund order 48213. It arrived damaged.
sha256:9215a189e9865140b67cfbd4c890c98b83fb37be…
The verifier needs no account and no network. Every bundle carries its public key, its checkpoint proof and its timestamp, so someone who has never heard of Stratl can check it years from now.
The early access page lists what works, what is in progress and what is not built, with the date it was last reviewed. When the product changes, that page changes.
The rule we build by. If another product already knows what happened, Stratl ingests it. If another product enforces something, Stratl records that it did. Anything else is someone else's product.
Evidence is only useful if the people describing it are exact. These are sentences you will not hear from us, and what we say in their place.
A record can never be changed.
What we sayA change to any record shows, and anyone can run the check that shows it.
Stratl makes you compliant.
What we sayStratl shows which fields a framework asks for and which are missing. That is coverage. Whether you meet an obligation is for you and your counsel.
This is why the model decided.
What we sayThis is what it saw, what it called, which rule applied, who approved, and what happened next.
We capture everything your agents do.
What we sayWe record what your capture points send, and every record states how it was captured.
Stratl is a young product run by a small team. During early access there is no sales process and no ticket queue. You write to us and the people building it write back.
Create a workspace, record one decision from the agent you already run, and verify it yourself.
Tell us what your agent decides and who might ask about it later. We will say plainly whether Stratl fits today.
If anything on this site does not match what the product does, we want to know, and we will fix the page or the product.
Write to us before publishing. Please do not include customer data or secrets in the email.
Stratl is designed, built and operated by Vyana Compute. During early access you talk directly to the people building it, at hello@stratl.ai.
Tracing tools are built for debugging, and they keep data for as long as debugging needs it. Evidence asks for different things: it has to be filed under the person or thing it was about, kept for years, signed with a key the vendor cannot export, and checkable by someone outside the company. Stratl takes data from tracing tools. It does not replace them.
Because the system that enforces a rule should not be the only witness that the rule was enforced. Gateways, approval tools and policy engines do the enforcing. Stratl records that a control ran, at which version, and with what result.
The design tries to make that unnecessary. Signatures come from a key we cannot export, timestamps come from an outside authority, and verification runs without us. What a young product cannot offer yet is a SOC 2 report or a service level agreement, and the early access page says so plainly.
No. It is in private early access for a small number of teams with a real agent. The early access page lists what works today and what does not.
The quickest way to find out whether we mean any of this is to record a decision from your own agent and verify it without us.