Nanorix is a sealed workspace for processing regulated data. Your existing code runs inside. Results come out. When you're done, you destroy it — and get cryptographic proof for your auditor.
50 capsules/month free · Python & TypeScript SDKs · No credit card
Patient records, financial data, PII — your team processes it every day. It hits disk, lands in logs, persists in caches. Then you spend months producing evidence for the auditor that it was handled properly.
What if that 30% ran in an environment where data physically cannot persist?
Think of it like Docker — but every container touching regulated data is a Nanorix capsule instead. Volatile memory only. No disk. No network. When you're done, you destroy it.
Create a capsule. Mount your Capsulefile with your code & deps.
Upload data. Run computation. Download results. Any order. Your workflow.
You decide when. Destroy the capsule. Everything is wiped. Nothing survives.
CDP generated automatically. Cryptographic evidence for your auditor.
Nothing about how you work changes. Where you work changes. And that change gives you the guarantee — and the proof — automatically.
Every capsule produces two artifacts when destroyed. The data is cryptographically eliminated. What remains is evidence.
The Cryptographic Destruction Proof. 8-step SHA-512 hash chain with Ed25519 signature. This is what you hand to auditors, regulators, your customers, a court. Anyone can verify it independently — no Nanorix account needed.
Tamper-evident · Independently verifiable · Works offline · Survives Nanorix
Your complete operational history. Everything in the CDP plus the full activity trail — every file uploaded, every execution, every result downloaded, all with hashes and timestamps. Your legal defense document.
Attorney work product · Complete chain of custody · Your file, not ours
Every CDP maps destruction evidence to the specific provisions your auditor needs. We map the evidence. Your framework tells you which provisions it addresses.
Media disposal. No media to re-use — volatile memory only.
Data disposal controls. 8-step verified destruction chain.
Right to erasure. Storage limitation. Proof generated in seconds.
Right to delete. CDP proves deletion for capsule-processed data.
Media sanitization. Purge/Destroy level verified.
Disposal of media using formal procedures. CDP is the verification.
Data disposal. Cardholder data destroyed with evidence.
Training data governance. Privacy-preserving handling with proof.
CDPs map to any framework with destruction or disposal provisions. Bring yours.
Factual regulatory references, not compliance certifications. Nanorix provides destruction evidence. Your compliance team provides the context.
Python and TypeScript SDKs. Capsulefiles bundle your dependencies. Route your regulated data operations through Nanorix instead of your own infrastructure.
Bundle your code + dependencies once. Mount on every capsule. Your runtime, your libraries, your entrypoint.
Create a capsule, work for hours. Upload, execute, download — any order, any number of times. Destroy when done.
client.run() — create, upload, execute, download, destroy in one call. Same capsule, same proof.
Every capsule includes: sealed workspace, volatile memory, 6-layer isolation, CDP, Capsule Record, regulatory context mapping.
A sealed ephemeral workspace. Isolated Linux namespaces, volatile memory only (tmpfs), no disk, no network, 6-layer isolation. Your code runs inside. You control the lifecycle — create, work, destroy on your terms. When destroyed, a CDP is generated as cryptographic evidence.
A Cryptographic Destruction Proof. An 8-step SHA-512 hash chain with Ed25519 signature that proves data was destroyed. Anyone can verify it independently — in a browser, CLI, or with any Ed25519 library. No Nanorix account needed. Works offline.
Your data enters a sealed workspace that only you interact with. The capsule has no network — nothing can exfiltrate. When you destroy it, the data is cryptographically eliminated. The CDP and Capsule Record are the only things that remain. The data is gone.
Create a Capsulefile — a YAML definition of your runtime, dependencies, and entrypoint. Build it once, mount it on every capsule. Your Python scripts, Node services, whatever you use today runs inside the capsule the same way it runs on your machine.
You do. There is no timer. The capsule is a workspace — create it, work for five seconds or five hours, destroy when you decide. A safety ceiling exists only to prevent orphaned capsules if your process crashes. It is protection, not a countdown.
The CDP is the shareable proof — what you hand to auditors and third parties. It proves destruction. The Capsule Record is your private, complete operational history — the full activity trail of everything that happened in the capsule. It is your legal defense document. Your file, not shared casually.
Every CDP maps destruction evidence to specific regulatory provisions: HIPAA 164.310(d)(1), SOC 2 CC6.5, GDPR Art.17, CCPA 1798.105, NIST 800-53 MP-6, NIST 800-88, ISO 27001 A.8.3.2, PCI DSS Req 3.1, EU AI Act Art.10. These are factual references, not certifications. If your framework has destruction or disposal provisions, CDPs map to it.
API key in 10 seconds. 50 capsules/month free.
Private deployment, BAA, SLA, dedicated engineering.