Solutions
Operator actions logged. Records where an auditor can find them.
Heads of AI, risk and platform at companies putting software and agents in front of money, patients or citizens, who must prove rather than promise.
Why now
Logging is becoming law, with a date.
Logging is becoming law
Article 12 of the EU AI Act requires high-risk AI systems to log events over their lifetime in a format authorities can use. The Digital Omnibus agreement of 6 May 2026 moved stand-alone high-risk obligations to 2 December 2027 and product-embedded ones to 2 August 2028. The deadline moved; the requirement did not. [1]
SourceRegulation (EU) 2024/1689, Article 12; Digital Omnibus agreement, May 6, 2026. The full citation and link are in the footer notes.
What it means for you
The dates moved; the duty did not. Every important system you run will need to produce its own operating record, in a form an authority can read, on request.
What waiting costs
A system that cannot produce its own operating record on demand is a system you will have to rebuild or retire. Adding logs to a cloud you do not control is slow and expensive.
Why Triple X
Triple X records operator actions and placement by default, keeps the records findable inside your own private cloud, and runs on your devices where the regulator wants the evidence inside your walls.
In plain English
Regulators are about to ask for the diary of every important system, not a summary. Triple X keeps that diary for you from day one, on infrastructure you can show them.
What you get
Four things, each a product you can open.
Tier A when a regulator is watching
Capacity reserved for one customer, vetted operator access, continuous control evidence.
OpenA receipt per Sealed run
What ran, where, and that no one could read it. A record, not a log of what the agent said.
OpenAttestations you can request
SOC 2 Type II, HIPAA business associate terms, CMMC Level 2 in progress, under NDA.
OpenPlacement pinned
Records stay on the devices and in your private cloud you chose; failover follows your policy.
Open
Which way in
Start where it fits. Move later without a new vendor.
Triple X Cloud nodes
No hardware of your own. Join the waitlist and start when your seat opens.
Your own devices
Triple X connects your racks or devices to a private cloud of your own.
Both
Sensitive work on your devices, the rest on ours, one private cloud.
Objections you will hear
What someone in the room will say.
Our vendor says they do not train on our data.
A promise in a terms page. In a Sealed enclave, nobody can read the data in use, so the promise becomes a property of the hardware.
We already log everything.
You log what the agent said. The requirement is a record of what it did, in a form an authority can use. That is a receipt, not a log.
Will this slow us down?
Policy checks and receipts run beside the workload on the same node. Measure it in the pilot.
Which regulation do we design for?
Design for the receipt. A verifiable per-run record satisfies Article 12, your auditor and your own incident review at once.
What yes looks like
The list a buyer brings to the table.
- Operator access that is logged and reviewable
- A verifiable receipt per Sealed run, exportable to an auditor
- Data that provably stays in your private cloud
- A 60-day pilot on one real workflow
- Attestations in hand before procurement asks
- No change to the frameworks the team already uses
Get started
Run one governed workflow for 60 days.
The auditor reads the receipt at the end.
- 01
Join the waitlist.
Tell us what you want to run and where. No credit card.
TakesTwo minutes
- 02
Run the pilot.
Ten nodes, 60 days, a pass mark you set in writing.
Takes60 days
- 03
Decide on day 60.
Extend, or leave at the transfer rate and nothing else.
WhoYou
We never ask for your root credentials, API keys or bank details by email.
The first 60 days
A pilot with a pass mark you set.
One governed workflow, Tier A, and an auditor who reads the receipts at the end rather than a promise at the start.
Week 1
Your private cloud on Tier A and the NDA
Create your private cloud on Tier A, sign the NDA and receive the SOC 2 report. Stand up one governed workflow on Sealed with a receipt per run.
Weeks 2 to 4
The real workflow, with receipts
Run the live workflow with policy checks beside it. The pass mark is the head of risk's: a receipt for every run, latency inside the budget, and an operator access log the second line can review.
Day 30
The auditor reads
Give the auditor the exported receipts, the access log and the SOC 2 report. Read the first Tier A invoice beside the current provider's.
Day 60
Decision
Add the next governed workflow, move records to your own devices, or stop. Leaving costs the transfer rate.
Questions
What buyers ask before they sign.
In the order they come up. Every answer ends with where to check it.
10 answers
All questionsWill our auditor accept a receipt in place of our logs?
The auditor decides, so bring them on day 30. The receipt records what ran, where, and that no one could read the data in use; it is verifiable and exportable. Article 12 asks for lifetime event records in a form authorities can use. Your logs stay; the receipt sits beside them.
ProofArticle 12 of the AI Act and the Digital Omnibus agreement of May 6, 2026.[1]
When do we have to be ready?
Stand-alone high-risk obligations now apply from December 2, 2027, and product-embedded ones from August 2, 2028, under the Digital Omnibus agreement. The deadline moved; the record-keeping requirement did not. Design for the receipt now and the date stops mattering.
Proofthe Digital Omnibus agreement of May 6, 2026.[1]
Who at the operator can touch patient or customer data?
In a Sealed run, no one, including the operator. Elsewhere, the platform underneath sees that a workload exists, how big it is and what it costs, and its operator actions are logged. Tier A adds vetted operator access and continuous control evidence.
Proofthe access table on the Security page and the SOC 2 Type II report under NDA.[2]
Which attestations can procurement hold before the tender closes?
A SOC 2 Type II report with an unqualified opinion, period November 1, 2025 to January 30, 2026, under NDA. HIPAA business associate terms where covered. An annual penetration test letter under NDA. CMMC Level 2 is in progress and is said so.
Proofthe SOC 2 Type II report under NDA and the attestation list on the Security page.[2]
What does Tier A cost over the usual provider?
Tier A is indexed at 115 against public cloud on-demand list price at 100, modelled against published rates in July 2026, not measured from migrations. It carries a 99.99% uptime commitment. Billing stays hourly with no minimum term.
Proofthe tier table and the price index note, July 2026.[3]
What does it cost to leave if the regulator changes course?
The outbound transfer rate, from $0.01 per GB, and nothing else. No exit fee, no minimum term. Receipts export with you, and the machines, Kubernetes and the S3 API are standard.
Proofthe transfer bands in the published pricing and the no-exit-fee clause in the contract.[4]
Can the records stay on devices in our own data hall?
Yes. Your devices join your private cloud, placement is pinned before anything is scheduled, and failover follows the policy you set. Run the governed workflow on your devices and the rest on hosted nodes, in one private cloud.
Proofthe Sovereign page and the failover rules on the Reliability page.
What happens in an incident?
Notice to you under the service agreement, with the facts held and the actions taken. The SOC 2 period recorded no security incidents. Vulnerability reports sent through the contact page are acknowledged within two business days.
Proofthe incident answer on the Security page and the SOC 2 Type II report under NDA.[2]
Will policy checks and receipts slow the workflow?
They run beside the workload on the same node. No latency figure is published, so the pilot measures it on your workflow against a budget you set. If the budget is missed, the pilot fails and you owe the transfer rate.
Proofthe latency measurements from your own pilot; nothing is published.
What is not included?
No legal opinion on which regulation applies to you, and no impact assessment written for you. No change to the frameworks your team already uses. Sealed is available for inference today; other Sealed workloads are arranged with an engineer.
Proofthe honest limits on the Sealed page.
No questions under this term yet. Ask Triple X.