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.
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 to your passkeys with WebAuthn PRF. The server never sees the key.
SupportedThe vault stores no record until two passkeys can open it, and refuses to remove one of the last two.
SupportedAnother passkey. There is no emailed link, no support reset and no server copy of the key.
SupportedAn app is allowed per purpose and gets the unlock key for one tab; the key is gone when the tab closes.
Supported
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.
A silo is a microVM with its own kernel and disk and no network interface. Keys stay outside it.
SupportedA 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 may run; a reading from any other hash is rejected, deny by default. Output leaves only as signed records.
SupportedA 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.
SupportedUnits cooperate through the interface's signed documents and the command gate, in shadow before approval.
SupportedRobotics and machines get an attested control unit behind a gate; infrastructure nodes sign their readings; software agents run in silos under a signed policy.
Supported
Where inference and processing run.
Silos, custody and attestation are capabilities of Furcate, the independent operating system Ipnops runs on.
A confined microVM per agent, reached through the API or over MCP, with a receipt for every run.
SupportedA signed policy is verified before anything runs; decisions are committed in signed batches.
SupportedVision, reasoning and speech models, including NVIDIA Cosmos Reason 2, are served by the Ipnops models service.
SupportedPinned environments with no network, read-only inputs and a GPU or a refusal.
SupportedSealed material is held by machines that quote their hardware; unsealing first asks the custody settings whether this machine may open it.
Supported
A record meets a node.
A vault record can carry the minimum attestation class a silo must meet. The silo presents its attestation, you approve, and the record is released to that silo and no other.
Vault records released to a silo by attestation class, with your passkey approval.
Available on requestNode keys through the vault, sealed to a TPM.
Available on requestThe attestation class shown beside each model-serving runtime.
Available on requestA dataset or model weights encrypted to a key only that chip can derive.
Available on requestSeal it. Confine it. Release it on evidence.
Tell us what you want held, and where it has to run.