VOIDED
DATA PROTECTION / OPEN SOURCERUST · NODE.JS · WASM
Voided

Keep the data.
Keep the control.

Encrypt your data. Store one authenticated artifact. Open it with the right key.

Start building Try it here
01 / THE LIBRARYNew to encryption? Start with the fundamentals ↗
plaintext + keyprotectone VOF3 artifactopenplaintext
01 / Run it

Nothing behind the curtain.

Real library. Real output. Change the text, rotate the key, and inspect every byte. This example runs entirely in your browser.

Live WASM

Run the contract.

Runtime idle
Ephemeral test keyNot generated
Function
Waiting for a test key.

Example data only. The key and complete round trip are visible here, stay in this tab, and clear on refresh.

02 / Integrate

Use protect/open.

Choose the runtime where plaintext already exists. Each SDK produces and opens the same Rust-defined artifact format.

Use the stateful client for browser key storage and the normal protect/open lifecycle.

@voideddev/e2ee-client
browser.ts
import { VoidedE2EEClient } from "@voideddev/e2ee-client";

const client = new VoidedE2EEClient();
const blob = await client.protect("Private data", {
  preset: "balanced",
});

const restored = await client.open(blob);
Open the Browser guide
03 / Recover

One deck.
Your interface.

A 52-card order can recover your key hierarchy. Choose an interface below: each uses the same generated deck and the same neutral component.

Build your recovery flow ↗

Read left to right, then down. Positions 01–52 are the order of one deck.

Loading the Recovery Deck component…

DEMO / NOT A BACKUP

Nothing here is saved. Switching views preserves the order; generating a new deck replaces it. In a real recovery flow, the exact sequence is a secret.

04 / The boundary

The security boundary.

Voided owns the cryptographic artifact path. The integrating application still owns access control, runtime security, and storage policy.

VOIDED OWNS

Artifact integrity

  • Cryptographically secure randomness
  • Authenticated encryption and stable formats
  • Explicit compression policy and output bounds
  • Deterministic Recovery Deck derivation
  • Fail-closed parsing and authentication
YOUR APP OWNS

Application security

  • Authentication and authorization
  • XSS prevention, CSP, and dependency hygiene
  • Key lifecycle coordination across tabs or processes
  • Protected artifact and root-wrapper storage
  • Recovery instructions and user experience
05 / Agent access

Documentation for agents.

Use a compact index, full reference, structured JSON, or the local MCP server. Each surface describes the same APIs and invariants.

HTML/ai.html

Human-readable, semantic implementation reference and pasteable agent prompt.

 TEXT/llms.txt

Compact routing index for agents deciding what to read next.

 TEXT/llms-full.txt

Complete standalone product, API, recovery, security, and release reference.

 JSON/ai.json

Structured machine reference with runtimes, layers, invariants, and status.

 MCPVoided MCP

Read-only local source knowledge, symbol search, module discovery, and file excerpts.
Advanced APIs

Lower-level control, when required.

Use these APIs when your application deliberately owns more of the surrounding data format or key hierarchy.

Artifact

Fuse and VOF3

Shape already-prepared encrypted bytes, inspect untrusted metadata, or repack a current artifact.

 Recovery

Recovery Deck

Recover one stable root from a 52-card permutation without storing the deck or derived key.

 Primitives

Own the outer format

Use encrypt/decrypt only when your system deliberately owns serialization and lifecycle.
Implementation

Start with protect/open.

Start with one artifact Open the AI reference

Type a concept or API name.