Website preview / Explore example files. Live storage is not connected.About this preview ↗
THE DATA WORKSPACE FOR THE HYBRID ECOSYSTEM
Your data. In context.
Private data. Public evidence.
A home for what matters. A purpose-built view for every kind of work. Bring files, identity evidence and agent memory into a Vault you can understand and manage.
Hybrid Vault is the data workspace behind the ecosystem. These example application views illustrate the proposed realms: files, memory, document status and supporting records. Connected realm access is still being developed.
A familiar home for your files.
Organize documents, browse folders and find the things you keep. This is the general file-management view of the same underlying Vault.
Proposed realms. Deliberate access. These views are prototypes. Server-enforced realm isolation is not implemented here; changing a view does not grant access to another application’s data.
OWNERSHIP, IN EVERYDAY ACTIONS
See what control looks like.
Your data has a home. Every application has a purpose. You stay in control of the connection.
Follow three guided examples of the experience we’re building: understand the record, choose its use, and see the boundary around it.
Conceptual data flow · Not live storage or network activity
UNDERSTAND THE LAYERS
One Vault. Distinct foundations.
Explore what each layer contributes—and the evidence that belongs with it.
PROTECTION
Protect the content. Choose the access.
The accepted native Vault flow encrypts file content and filenames before storage. Owner approval binds file access to the intended application and recipient.
What this means for you
Protection and permission remain explicit. Existing files retain their own protection profile while the separate upgrade work continues.
Strong cryptography starts with good randomness. Hybrid’s quantum entropy service obtains random bytes from dedicated quantum random-number generator hardware.
The meaningful questions follow the randomness: where it came from, how it was handled, and which approved operation used it.
Ecosystem capability · Vault-specific integration is still being defined.
PUBLIC-CHAIN VERIFIABILITY
A proof you can follow. A file you keep private.
The evidence should give you something concrete to inspect. Hybrid-Chain provides public records and native validator certificates; Hybrid Explorer makes those records readable.
MainnetPublished acceptance example
EXISTING VAULT PLATFORM · 20 OCTOBER 2026
Real file operations. New Mainnet evidence.
The published API acceptance used five isolated synthetic owners. Original files were uploaded, retrieved byte-for-byte, revoked and explicitly reapproved. Their new native proofs were independently checked.
Public-safe commitments Recorded timestamps Network & evidence state Validator certificates
Each state has its own meaning.
01
Stored
A storage operation has been acknowledged.
02
Replication observed
Current observations describe available copies.
03
Evidence submitted
The public commitment enters the evidence path.
04
Validator-finalized
A native certificate establishes finality for the record.
A finalized record establishes its certified commitment. Current file availability and access remain separate checks.
POWERFUL FOUNDATION. FAMILIAR FRONT DOOR.
Purpose-built for data. Familiar for everyday work.
Files are one way into the Vault. Memory and identity-document views make other kinds of data easier to manage. Explore the purpose-built interfaces with clearly labelled examples.
Organize & find
Nested folders, breadcrumbs, filename search, filters, and list or grid views.
Open & understand
Example previews, exact versions and readable file details, with deeper evidence within reach.
Share deliberately
Review the file, version, recipient and permission. Keep workspace people and external recipients distinct.
Lock when you choose
A clear open-padlock control, a considered confirmation, and a private locked view.
Keep contexts clear
Separate personal and organization examples, proposed app contexts, and an isolated Testnet view.
Follow what happened
See the intended destination, interrupted-upload states and original-operation reconciliation.
Shared identity can make access familiar. Sharing files, identity documents or agent context remains an explicit, separately authorized choice.
A FEW GOOD QUESTIONS
Get to know what stands behind it.
Why does each realm have a different interface?
The Vault is the underlying data workspace. The work determines the interface: folders for files, spaces and versions for memories, document status for identity evidence, and records for banking or Discovery. The planned realm contract supplies segregation and permissions; the interface does not create authority.
Can I edit agent memories directly through the Vault?
That is part of the Vault’s role. The memory-management preview lets you edit a fictional entry and retain its earlier version. The connected design lets Hybrid Cortex use the amended, authorized memory record under its existing policy. This preview does not synchronize with Cortex or change an agent’s permissions.
What makes the architecture decentralized?
The storage, access and public-evidence responsibilities are separated. The existing storage architecture uses IPFS and regional replication, while Hybrid-Chain records public-safe commitments. Today’s operated services and admitted infrastructure still have defined trust boundaries. A public, permissionless storage-operator network is not established by this preview.
How do quantum entropy and encryption differ?
Quantum entropy describes a physical source of randomness. Encryption describes the algorithms and keys that protect a file. The hardware source does not, by itself, establish post-quantum encryption. Vault-specific entropy consumption is still being defined; existing files retain their actual protection profile.
What does a public storage proof establish?
It lets you inspect the published commitment, its evidence state and available native certificate. Merkle inclusion and validator finality support that recorded event. They do not expose a document’s content or independently guarantee its future availability. Storage readiness, replication observations and current access are checked separately.
Will my documents appear on the public chain?
Protected file contents, filenames, private owner references and recipient lists do not belong in public proof metadata. The public evidence path carries approved commitments and record information instead.
What can I use on this website today?
You can explore the frontend with fictional files: folders, previews, sharing reviews, lock states and an interrupted-upload example. Real storage is not connected here yet. Sign-in availability is shown on the separate Hybrid ID connection page. The published Mainnet evidence linked above comes from the existing Vault platform’s separate acceptance run.
What happens when I revoke a share?
The connected service’s revocation rules govern future authorized retrieval. Revocation cannot recall plaintext or keys a recipient has already received. The preview demonstrates the review and local state change without modifying real access.
MEET YOUR NEXT SPACE
Keep what matters. Understand what protects it.
Try a purpose-built view. Follow the evidence. See how your data fits together.