Sealed data. Keys held where they belong.

The Ipnops vault holds encrypted data and the keys that open it. People hold theirs in passkeys. Nodes hold theirs in hardware. Silos give models and agents a confined place to run.

A vault of sealed records opened by passkeys
01The vault
Signed records linked in a ledger

Sealed on your device.

Records are sealed in your browser to your passkeys. The service stores ciphertext it cannot read. The passkey opens the vault; signing in opens nothing.

Sealed records

Sealed to your passkeys with WebAuthn PRF. The server never sees the key.

Two passkeys

The vault stores no record until two passkeys can open it, and refuses to remove one of the last two.

Recovery

Another passkey. By design there is no emailed link, no support reset and no server copy of the key.

Per-app grants

An app is allowed per purpose and gets the unlock key for one tab; the key is gone when the tab closes.

02Distributed intelligence
Confined nodes cooperating through signed I/O

No single system holds everything.

Intelligence spreads across many nodes, chips and machines. Each unit is confined, identified by its hardware, and cooperates with the others only through signed, approved I/O.

Confined

By design, a silo is a microVM with its own kernel and disk and no network interface. Keys stay outside it.

Solos

A solo is an agent, model or dataset confined to one chip or board, with a hardware identity and keys. A signed manifest pins the model hashes it runs; a reading from any other hash is rejected, deny by default. Output leaves only as signed records.

Hardware identity

A node's identity is derived from its hardware key. A unit earns a grade from how its key is held: soft, device, se, tee, dice or tpm.

Signed, approved I/O

Units cooperate through the interface's signed documents and the command gate, in shadow before approval.

Fields

Robotics and machines get an attested control unit behind a gate; infrastructure nodes sign their readings; software agents run in silos under a signed policy.

03Secure areas
An agent confined in a silo with one signed channel

Where inference and processing run.

Silos, custody and attestation are capabilities of Furcate, the independent operating system Ipnops runs on.

Silos

A confined microVM per agent, reached through the API or over MCP, with a receipt for every run.

Agent runtime

A signed policy is verified before anything runs; decisions are committed in signed batches.

Model serving

Vision, reasoning and speech models are served by the Ipnops models service; a reasoning model serves text.

Job programs

Pinned environments with no network, read-only inputs and a GPU or a refusal.

Custody

Sealed material is held by machines that quote their hardware; unsealing first asks the custody settings whether this machine can open it.

Seal it. Confine it. Release it on evidence.

Tell us what you want held, and where it has to run.