Recovery & Delete Control is now in early access: use it on your own database nowuse it now

Security enforced by the architecture.

Each protection on this page comes from how DataPrism is built and installed in your cloud, and each one is listed with the conditions it depends on.

Production stays where it runs. The copy lives apart.

Your production database stays where it runs today: Supabase, Neon or AWS. The locked copy, its key and the executor sit in a separate cloud account, installed with your own rights.

DataPrism runs an optional console, designed to see metadata only.

The production database stays where it runs. A copy is replicated into a separate cloud account, where it stays locked for a set lock period; its key, the executor and the release installed there sit in that account too. With the default setup, the cloud provider of that account hosts the key and the compute that decrypts. DataPrism stays outside. It runs an optional console, designed to see metadata only, and publishes releases designed to be signed, which run only once installed in that account: DataPrism cannot push one there. It has no role, no key and no right to delete there, so it cannot read the copy, delete it or shorten its lock. The executor is part of the design.

Four things DataPrism cannot do.

Each one holds on every path, support and recovery included.

  • Read your copy.

    It is encrypted with a key from your KMS. We never hold that key, and support never takes a dump of your database: help always runs in your environment.

  • Delete it or shorten its lock.

    We have no access to the account that holds it. The lock is the storage's compliance mode, which the provider documents as preventing any user, the root user included, from deleting a locked point or shortening its lock period.

  • Change the software you run.

    You pin the release you run, and we cannot push another one in its place. Releases are designed to be signed and reproducible.

  • Write to your database.

    We hold no OAuth application and no management token with write access to your database.

If DataPrism stops operating, your copies stay locked until their lock period ends, and you restore them with your key and the restore tool you hold. The release you installed is designed never to delete a copy, destroy a key or change a lock period.

The conditions that come with it.

We state these conditions next to every promise we make.

Default setup
With the default setup on AWS, the copy, the key and the compute that decrypts all sit at AWS. We never claim that your cloud provider cannot read the copy. An option that keeps the key and the compute outside the provider is part of the design, for teams that need it.
Keys
A copy key you destroy or lose makes the copy unreadable, for you too.
Scope
The copy covers the database, not Supabase Storage files, Vault secrets, Edge Functions or project configuration.
Lag
Data written after the last locked point can be lost.
Destruction control
It covers the operations a platform lets us deny one by one: AWS APIs through an organization policy, Postgres rights on Supabase. A destruction run outside the executor is not prevented; destructive SQL is undone by restoring a point before it. We do not offer it where the platform has no per-action permissions.
Agents
Destruction control is designed to govern what an agent may destroy. We make no promise about what an agent reads.

Who can do what, in short.

The threat model the product is designed against, summarized. We walk through the full model with early access teams.

An agent, a script or CI
Can delete the database and its native backups. Cannot delete the locked copy, shorten its lock period, destroy its keys or remove earlier points.
Someone with your credentials
The same, root included, and can add junk points. Cannot delete a locked point or touch the keys that organization policies protect.
Your management account
Can change the organization policies and close the account that holds the copy. Closing it deletes the copy unless the account is reopened within 90 days, so the design logs that closure and alerts on it.
Your database provider
Can delete the project and its native backups. Cannot reach the copy.
DataPrism, compromised or compelled
Sees console metadata and can stop maintaining the product. Cannot read, delete or unlock the copy, alter your signed attestations or prevent a restore. A modified release runs only if you install it.
Your cloud provider
By default it holds the copy, the key and the compute that decrypts: only the option in the limits above keeps it out. A separate account at the same provider changes who controls the account, not the provider. A second copy at another provider is a separate part of the design.

Before it runs at a customer.

The executor, which holds the right to destroy, goes through a named external security review before it runs at a customer.

To report a security issue, write to contact@dataprism.co.

Ask us the hard questions.

We walk early access teams through the full threat model and every condition on this page. Pricing on request.