Anonymous VPS hosting is a chain. We are one link.

A server is traceable to you if any link in the chain between you and it can be resolved. There are five, and a provider controls exactly one of them:

1. The payment path — how money got from you to the provider.
2. The registration data — what the provider asked for and stored. This is the link we control.
3. The access path — the network route you use to administer the server.
4. The workload — what the server itself reveals, in logs, headers, certificates and DNS.
5. Operational discipline — reused SSH keys, reused usernames, reused hostnames, and everything else that correlates one identity to another over time.

A provider that removes link 2 entirely, as we do, has done something genuinely useful and completely insufficient on its own. Links 1, 3, 4 and 5 are yours. This page is mostly about those, because that is where anonymity is actually won or lost.

• No identity collection. No name, address, ID document, phone number or payment card exists anywhere in the ordering system. Not optional — the fields do not exist.
• No card payments at all. Cards create a chargeback path, which creates a fraud-control incentive, which creates identity collection. Removing the cause removes the effect.
• Monero accepted. Bitcoin is a public ledger, so a BTC-only provider offers materially less privacy than one taking XMR, regardless of what its front page says.
• 0-day access log retention. No deep packet inspection, no traffic mirroring, no identity-linked NetFlow.
• Our own address space. IPv4 address space announced from our own autonomous system, so no upstream can be leaned on to pull your prefix over our objection. The AS number and its current status are on the network page.
• Tor and VPN traffic explicitly permitted, with a free checkout toggle that flags the server so abuse handling is correct from day one.

Full detail on what is and is not stored is on the no-KYC page.

This is where most people's anonymity actually fails, and it fails before they ever reach a hosting provider.

Bitcoin is not anonymous. It is a permanently public ledger. If you buy BTC on an exchange that holds your passport and send it straight to a hosting invoice, you have created a durable, auditable link between your legal identity and your server. The hosting provider knowing nothing about you is irrelevant — the exchange knows, and the chain is public.

In rough order of effectiveness:

• Monero (XMR), acquired without KYC. Ring signatures, stealth addresses and confidential transactions mean the ledger does not reveal sender, recipient or amount. This is the strongest option available and it is why we accept it.
• Monero acquired on a KYC exchange. Still substantially better than Bitcoin — the exchange knows you bought XMR, but the on-chain path to the invoice is not publicly traceable.
• Bitcoin from a non-KYC source — peer-to-peer, an ATM under reporting thresholds, or earned rather than bought.
• Bitcoin from a KYC exchange. Convenient, and effectively pseudonymous at best. Fine if your concern is data breaches and marketing databases rather than a determined investigator.

All of these work at checkout. We are describing the trade-offs so you can pick knowingly, not steering you.

Your server sees the IP address you connect from, and so does anyone with visibility into that path. SSH from your home connection and the server's own auth log is a record of where you live.

• Use Tor for administration. ProxyCommand torsocks nc %h %p in your SSH config is enough for most people, and costs a little latency.
• Better: run a hidden service on the box. Bind sshd to an onion address and firewall public SSH off entirely. There is a guide in our docs.
• Or chain through a second VPS paid for separately. A jump host in a different jurisdiction, bought in a different session, breaks a single-provider correlation.
• Do not administer from a network associated with you — home, office, or a phone hotspot — even once. A single connection is enough.

Servers are talkative. Common leaks, all self-inflicted:

• TLS certificates. Certificate Transparency logs are public and permanent. A certificate for internal.yourrealname.com on an anonymous server has published the association forever.
• Reverse DNS and WHOIS. Set rDNS to something neutral. Register domains through a privacy-respecting registrar, or use an onion service and no domain at all.
• Application headers and error pages. Default installs leak versions, paths, hostnames and sometimes email addresses in stack traces.
• Analytics and CDNs. Third-party JavaScript reports your visitors — and your admin sessions — to companies that log everything and answer subpoenas.
• Outbound updates and telemetry. Package managers, crash reporters and license checks all phone home with identifiable patterns.
• NTP and DNS. Default resolvers see every lookup the box makes. Run your own resolver or use DNS over TLS to somewhere you trust.

The failures here are boring and extremely common:

• Reusing an SSH key that also authenticates to a personal GitHub account.
• Reusing a username, hostname naming scheme or password across identities.
• Using the same email alias for the anonymous server and for something tied to your name.
• Paying for two "separate" identities from the same wallet.
• Referencing the server in a support ticket from an address that is linked to you elsewhere.
• Deploying with an infrastructure-as-code repository that has your name in the commit history.

Generate a fresh key. Use a fresh alias. Use a fresh wallet. Keep the identities genuinely separate, or accept that they are one identity.

Anonymity is not binary, and the honest question is "anonymous against whom?"

We will not pretend to the last row. Most people are somewhere in the middle, and for the middle the combination of no-KYC, Monero, an offshore jurisdiction and Tor administration is genuinely strong.