Your application
Backend / service
Databunker Pro is a dedicated service beside your application. Sensitive profiles and files live behind its API. Your existing database keeps the references.
Backend / service
Your existing business data
customer_id1024user_token—Awaiting a record reference
The controlled retrieval boundary
Encrypted customer records
Separate from your application database
Encrypted file content
Files linked to a customer record
Your backend sends the profile and attached file through the authenticated API. Databunker encrypts their contents before writing to its configured storage.
profile: { name: "Alex Morgan" }
file: passport.pdfThe API credential authorizes the request.
Your backend keeps business data and a token. The vault checks every request and encrypts the originals; a separate database and file store hold only ciphertext. Plan it as an integration, not a config switch.
Your backend creates records and requests the values it needs. Your database keeps separate business records, such as orders and subscriptions, and a reference to the vaulted customer profile.
Databunker authenticates API calls, evaluates the configured permissions, and encrypts sensitive values at rest. Use scoped credentials for application access.
A supported relational database backs the vault. Attached files use local disk or a supported object store, with access going through Databunker.
Knowing a record token does not grant access to the record. The application sends a separate access credential with its API request.
user_token: a21fa1d3…
Stored in your application database.
X-Bunker-Token
Kept in your application backend.
/v2/UserGetAccess is defined by the configured policy, not by possession of a record reference.
A profile in one database. An ID scan in another bucket. Bring them under the same controls, so access follows the person and the purpose.
Mask fields and scope access to records and documents.
Set retention windows and enable profile version history.
Support gets the context to help. Identity documents stay restricted.
The questions that decide whether a vault belongs in production. Every answer links to the docs behind it.
AES-256 per-record encryption, FIPS 140-2 compliant. A rotatable wrapping key protects the master key, so rotation needs no data re-encryption. Backup uses Shamir’s Secret Sharing, 3 of 5.
Encryption docsConditional role-based policies decide which fields each caller receives, with masking on every read. Bulk export is denied by default and audited when unlocked.
Access control docsTenants are isolated with PostgreSQL row-level security. The same person in two tenants gets two unrelated tokens.
Pro overviewAbout 14 ms median per read, flat from 10M to 100M records. Bulk imports reach roughly 12,000 records per second. Storage grows linearly at about 5.7 KB per 120-field profile.
BenchmarkEvery create or update can keep a full snapshot of the profile, hashed for integrity checks. Review what changed, investigate an incident or restore an earlier state. Off by default; you set how many snapshots to keep and for how long.
Versioning docsA stateless Go service on Docker, Kubernetes with Helm, or OpenShift, backed by PostgreSQL or MySQL. Self-host it or let us run it.
Deployment optionsRunning the open-source Databunker? Pro adds multi-tenancy, key rotation, Shamir recovery, format-preserving tokenization, fuzzy search, record versioning and policy-based access.
Ready for implementation details?
Read the architecture docsWalk through your architecture with a Databunker engineer.
Find the right place to start.