Why sovereignty belongs in the application layer

The common approach to AI audit integrity is to lean on the cloud provider. CloudTrail is the witness. KMS owns the keys. S3 stores the logs. That shape works if the customer trusts the provider with the evidence and operates inside its region.

For regulated enterprises, for sovereign jurisdictions, for air-gapped environments, and for anyone who simply wants an integrity story that does not rest on a third-party service, the cloud-provider-as-witness model fails. RelayOne moves the integrity into the application and database layer. Signatures compose without any cloud involvement. The chain is verifiable offline. The posture that produced the receipt is recorded in the receipt itself.

Put differently: the integrity story should be portable. If you move deployments from AWS to on-prem to sovereign BC-Canadian, your evidence bundles remain equally trustworthy. Only the application-layer approach gives you that.

Relationship to the rest of the portfolio

  • RelayGate, per-request programmable middleware. Sits inline at the edge. Strips PII, injects credentials, executes ContextWorkers. Asks RelayOne for the policy decision; writes the flow receipt.
  • R1, internal agent runtime. The thing RelayOne reroutes to when a request must stay inside. R1 on Heroa is the sovereign BC-Canadian option for regulated workloads.
  • TrueCom, commerce + receipts substrate. Signs every agent transaction. RelayOne stores the TrueCom receipt alongside its own policy and flow receipts so audit and commerce live on one chain.
  • Veritize, drift tracking. When an agent's output needs to be compared to a ground-truth corpus, Veritize emits drift scores that RelayOne can attach to evidence.

RelayOne does not require any of these; they make it more useful when present.

Team

RelayOne is built by a small team inside Good Ventures. The team composition is intentionally private during preview; the Good Ventures portfolio page names leadership.

Contact

General inquiries: [email protected]. Evaluation requests route through the pricing page form. Security issues: {{TBD-security-contact-email}}.