Software for regulated industries. Anywhere.
VaultDB is for anyone who writes software that holds data with obligations attached: patient records, accounts, claims, contracts, personnel files, credentials. Wherever that software runs, and whichever law it answers to.
The people who build for regulated industries carry the regulator's questions into their code: where is the data, who can see it, what happened to it, and is it gone when it should be. VaultDB answers all four inside the engine, so your product can answer them for your customers.
in-house teams at hospitals, banks and insurers
start-ups whose first customer is regulated
consultancies building for regulated clients
a Rust crate, in your own process
your servers, your customer's, any cloud
Every record and every secure file sealed with AES-256-GCM under its record's own key before it reaches the disk, by a FIPS 140-3 validated module in the default build.
Access is a tree of grants with one arbiter on every operation. A record's files follow the record's access.
Every write to records and secure files, and every read of record data, on a hash-chained audit log that anyone can verify with no key at all.
Crypto-shred destroys a record's key: the record and all of its files become unreadable at once, and the history stays verifiable.
Wherever data carries obligations.
The engine reads only the fields you declare for indexing and seals everything else, so the same store serves a hospital, a bank and a law firm. What changes from one field to the next is the data, and the law it answers to.
Healthcare.
Patient records with their scans, lab results and signed consent, kept together. Every read of a record on the audit chain, and imaging slices in a bucket that logs every write.
Finance and payments.
Accounts, transactions and customer due-diligence files, sealed per record, with an audit trail that verifies without a key and access scoped to the branch, the team or the single account.
Insurance.
Policies, claims and the medical evidence behind them, under one set of permissions, and erased together when retention ends.
Legal.
Contracts, case files and privileged documents, each version kept, every change on the chain, and access granted per matter.
Public sector.
Citizen records, permits and case files, with the tamper-evident history an inspection asks for.
Human resources.
Personnel files, payroll and background checks, readable by the people who need them, and erased on request.
Life sciences.
Study records, trial data and signed documents, every version kept, with an audit trail that shows who changed what and when.
Identity and security.
Credentials, keys, certificates and tokens: the data that opens everything else, kept in VaultDB by Clavitor, the credential vault for people and their AI agents.
The same four questions, in every jurisdiction.
Data-protection law differs in its words and agrees on its demands: keep personal data secure, control access to it, be able to account for it, and delete it when it must go. VaultDB gives your software the mechanism for each, wherever you sell it.
VaultDB gives you the mechanisms; certification is a property of your deployment and your audit, and VaultDB is a component you build that case on. The licence is governed by Swiss law, wherever you are.
Wherever your software runs.
VaultDB is a Rust crate you link into your own process, with the store on a disk you choose. It runs on your servers, on your customer's servers, in any cloud or on a machine with no network at all, on Linux x86_64 and aarch64. The data stays where your software puts it, so data residency is yours to decide. You use it from Rust; there is no interface for other languages today.
sales@vaultdb.ch