Less exposed code, fewer risks
The platform is built on OpenBSD, a system known for its security, and on deliberately compact code. Its services are confined by pledge and unveil: each one can only do what it needs to, even if it is compromised. Each VM is a separate, unprivileged process.
Confidential VMs
On AMD EPYC servers, a VM can run with memory encrypted by the processor (AMD SEV), with a key unique to that VM: its memory remains unreadable to the host system. This protection comes on top of disk encryption.
Data encryption
VM disks can be encrypted with AES-256-XTS, using keys managed by the platform. A removed disk, a replication copy or the remnants of a deleted volume remain unreadable.
Network isolation
Each organization has its own routing table: no layer 2 network is shared between customers. Each VM has its own firewall, which also blocks address spoofing.
Identities, roles and audit
Your team members sign in through a shared identity portal, with two-factor authentication, or with their company account (OpenID Connect). The platform checks the permissions of their role on every request, and every action is recorded in the audit log.
Your VMs belong to you
The platform installs no agent in your VMs and does not log into them. Catalog applications are installed on first boot, by cloud-init, with no subsequent access.