ARK256
BUILT WITH TENANTSDB /
ARK256
ARK256
Zero-knowledge encrypted file storage. The server can never read what it stores, and every vault keeps its data in its own physically isolated database.
Built with TenantsDB
VIA TENANTSDB
mongodb
WEB
ark256.com
THE PROBLEM
Encrypted files deserve more than a shared bucket
Zero-knowledge encryption protects file contents. The server holds only ciphertext and can never read what it stores. But encryption says nothing about where that ciphertext sits. In most encrypted storage products, every vault's data lands in one shared bucket or one shared database, so the isolation ends at the cryptography. A misrouted query, a backup mistake, or a bad migration touches every vault at once.
For a product whose entire promise is separation, that is a weak foundation. Ark256 wanted tenant isolation to be physical, not just cryptographic: each vault's encrypted data in its own database, with its own lifecycle, its own backups, and a blast radius of exactly one.
HOW IT USES TENANTSDB
One isolated database per vault, files included
Every Ark256 vault is its own MongoDB database, provisioned through TenantsDB on a database-per-tenant model. Encrypted files are stored inside that database using GridFS, MongoDB's native large-file storage, so the files are captured in the vault's backups and restore together with the vault as one unit. Deleting a vault means dropping one database, and everything in it is gone in a single step. The higher tier goes further: a file is sliced across three separately provisioned, physically isolated databases in different regions, so no single database ever holds the whole file.
TenantsDB makes the vault lifecycle programmable. Vaults rotate on a schedule: a fresh database is provisioned through the API, encrypted data migrates over, the vault repoints, and the old database is destroyed. Storage infrastructure becomes something the product creates and discards on demand. The control plane stays separate the whole time, so nothing about running the product shares storage with what users encrypt and keep. Cryptography protects the contents, and physical database isolation protects the boundaries.