What KYC looks like at a hosting company
Know Your Customer is a banking term, but hosting companies have built their own versions of it. The obvious one is a request for a government ID or a selfie before a server is handed over. The less obvious ones are the forms you fill in without thinking: full name, billing address, phone number with an SMS code, and a card whose billing details must match the account. Behind the form there is often a fraud-scoring service that compares your IP, your email domain, your card country and your browser fingerprint, and a high score triggers a manual review that ends with "please send a photo of your ID".
So "no KYC" is not a yes-or-no label. A host can genuinely never ask for ID and still hold your name, address and phone number in an account you were required to create. Another can ask for nothing but an email and still reserve the right to verify "higher-value" orders. The useful comparison is what the host requires at signup, what can trigger a later check, how you pay, and which law the company sits under.
How to evaluate a no-KYC claim
- Read the terms of service and the billing knowledge base, not the landing page. Verification policy lives in clauses about fraud, chargebacks and PayPal, and that is where "we may request" sentences hide.
- Try the order form over Tor before you pay. If it refuses to load, demands a phone number, or silently scores the order for manual review, you have your answer without spending anything.
- Separate account from identity. An email-only account is close to accountless in practice. A name field that accepts a pseudonym is fine. A phone field that sends an SMS is identity.
- Match the payment method to the claim. A host that says "no KYC" but takes only cards and PayPal is relying on the payment network to know you. Crypto, and especially Monero, is what makes no-KYC meaningful.
- Check the datacenter jurisdiction separately from the company jurisdiction. Where the server physically sits decides what law applies to its contents and traffic.
- Look at what happens on non-payment. Crypto hosts cannot charge you automatically, so the grace period, suspension and deletion timeline is part of the service model.
Hosts compared (as of October 2026)
The rows below were checked against each provider’s own terms, FAQ and order pages in October 2026. They describe mechanics only. No prices, no judgement of quality; a provider that asks for more at signup is not necessarily a worse host, it is a different fit.
| Host | Account required | What signup asks for | Verification policy in published terms | Payment methods | Company jurisdiction | Server locations |
|---|---|---|---|---|---|---|
| Njalla | Yes | Email or XMPP address and a password | Terms list email/XMPP and password as the only data collected | BTC, LTC, XMR, ETH, PayPal | Costa Rica (Njalla SRL) | Sweden |
| 1984 Hosting | Yes | Email, confirmed by link | No ID step described in FAQ or signup page | Cards, PayPal, BTC, XMR | Iceland (1984 ehf) | Iceland |
| Privex | Order form | Name (may be a pseudonym) and email | No ID step described; Belize residents excluded | BTC, BCH, LTC, XMR, DOGE, HIVE, HBD, EOS; no fiat | Belize (Privex Inc) | SE, NL, DE, FI, US |
| IncogNET | Yes | Email only (forwarding addresses allowed) | Terms state email is the only required information | BTC, XMR, LTC, DASH, DOGE, other coins via Trocador, PayPal, cards | United States (IncogNET LLC) | US and Europe |
| FlokiNET | Yes | May request additional verification for higher amounts; PayPal email may need to match | XMR, BTC, LTC, ZEC, ETH, USDT, bank, PayPal, cards, cash by post | Iceland (FlokiNET ehf) | IS, RO, FI, NL | |
| BuyVM (Frantech) | Yes | Account with billing details | Terms require account details to match the payment method; PayPal must be a verified account | BTC, LTC, DOGE via BTCPay Server, other coins via Cryptomus, PayPal, cards, Alipay | Canada (Frantech Solutions) | US and Luxembourg |
| BitVPS | No | Email for the access link | No verification step; no name, address or phone fields | BTC, XMR, ETH, SOL, other coins, cards | United States | DE, FI, US, SG |
Notes on the table
- Njalla’s terms say the only data it collects is the email or XMPP address and password you set, and that you are not obliged to provide anything else. Its about page states the company, Njalla SRL, is based in Costa Rica; the servers page says the machines are in undisclosed locations in Sweden.
- 1984 Hosting requires an account; the signup page describes an email confirmation. Its FAQ says crypto payment is hidden from visitors who appear to be in Iceland for tax reasons, which is a geolocation check, not an identity check.
- Privex has no conventional account; its about page says it asks for a name and an email, and third-party reviews note a pseudonym is accepted. Its FAQ says it cannot accept cards or PayPal and explains why.
- IncogNET’s terms are explicit that an email address is the only required information and that forwarding services are allowed. It processes several coins in-house.
- FlokiNET’s own blog says any valid email is enough to become a customer; its PayPal knowledge-base article is the place where "additional customer verification details" for higher payment amounts is mentioned.
- BuyVM’s terms require account details to match the payment method and PayPal payments to come from a verified PayPal account. Its September 2026 announcement says it cannot currently accept XMR through its processor. It is included because people searching this topic ask about it, not because it markets itself as no-KYC.
What no-KYC does not change
A host that does not know your name still knows your server. It sees the IP it assigned, how much traffic flows and to where, and whatever an abuse report says about it. Every provider in the table, including BitVPS, has an acceptable use policy and will act on abuse regardless of how you paid. No-KYC removes the identity layer from the billing relationship; it does not make the server invisible and it does not change what is legal in the datacenter’s country. If the destination of the traffic matters, that is a job for Tor or a VPN running on the server, and the other guides on this site cover both.
Where BitVPS sits, honestly
BitVPS is at the accountless end of the table: there is no signup form at all. You choose a plan, location and OS, enter an email, pay, and manage the server through a magic link. Nothing asks for a name, address or phone, there is no fraud-score review, and the onion mirror means the order can be placed without revealing an IP. All plans cost the same regardless of payment method, so there is no penalty for choosing Monero over a card.
What you give up is everything an account would have given you. There is no dashboard of past orders; each server is reached from its own link, and if you lose access to the mailbox you lose the easy way back in. Crypto is prepaid in days with a small per-coin minimum at checkout, there is no crypto auto-renew, and a server is deleted when its paid period ends unless extended (a reminder goes out first). Recurring monthly billing is card-only. Payments are on-chain; there is no Lightning. Six locations, in Germany, Finland, the US and Singapore, is a shorter list than some hosts above offer, and the company operates under US law, which is a feature or a drawback depending on who you are keeping the server away from.
Which plan to pick
The accountless model applies to every plan, so choose by workload. Small services and VPN endpoints fit the BVX11 (2 vCPU, 2 GB, 40 GB NVMe, from $10/mo in the EU) or the BVCX23 (2 vCPU, 4 GB, 40 GB, $11/mo, EU only). Pick the country deliberately: Germany and Finland are the cheapest, and the US and Singapore locations exist for when the jurisdiction or latency matters more than the price. Configure a server, pay with whichever method matches your threat model, and the access link arrives when the payment confirms.