Virtual machines that stay encrypted while they run

Confidential Compute runs your virtual machines, PostgreSQL databases, Kubernetes clusters and GitHub Actions runners on VMs whose memory is encrypted by the processor itself, so the server they run on can’t read it. The disk unlocks only after the machine’s attestation checks out, so what you deployed is what’s running.

Launch a VMHow it Works
  • Virtual Machines
  • Managed Database (PostgreSQL)
  • Kubernetes
  • CI Runners

Only you can see your workload. Nothing to rebuild.

Move your existing containers, databases and services across as they are. Plain Ubuntu or Debian, or a ready-made app like WordPress, with SSH from your terminal or the browser. Encryption happens below the operating system, so nothing in your stack has to know it's there.

Virtual machine list in the Hippius console, with an instance's action menu open
Virtual machine templates in the Hippius console
A virtual machine's details in the Hippius console

Confidential Compute Plans

Fixed VM sizes with memory encrypted by the processor. Metered per second from your account balance, from launch until you delete the VM.

Billed per second
Loading Confidential Compute VM sizes

Metered per second (one-minute minimum) and charged hourly from your account balance. A stopped VM is still billed: delete it to stop paying. Monthly prices are estimates over 730 hours. Outbound bandwidth depends on the region: see the table below.

Cost Calculator

Know your bill before you launch.

Loading the Confidential Compute cost calculator

Why UseConfidential Compute?

Encrypted while it runs

The memory itself is encrypted by the processor while your code executes, with a key the host operating system never holds.

The disk opens only on proof

Your disk stays locked until the processor proves the machine runs approved software. A VM that fails never finishes booting.

Proof you can check yourself

Each VM's page shows its attestation, with the processor's signed report when it's on record. Check AMD's signature yourself.

Secrets handed over once

Database credentials are shown once. The kubeconfig is sealed to a key made in your browser. A deleted VM's disk is crypto-erased.

What our users think about Hippius

Peyton SpencerCEO, Ditto
“Our storage costs on Hippius are nearly zero. We've moved every trace our AI agents generate onto Hippius, and it keeps scaling cleanly without any issues and minimal cost.”
Ahmad AyadML Engineer, Vidaio
“We moved our video processing pipeline from AWS S3 to Hippius for one simple reason: to save costs. The switch was seamless, nothing about our workflow changed, we just pay less to move the same data.”
@0xROLOFrom X
“I can't wait to have the Hippius app on my iPhone and Mac and make it one of my most-used apps”

How We CompareWith The Market

Features
Hippius
Azure
Google Cloud
AWS
Disk key released only after attestation
Yes
Yes
Partial supportConfidential Space only
Partial supportDIY with NitroTPM
Managed PostgreSQL on confidential VMs
Yes
Partial support2 regions, no attestation
No
No
Managed Kubernetes with the control plane on confidential VMs too
Yes
Partial supportWorker nodes only
Partial supportWorker nodes only
No
Ready-made confidential CI runners (GitHub Actions)
Yes
No
No
No
Runs on independent operators, not one company
Yes
No
No
No

Start usingHippius today