Private Containers
Private containers for the agents you build and run. Bring a framework or your own code.
Use AI on source code, deal documents and customer records without exposing them. The agent, its tools and the model call run in hardware nobody else can read, under rules you set, with a signed record of what it did.

Can't read your data: the cloud provider, the model provider, EQTY
Two ways to use it. Both run in confidential hardware and call OpenAI Private Inference.
Private containers for the agents you build and run. Bring a framework or your own code.
Codex for work, on your confidential code and documents. Set up, locked down and ready for your team.

Codex runs inside hardware that encrypts it while it works, proves what it's running, and gets your keys only after that proof checks out.
Intel TDX and AMD SEV-SNP encrypt the VM's memory with keys held inside the processor. The cloud provider's hypervisor, host OS and staff can't read it. NVIDIA GPUs in confidential mode extend that protection over an encrypted link.
At start-up the chip measures the VM image, the OpenShell policy and the Codex build, and signs the result. We check that report against the build you approved.
Your keys are released to that exact measurement and nothing else. Change the image or the policy and the keys stay locked.
Inside the VM, OpenShell confines Codex to the files, commands and network endpoints your policy allows, and keeps real credentials away from it.
Data is decrypted only inside locked hardware, and only for a task you approved. You hold the key. Revoke it and everything that uses it stops.
You decide which data, tools and models each task may use. Anything else is refused, even if the agent is told to try.
Model calls go to private services such as OpenAI's, only after their hardware is checked, and only to the machine that was checked.
Every task leaves a signed record of what went in, what was called and what came out. Your auditor can verify it without an EQTY account.

The full chain of a task is a graph you can explore: the data, code and model that went in, the hardware each step ran on, and what came out. Select any step to see who ran it, where, and the signatures that prove it.
Every task produces evidence your reviewers can check themselves. It maps to the laws and standards they already work with, across the US, the EU, the UK and beyond.
Signed by Intel, AMD and NVIDIA hardware for every environment that touched the data.
Inputs, actions, tool and model calls for every task. Verifiable offline, without an EQTY account.
When each key was released, to which measured environment, and for which task.
Every version of the rules each task ran under, who approved it and when.
The chain from source data to output, step by step, with where each step ran.
Architecture, data flow and controls, generated from the real setup for security reviews and impact assessments.
Also: PIPEDA ·
DPDP Act ·
APPI ·
NIS2 ·
GLBA
EQTY provides evidence and controls. Compliance depends on how you use them, so confirm the mapping for your case with your counsel and auditors.
An agent reviews and changes code for a product that hasn't launched. It can reach the repository and the model, nothing else.
An agent summarises a data room for a deal that's still secret. Only the summary leaves, and the record shows who ran what.
An agent reads health records and drafts claim decisions for a person to sign, with HIPAA documents for legal.
A pilot puts one AI use case into production on your data in about 8–12 weeks, with the documents your security team needs to approve it.