Skip to content

Nanorix Documentation

Nanorix generates Cryptographic Destruction Proofs (CDPs) — signed, hash-chained evidence that data was destroyed through a specific sequence of operations.

Your code and data enter a sealed ephemeral environment. Processing runs in volatile memory. Everything is destroyed. You get results and a CDP.

Get Started

Core Concepts

Sessions are ephemeral compute environments. Each session runs inside 6 layers of Linux isolation with volatile-memory-only storage. Sessions have a TTL and are automatically destroyed when it expires.

CDPs are the proof artifacts. When a session is destroyed, Nanorix executes an 8-step cryptographic destruction sequence. Each step generates evidence, and the evidence is hash-chained (SHA-256) and signed (Ed25519). The resulting CDP is self-contained and independently verifiable.

Regulatory context is a factual mapping included in every CDP that identifies which regulatory provisions (HIPAA, GDPR, SOC 2) are potentially related to each destruction step. This is a reference mapping, not a compliance certification.

Verification

CDPs can be verified three ways:

  1. Web verifier — Drag-and-drop at nanorix.io/verify. Client-side only, zero network calls.
  2. API endpoint — POST /v1/verify with the CDP JSON. Stateless, no authentication required.
  3. Offline — Using any Ed25519 library. The public key is embedded in the CDP. No network needed.

:octicons-arrow-right-24: Verification methods

Resource URL
API Base URL (US) https://api.nanorix.io
API Base URL (EU) https://api.nanorix.eu
Web Verifier nanorix.io/verify
Status status.nanorix.io
Terms of Service nanorix.io/terms
Privacy Policy nanorix.io/privacy
DPA nanorix.io/dpa