Built on Confidential Compute

Managed PostgreSQL on a confidential VM

PostgreSQL 16, 17 or 18, with backups to your own Object Storage and automatic failover on High availability. The database runs on a confidential VM with encrypted memory, so your data stays private while it runs.

Memory encrypted by the processor (AMD SEV-SNP). The disk unlocks only after attestation.

Why Hippius Databases

Managed for you.
Encrypted for you.

Encrypted while it runs

Each instance is a confidential VM: the processor encrypts its memory with a key the host never sees. There is no shell on the machines.

Credentials shown once

Password, client certificate and backup key are shown once, at creation, and we can't show them again. The certificate authority is destroyed after signing, so no one can issue another.

Backups in your own storage

A full backup every night, a differential about every six hours, write-ahead logs at least once a minute, into your Object Storage. Encrypted with your key before they leave.

By design

What we can't do. On purpose.

Your credentials are made for you and handed over once. So a few things are simply not possible.

  • We can't reset your password.

    There is no reset and no recovery. Lose it, and you start a new database, or restore into one, with a new password.

  • We can't issue another certificate.

    The certificate authority is destroyed after signing your server and client certificates. Nobody can mint a new one.

  • We can't open a shell on it.

    There is no shell on the machines. You reach your data the way your app does: over TLS, with your password.

Use cases

For data you can't leave exposed.

  • App backends on Hippius VMs

    Run your app on a confidential VM and reach the database on your private network, with no public exposure at all.

  • Sensitive records

    Customer records and other sensitive data that the server it runs on must not be able to read.

  • Services that must stay up

    High availability runs three instances. If the leader fails, a replica takes over, typically within about 2 minutes, and the public hostname follows it.

FAQs

PostgreSQL 18, 17 or 16, chosen at creation. 18 is the default. A database can't be resized or moved to a new major version after it is created, so pick a size with room to grow.