A SEV-SNP VPS you can verify from inside.

A SEV-SNP VPS is a virtual server whose memory is encrypted by the CPU with a key the host never holds, and whose memory integrity is enforced in hardware. AMD Secure Encrypted Virtualization (SEV) gives each guest its own memory encryption key; SEV-ES extends that to CPU register state; SEV-SNP (Secure Nested Paging) adds "strong memory integrity protection" against replay and re-mapping, enforced by a Reverse Map Table that keeps a one-to-one mapping between physical and guest physical addresses. Linux has run as an SEV-SNP guest since kernel 5.19; the hardware is any AMD EPYC from Milan onwards. Blackbox nodes run the EPYC 7543, a third-generation (Milan) part.

Check the launch policy first. It is a field in every attestation report, and bit 19 is DEBUG: set, the hypervisor may decrypt guest memory through the debug interface; clear, KVM's debug decrypt command "returns an error if the guest policy does not allow debugging". Every Blackbox guest launches at policy 0x30000, SMT allowed, debug and migration disallowed, which is also QEMU's documented default.

Check attestation second. The guest kernel exposes /dev/sev-guest, through which the guest requests a report signed with the Versioned Chip Endorsement Key, "derived from chip-unique secrets". The report carries the launch measurement, the guest policy, the VMPL, a chip identifier and 64 bytes of guest-provided report data you choose you choose, and verifies against AMD's certificate chain with snpguest. That proves a genuine SNP guest at a stated policy, not which kernel or initramfs booted: on an ordinary confidential VM those come from an unencrypted /boot the host can rewrite, and the initramfs is what asks for your disk passphrase. Measured boot closes that hole: firmware, kernel, initramfs and command line are part of the launch measurement, rebuilt byte for byte from public source, and the initramfs binds its fresh SSH host key into REPORT_DATA, so the verifier confirms the signed report, the measurement and the key on the wire before you type anything. The recipe is in the measured boot guide.

Check what surrounds the guest third. On Blackbox there is no guest agent and no virtio-serial channel, so the panel cannot reset a root password. Disk encryption is LUKS2 you run yourself over SSH into the initramfs; the passphrase never touches Servury. Plan table and full limits: the Blackbox page. Background: Blackbox: a VPS its operator cannot read and what your provider can still see.

Where it stops: SEV-SNP protects memory and CPU state, not the network. Servury can still power the machine off; a court order can make it, and cannot make it hand over what it does not have. No DDoS mitigation; one location. Availability is 99.9% under the terms; per-node uptime is live on /status/. No email, no phone, no ID: a 32-character credential is the account, as on the no-KYC VPS page.