RUST · NODE.JS · BROWSER

Protect data.Store one artifact.

Voided turns plaintext into a versioned, authenticated artifact. The same contract runs in Rust, Node.js, and browser WASM, with bounded compression, Fuse shaping, and stateless recovery available when needed.

Start building Learn how encryption works

1.0 release candidate · VOF3 writer · Windows verification pending

Ephemeral test keyNot generated

Plaintext

Function

Preset

Waiting for a test key.

Node.js accepts text directly and manages encoding. Rust shows the source-of-truth byte API explicitly. The trace exposes the ephemeral key and every byte from the local Rust/WASM execution; refreshing clears it.

plaintext + keyprotectone VOF3 artifactopenplaintext

Default path

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

Recovery Deck UI

One component. Completely different experiences.

Thirteen integrations, one neutral component, and one exact 52-card order. The layouts below change the interaction, composition, motion, and information density—not the recovery protocol.

Experience catalog · 13

All 52 positions at once: the sensible default integration.

Loading the generic Recovery Deck component…

Responsibilities

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

AI 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

Start with protect/open.

Start with one artifact Open the AI reference

Protect data.Store one artifact.

Run the contract.