Immutable by construction.
VaultDB is an encrypted database engine for software in regulated industries. It keeps records and the files that belong to them, from scans to signed contracts and certificates. Each is sealed before it touches the disk, access-controlled down to a single node, chained into an audit log anyone can verify without a key, and erased together when the record is. Records stay searchable without being read. Written in Rust by Clavitor LLC. Governed by Swiss law.
Whoever gets the store gets nothing they can read. A stolen backup, a copied disk, an administrator with full access to the database: each sees sealed content and the shape around it. So anything can go in, from credentials and patient records to contracts, scans and ciphertext you encrypted yourself, under the same guarantees.
objects: files sealed under the record's own rules
over 200 tests · frozen conformance vectors
AES-256-GCM · AES-KW · HKDF-SHA256 · zstd
FIPS 140-3 validated module at rest · AWS-LC FIPS 3.1.0 · CMVP #5314
nine-model security audit · 2026-07-28
checksum 015b54779d2fb2102324c916195ab3feae9a980c25b0a40b82fb019d68b534cd
Records and their files. One seal.
A record was never the whole story. Scans, signed PDFs, certificates: VaultDB keeps them with the record they belong to, sealed under its key, versioned, access-controlled through it and on the same audit chain. Crypto-shred the record and its files go with it.
Objects →Built for the controls the frameworks ask for.
Encryption at rest per record, tamper-evident audit of every write to records and secure files, every read of record data and every read in the secure-full bucket, least-privilege access as a data structure, erasure that survives an audit — the engine gives you the mechanisms; your attestation gets shorter because there is less that could see the data.
These are the controls VaultDB gives you the mechanism for — encryption at rest, tamper-evident audit, least-privilege access, provable erasure. They are not certifications VaultDB holds: a certificate is a property of your deployment and your audit, not of a library. VaultDB is a component you build that case on.
And because the engine indexes only what you declare and seals the rest unread, data you encrypted client-side rides through untouched — encrypt before you store, and it still indexes, audits and shreds.
Every write is a new sealed row. The highest version is current; nothing beneath it is ever touched.
Deletion is a status, recursive through the tree. Grants and revokes are rows. History stays intact and verifiable.
The engine reads only the fields you declared for indexing. Everything else — including ciphertext of your own — is sealed cargo.
Crypto-shred destroys a record's key and its index residue. Rows and chain stay verifiable; the content is gone for good — GDPR and HIPAA erasure without rewriting history.
For anyone who writes software for a regulated industry. Anywhere.
If what your software stores answers to a regulator, an auditor or a court, VaultDB is built for you: healthcare, finance, insurance, legal, the public sector and every other field where data carries obligations. It links into your own process, so it goes wherever your software goes.
Who it is for →
Every seal is cut to its row.
Others search because they can read. VaultDB searches what it cannot read.
A conventional database can search everything for one reason: it holds the plaintext. Encrypt at the field and search dies; encrypt the disk and everyone with database access still reads it all. VaultDB keeps a blind index — a two-byte bucket per indexed value, nothing else — and finds records by prefix without ever decrypting what it stores.
Try it, and see the bucket map →
One file. Many sovereigns.
Tenants share one file the way states share one hall: present, adjacent, and unable to read each other. Everything is a node; a grant on a node covers its whole subtree; one arbiter decides every operation, and what you cannot open you cannot see exists.
Access control, in full →Sealed, scoped, and on the record.
Encryption binds each record to its row. Access decides who may open it. And the log remembers every open of a record — proving, without a key, that the record of it was never altered. Three mechanisms, one file, one transaction each.
History that cannot be rewritten. Not quietly, not at all.
Every write to records and secure files — and every read of record data or of a secure-full file — appends an audit row hashed over the one before it, sealed, and verifiable with no key. Edit, remove or reorder a row and the walk names the seq where it broke; roll back the whole file and the witness says so.
Verify at three levels →The keys that open companies. Kept here.
Clavitor, a credential vault for people and their AI agents, keeps every password and token it holds in VaultDB. Its servers talk over a post-quantum channel (P-256 with ML-KEM-768, FIPS 203), and all of their cryptography runs in one FIPS 140-3 validated module, the same one VaultDB uses at rest.
Governed by Swiss law, from Zürich.
VaultDB is a product of Clavitor LLC. These terms are governed by the laws of Switzerland; disputes are resolved in the courts of Zürich. Switzerland's Federal Act on Data Protection applies regardless of where you live; Swiss law does not permit bulk surveillance or warrantless access, and foreign governments cannot compel disclosure without Swiss legal process.
Licensing and contact →