Anonymous VPS and VDS in eight locations, and Blackbox: a VPS whose memory not even the host can read. Pay in crypto, cash or card. We never ask who you are.
Memory encrypted by the CPU with AMD SEV-SNP, a LUKS2 disk behind a passphrase only you type, no guest agent, and a boot chain the CPU measures and signs. No logs and no KYC, at a price you would pay for an ordinary VPS.
$blackbox-verify--host203.0.113.7 # on your own computer
reported measurement match
verdict OK
$sshroot@203.0.113.7 # the box waits in its initramfs
Please unlock disk root_crypt: ********
Disk unlocked. Booting.
$sshroot@203.0.113.7 # same machine, now running
$dmesg|grep-i"MemoryEncryption"
Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP
$ls/dev/virtio-ports/
ls: cannot access '/dev/virtio-ports/': No such file or directory
$
› type the passphrase only over SSH, after a PASS
A terminal session. First, on your own computer, the verifier: $ blackbox-verify --host 203.0.113.7; reported measurement match; verdict OK. Then the unlock: $ ssh root@203.0.113.7; Please unlock disk root_crypt: ********; Disk unlocked. Booting.; $ ssh root@203.0.113.7; $ dmesg | grep -i "Memory Encryption"; Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP; $ ls /dev/virtio-ports/; ls: cannot access '/dev/virtio-ports/': No such file or directory.
Measured boot
Don't trust it. Verify it.
With measured boot, a Blackbox never boots from its own disk. Firmware, kernel, initramfs and command line go into one launch measurement the CPU signs, and you check it from your own computer before the passphrase leaves your keyboard.
U1measured boot · AMD SEV-SNP
1What bootsmeasured at launch
FirmwareOVMF.amdsev.fdbuilt from public edk2 sources
KernelvmlinuzDebian's signed kernel, unmodified
Initramfsinitrd.imgthe program that asks for your passphrase
Command linecryptopts= ip= bb.*carries your SSH key and addresses
2One numbersigned by the CPU
Launch measurement
Change one byte of the four and this number changes. Nothing the host does can make other bytes produce it.
Signed in siliconAMD SEV-SNP · EPYC 7B13
3You check iton your own computer
$ blackbox-verify \
--host 203.0.113.7
signature chains to AMD's root
measurement equals the one you computed
host key matches the signed report
verdictPASS
4You unlock itonly after a PASS
$ ssh root@203.0.113.7 unlock
Please unlock disk root_crypt: ********
Disk unlocked. Booting.
over SSH, never into the console
On a fail
Do not type it. The machine is not what it claims to be.
Eight guarantees
Eight things your current VPS does not do.
Every one of them is on by default or one click away, on every size.
Guarantee 01
Encrypted storage and RAM
Memory is encrypted by the CPU with AMD SEV-SNP, under a key that never leaves the chip. Nobody can read it, even from the hypervisor. The disk is LUKS2, with a passphrase only you ever type.
Firmware, kernel, initramfs and command line are part of a launch measurement the CPU signs. Change a byte and the number changes, and the verifier refuses before you type your passphrase.
An ordinary VPS has an agent inside that the host can use to reset root, run a command or read a file. A Blackbox has none, and no virtio port for one. That is why there is no reset-password button.
Hand the node your own UKI by URL and SHA-256, write your own pre-encrypted disk image over the volume, or boot any ISO. On a measured machine the CPU measures your bytes, not ours.
A dedicated IPv4 and a whole /64 of IPv6 routed to your machine. Eighteen quintillion addresses that are yours alone.
2001:db8:0:149::/64routedtoyourVM
Guarantee 06
BYOIP and BYOASN
Announce your own RPKI-verified space over the network, or run your own BGP session with transit and originate your prefixes yourself. Panel buttons, not tickets.
AS64500 · 198.51.100.0/24
your BGP session, our transit
announced from your Blackbox
example ASN and prefix
Guarantee 07
Reverse DNS you set
Set rDNS for your IPv4 and IPv6 from the panel, live within a minute. Mail servers need it; you do not need us for it.
$dig-x203.0.113.7+shortmail.example.com.
Guarantee 08
Abuse reports read by a person
Run a Tor relay, a VPN exit or a mail server and reports will come, most automated and many wrong. A human reads every one and talks to you first. No script suspends you because a blocklist said so.
a report arrives
a person reads it
you hear first
Four sizes · Montreal
Same silicon at every size.
Every tier is protected identically: same silicon, same encryption, same keys nobody else holds. Core, Plus, Max and Ultra differ only in size.
Montreal, Canada · dedicated hardware in a colo4 tiers · 4 in stock
Transfer is counted as the larger of inbound or outbound, never both. Past the allowance the port slows to 10 Mbps instead of billing you.
What it does not protect
The honest limits.
Encrypted memory hides what is on the machine. It is not anonymity, and it does not hide that the machine exists.
The console
Serial and VNC pass through the host. Watch the boot there; never type a secret into it.
Metadata
Traffic volume, packet headers, CPU use and the fact the machine exists are visible, as at any transit provider.
The first boot
The root filesystem starts as a stock image the host could read. Encrypt it at first boot, or write your own pre-encrypted disk.
We can stop or delete the machine.We cannot read it.
Signup, side by side
A root shell, without telling anyone who you are.
Both start from nothing. absolute generates a credential, takes the payment and has the server live in about 30 seconds. A typical cloud wants your name, phone, card and passport, then stops to check them.
U1
two signups · both from nothing
absolute.example/orderreadyrunningdone
New accountno email, no password
credential generatedq7XkR2mVd9LpW4tBn3cF8hJs6yZa1GeTq7Xk••••••••••••••••••••••••••••the whole account. no email, no phone, no KYC.
pay 0.0333 XMR to 8Bx…f3Qafresh address, this invoice only · example rate
watching a self-hosted node…
payment seen on a self-hosted node
provisioning
server live at 203.0.113.7about 30s after payment · waiting in its initramfs
your own terminal
$blackbox-verify--host203.0.113.7
PASS · measurement matches the release
$sshroot@203.0.113.7encrypt
passphrase: ********only you ever type it; nobody can recover it
encrypting in place
LUKS2 on disk · booting
root@blackbox:~#
› no email, no phone, no KYC› live in about 30s, no name on file0 fields
absolute
~30s
From payment seen to a live server. The credential is the whole account.
cloud.example/signupreadyfillingstopped
Create your accountall fields required
Full name*MK
Email*m.k@.
Password*••••••••••••
Phone (SMS code)*+812·418207
Card number*40417
Billing address*Rd,
Date of birth*19--
Government ID (upload)*uploading…passport.jpgin review
Selfie (liveness check)*
Company*
Use case*
Stopped for an identity check. Review can take up to 72 hours.
0/111/112/113/114/115/116/117/11continue →waiting on review
a typical cloud
stuck at 7 of 11
Name, phone, card and birthday go in. Then a passport scan, and up to 72 hours of review.
absolute, in its order page and then your own terminal. It generates a 32-character credential, which is the whole account, and masks it; takes Blackbox Core in Montreal at $9.99 a month; asks for 0.0333 XMR, at an example rate, to a fresh address used for this invoice only; sees the payment on a self-hosted node; and has the server live at 203.0.113.7 about 30 seconds after payment, waiting in its initramfs. On your own computer, blackbox-verify --host 203.0.113.7 reports PASS: the launch measurement matches the release. Then ssh root@203.0.113.7 encrypt asks for a passphrase only you ever type, encrypts the disk in place with LUKS2, and boots to a root prompt. No fields, no name on file. A typical cloud, in a signup form with 11 required fields: Full name, Email, Password, Phone (SMS code), Card number, Billing address, Date of birth, Government ID (upload), Selfie (liveness check), Company, Use case. It takes the first 7, uploads a passport, then stops: identity check pending, review can take up to 72 hours.
Shown with Monero at an example rate. BTC, LTC and XMR get a fresh address per invoice; ETH, TRX, BNB, USDT and USDC draw from a small pool, one open invoice per address; every coin is watched on self-hosted nodes. Cash by mail asks for nothing more. A card goes through a card processor, which handles the card and sees the amount and an opaque customer record, never the plan or the server.
What hosts keep on you
Subpoena us for a name and you get an empty table.
A typical cloud keeps all 14 things below on every customer, long after they cancel. absolute asks for none of them. Two can exist only by your choice: a support ticket if you open one, a card processor ID if you pay by card.
records · read-only
records=> select name, email, ip
records-> from customers
records-> where email is not null;
name | email | ip
------+-------+----
(0 rows)records=>
Customer records, by host
kept on file
only if you choose
not kept
Hostemailsignup IPlogin IP historycard processor IDsupport ticketslegal namephonecard numberbilling addressdate of birthID scanselfieaccess logstraffic flow logsKept
absolute
Never asks who you are. Keeps a support ticket only if you open one, and a card processor ID only if you pay by card.
not keptnot keptnot keptkept only if you choosekept only if you choosenot keptnot keptnot keptnot keptnot keptnot keptnot keptnot keptnot kept0by default
A ‘privacy’ host
Skips the ID check, but wants an email and logs every login.
Rows are composites, not named companies: what each kind of host typically asks for at signup and still holds after you cancel. On absolute’s row, no email, phone, name, address or ID is ever asked for, and neither visitor IP addresses nor traffic are logged. Delete the account and every record naming it goes; invoices stay as anonymous amounts and dates.
Servers
Built so there is nothing to find.
Six things every plan includes, in all eight locations. Plans start at $9.99 a month.
Install anything. No managed-hosting guardrails. Reinstall to another OS from the panel.
access: root or RDP, systems: 8, reinstall: from the panel
U4renewal
billingpanel
renew every14 daysdelete
day 18152229
7-day minimumprorated
renew every 14 daysor whatever cycle you set
renewed
deletedthe job was done
7-day minimum, prorated
renew every 14 days, or any cycle
renewed
deleted when the job was done
Custom renewal cycles
Seven-day minimum, prorated, then renew on whatever cycle you set. Delete it the moment the job is done.
minimum: 7 days, prorated, cycle: yours to set, account with no balance or services: deleted after 24 h
U5logs
access.logCustomLog /dev/null
203.0.113.51GET /servers 200
203.0.113.8POST /order 302
203.0.113.97GET /panel 200
203.0.113.23POST /invoice 200
203.0.113.140GET /canary 200
203.0.113.66GET /status 200
203.0.113.51GET /servers 200
203.0.113.8POST /order 302
203.0.113.97GET /panel 200
203.0.113.23POST /invoice 200
203.0.113.140GET /canary 200
203.0.113.66GET /status 200
/dev/null
packet inspection: none
flow logs: none
No traffic logging
No packet inspection, no flow logs, no activity monitoring. Web access logs go to /dev/null.
web access logs: /dev/null, packet inspection: none, flow logs: none
U6ipv4
203.0.113.0/24shared: never
203.0.113.24· dedicated, yours
transferstandard line
unmeteredcap: none
Dedicated IPv4 on every plan
Never a shared address. The standard line is unmetered.
ipv4: dedicated, standard line: unmetered, blackbox: 4 TB–32 TB / 31 days
Locations
Eight locations. Your browser picks the nearest one.
New York, Montreal, four cities in Western Europe, Singapore and Hong Kong. Every plan in every one of them has a dedicated IPv4 and full root or RDP. No packet inspection, no flow logs.
Montreal runs on owned hardware in a colo, and it is the only place a Blackbox lives: SEV-SNP encrypted RAM, a LUKS2 disk only your passphrase opens, measured boot.
U1Coverage130°W–150°E · 10°S–72°N
Inset · Western Europe
Guessing the nearest location from your clock…YUL 45.5°N 73.6°W
The nearest location is guessed from your time zone, here in the browser: no IP lookup, no location prompt, nothing sent. Pick a row to pin it on the map. Prices are per month; stock is a snapshot and changes. Land: Natural Earth, public domain.
Pricing
You pay for the machine. Nothing else is for sale.
Every plan in every location, priced per month. Rent for as little as seven days. Stop renewing and the server expires: expired services are removed along with their data.
Location
YULCanada
Montreal
Owned hardware in a Montreal colo. Home of Blackbox: SEV-SNP, LUKS2, BYOIP, rDNS.
PlanCPUMemoryStoragePortTransferPer month
Blackbox · Zero-knowledge VPS
Transfer is counted as the larger of inbound or outbound, never both. Past the allowance the port slows to 10 Mbps instead of billing you.
# the fingerprint matches the one above. Good until 2026-11-30.
01
One key
Every canary is signed with the same ed25519 key. Check the fingerprint gpg prints against this page; a new key would mean something happened.
02
A fresh block hash
Each one names a recent Bitcoin block, when it was mined and its hash, so it can't be written in advance and left on a timer.
03
Two mirrors
The same file is published on the clearnet site and the onion address. Fetch both; diff should print nothing.
04
A missed month
If a month is missed, the file disappears or the signature fails, don't wait for an explanation. There won't be one.
Questions
We answer the question, not the person.
What people ask before they pay. None of it needs your name.
Anything elseU1
Open a ticket from the control panel, over its onion address if you like. It doesn’t ask who’s asking either.
panel
absolutexq7…onion
asker
one 32-character credential
You set up a server without handing over a name, an email address or a phone number, and there is no KYC: a randomly generated 32-character credential is the whole account. That covers what we learn. What your server gives away is up to you, because privacy stays a shared responsibility: use key-based SSH and strong passwords, and don’t run scripts from sources you don’t know. The panel has an onion address if you’d rather it never saw your IP either.
No traffic logs: no packet inspection, no flow logs, no activity monitoring, and the web server’s access log goes to /dev/null. What is stored is what an account needs to work: the credential, your balance, invoices (amount, method, time), the address each crypto payment was sent to, your servers’ configuration (hostname, IP, OS, specs, expiry) and your support tickets. An account with a zero balance, no services and no open tickets is deleted after 24 hours. The canary says whether anyone has asked for any of it.
Crypto (XMR, BTC, LTC, ETH, TRX, BNB, USDT, USDC), watched on self-hosted nodes, with a fresh address per invoice on BTC, LTC and XMR. Cash by mail, with the credential in the envelope rather than your name. Or a card, through a processor that sees an amount and an opaque customer record, never what it was for; its card form does see your IP, as any processor’s does. Once the payment is confirmed the server is live in about 30 seconds, credentials in your panel. Nobody reviews you first.
A VPS shares its host’s resources and is the budget line, from $15.59/mo in 5 locations. A VDS keeps its cores to itself, from $16.79/mo in 5 locations. Both are unmetered with a dedicated IPv4. Blackbox is the zero-knowledge VPS: AMD SEV-SNP encrypted RAM, a LUKS2 disk only you can unlock, measured boot and no guest agent, in Montreal, from $9.99/mo with 4 TB of transfer per 31 days on Core. If the host should be unable to read the machine, it’s Blackbox.
Because it needs the whole stack, down to the CPU, the firmware it boots and the network that routes your addresses. That only exists on the owned hardware in a Montreal colo, which is also where LUKS2, bring-your-own IP and ASN, and reverse DNS you set yourself live. The other 7 locations sell the standard VPS and VDS lines.
No. There is no guest agent inside a Blackbox and no virtio port for one, so the host has no way to run anything in it. That is the point, and why there is no reset-password button. The disk is the same: you type the LUKS2 passphrase yourself, over SSH, after blackbox-verify prints PASS. Lose it and nobody can recover the data, us included. Keep it somewhere that isn’t the server.
Core includes 4 TB per 31 days and each tier doubles it (Plus 8 TB, Max 16 TB, Ultra 32 TB). Transfer is counted as the larger of inbound or outbound, never both. Past the allowance the port slows to 10 Mbps instead of billing you. The standard VPS and VDS lines are unmetered.
Yes. The minimum is seven days, prorated; after that, renew on whatever cycle you set, or delete the server the moment the job is done. Deleting the account destroys every server and every record naming it; invoices stay as anonymous financial records (amount, method, status, dates).
Debian 12 and 13, Ubuntu 24.04 LTS and 26.04 LTS, Rocky Linux 9, AlmaLinux 9 and 10, CentOS 10, FreeBSD 14 and 15, OpenBSD 7.8 and 7.9, Windows Server 2022 and 2025. Full root or RDP from the first minute, and reinstall to another from the panel whenever you like. A Blackbox also boots any ISO, your own kernel as a UKI, or a disk image you built and encrypted at home.
On a Blackbox, a person, every time. Run a Tor relay, a VPN exit or a mail server and reports will come, most of them automated and many of them wrong. A human reads each one and talks to you before anything happens to the machine. No script suspends you because a blocklist said so.