A privacy VPS you can verify, not one you have to trust.

Read the privacy pages of the well-known providers and a pattern appears: the privacy is a policy. "We do not log", "we do not ask for ID", "we will not hand over data without a court order". Policies can be changed, ignored under pressure, or contradicted by another page on the same site. A capability that has been removed cannot. Every cell below comes from the provider's own public pages, read on the date given; the quotes are collected on the in their own words page.

"Not mentioned" means the provider's homepage did not mention SEV, SEV-SNP, confidential computing or memory encryption when we read it. Two providers in this table sell encrypted memory. One of them also takes no identity, no email, runs its own payment rails and publishes the boot chain for you to measure.

A no-logs claim is checkable only if the provider tells you what "no logs" means on their boxes. Here is ours, as configured on the web and hypervisor hosts, and restated in the privacy policy.

• Web access logs: none. Every vhost carries CustomLog /dev/null combined. No IP, no page, no timestamp of any visit is written anywhere.
• No analytics, no trackers, no third-party scripts. The only thing counted is an optional one-question survey with no account attached to the answer.
• Referrer-Policy: no-referrer on every response, so leaving this site tells the next one nothing.
• Console transcripts: off. The hypervisor does not keep what your server prints to its serial port. A per-server switch in the panel lets you turn it on for debugging, and off again empties it.
• Error and job logs exist for crashes and carry server identifiers, never a visitor address, a user id or an invoice.
• What is kept: your credential hash, your balance, your services with their addresses and expiry dates, invoices, and the support messages you send us. Notifications older than 90 days are pruned.
• Payments: crypto on our own nodes with a fresh address per invoice; cash by mail in any currency; cards through Stripe with no metadata and no description attached to the charge.
• Reachability: the site is mirrored as a Tor onion service and an I2P eepsite, listed in the footer, for people who would rather not show up on the clearnet at all.
• Warrant canary: PGP-signed and re-issued regularly at /canary/.

Every Blackbox runs on hardware we own in our own rack in Montreal, with the same confidential computing, the same absent agent and the same encryption options at every tier. Every machine includes a dedicated IPv4 and a routed IPv6 /64 on a 10 Gbps port, with 4 TB of transfer per 31-day period on Core, doubling with each tier. Past the allowance the port runs at 10 Mbps until the period rolls over; nothing is billed and nothing is switched off. Terms run from 7 to 365 days, billed pro rata.

The standard line (from $15.59 a month in eight locations) shares the account model: no identity, the same payment rails, the same absence of access logs. It runs on hardware we do not control, so it has none of the hardware guarantees above. It is a no-KYC VPS; Blackbox is the privacy VPS.

A confidentiality claim is worth exactly what its limits are worth. These are ours, and anyone selling a privacy VPS who does not list theirs is hoping you will not ask.

• Your traffic is visible in transit. We route your packets, so unencrypted traffic can be seen on the wire here like it can be everywhere else. Encrypted memory is not anonymity for your connections; use Tor, a VPN or end-to-end encryption for that.
• Confidentiality is not availability. We can stop, refuse to run, or delete your machine. Encryption stops us reading your data, not withholding the service. Keep backups somewhere that is not us.
• The image before you encrypt it is our stock Debian or Ubuntu cloud image and is readable by the host until the encrypt step runs at first boot. Encrypt before anything on the disk has run.
• Without measured boot you are trusting our image. It is on by default for new Linux Blackbox orders; an older machine gets it through a reinstall.
• Side channels are an open research area. SEV-SNP stops the hypervisor from reading or corrupting guest memory. It does not claim to close every microarchitectural side channel, and published attacks exist. Against a determined operator running dedicated research on your specific VM, no commercial confidential computing product is a complete answer today.
• Canada is a Five Eyes country. We do not sell the jurisdiction as a feature. The design assumes a request could arrive, and is built so that what could be handed over is ciphertext and billing metadata.

The workloads where the provider being unable to look inside actually matters: a Tor relay or bridge, a Monero node or wallet server, a WireGuard exit, a password manager, a Matrix homeserver, a Mastodon instance, a Nextcloud holding files you would not put on a cloud drive, a Pi-hole for a household, or an AI agent with your API keys in its config. If the first question about your project is "who else can see this", the answer here is nobody, and you can check.