Alpha · Runs on Vault
Data Vault
The storage kernel the other systems sit on. Your data stays where you already keep it.
Every institution that has considered an intelligence platform has run into the same wall: the software wants a copy of everything. Vault is our answer — applications reach institutional data through a bridge, and never hold the credentials that would let them take it.
Composed from
Vault
Vault is the permission and persistence plane every other module answers to — what it may read, write, retain, and pass to the module beside it. View the module layer →
§ 01
The bridge
An application asks Vault. Vault asks your storage.
Connect Drive, Dropbox, Box, OneDrive, or a local filesystem once. Vault holds the OAuth relationship; the client application holds nothing. Revoking an application's access is a switch on this screen, not a support ticket with whoever built it.
Per-client access control
Each connected application gets its own scope across your storage nodes. Two applications reading the same account do not automatically see the same things.
Portability by construction
Because we never held the primary copy, there is no export to negotiate at the end of a contract. Disconnect and the data is already where it was.
§ 02
Why it matters to the rest
The substrate
The consumer apps and the institutional systems are clients of the same storage kernel.
OpenAya
Registered as a connected client with its own root path and scope. Student and project work persists without Serpens becoming its custodian.
MyDigital
Uses Vault as its system layer for asset and subscription inventory. Currently in beta while its access model is finalised.
Institutional systems
Where an agency requires that records never leave its own tenancy, Vault is how a Serpens system reads them without moving them.
What we are careful not to say.
Vault controls access. Where content is genuinely unreadable without a key we do not hold, we say encrypted and mean it. Where the guarantee is scoped permission over a store we can reach, we call it that instead — the two are different promises, and conflating them is how trust pages become liabilities.
Data Vault is alpha. It is demonstrable, it is not yet something to run an institution on, and it is labelled that way everywhere it appears.
Read the Trust Center →If your data cannot leave, start here.
All powered by Serpens
Vault
Vault is one of the four engines every other Serpens product answers to for permission and persistence. How Serpens is built →