What no-KYC hosting actually means

Email or token plus a 12-character password buys a server - no ID step at any spend. What the host stores on a $6/mo Core, and what stays upstream.
Email or token plus a 12-character password buys a server - no ID step at any spend. What the host stores on a $6/mo Core, and what stays upstream.
KYC is a banking habit, not a hosting rule
Here is the assumption worth discarding first: that identity checks at checkout are somehow required of everyone and this company merely forgot them. They are not. Duties to verify customers - KYC in industry shorthand - belong to banks, payment institutions, and money transmitters, all licensed animals, and renting compute is none of those in the jurisdictions where the racks physically stand. A vendor who never asks who you are is not dodging anything; it is selling hardware time the way an electronics counter sells drives, receipt and all, minus the interrogation.
The confusion has an origin worth naming. Cards and European bank transfers drag a regulated middleman into every purchase, that middleman is legally compelled to profile its customers, and shoppers grew used to meeting the passport scan at the till without asking whose requirement it was. The obligation binds the financier, never the landlord of the machine. RFC 6973 argues the opposite direction for the internet at large, cataloguing what pervasive identification costs a network's participants - context the checkout here takes seriously.
Settling in coin removes the middleman and, with him, the profiling. Nineteen assets clear an order here - XMR when discretion matters at the rail itself, USDT-TRC20 when the quoted dollar sum should hold still - and the money leg ends the moment a matching transaction appears on chain. Nobody grades the sending wallet, because no grading product exists on this side of the counter. The account that owns the machine is a string you type, not a person the vendor knows.
One boundary needs stating before anything else, because buyers routinely misread it. None of this reaches backward: coins bought at an exchange that photographed your face carry that photograph in someone else's archive forever, and a domain registered under a company name broadcasts it publicly. What a credential-only shop promises is narrowly about its own shelves - what it writes down, and what it never asks. The next section puts that promise into two form fields.
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowTwo fields, no third
Enrollment takes an address - a mailbox or an anonymous token - and a secret of at least 12 characters. Nothing else exists: no utility scan, no selfie against a blank wall, no SMS loop, and crucially no spending tier that unlocks a document demand later. The form you complete at minute one is the form you would complete at year five. The address exists purely so SSH credentials and bills have somewhere to arrive, which is the only job it ever does.
Pick a plan, a term, one of a dozen facilities, an operating system image; the invoice credits; a VPS boots roughly a minute afterwards. Metal adds a racking wait of 2-4 hours before IPMI reaches your hands. At no point does the flow branch on identity - no pre-boot questionnaire, no agent reviewing your file, no verification call. Support, should you ever need it, works from the credential you present; the requirements-and-limits guide maps exactly what that credential carries.
Order Core at $6/mo ($4.80/mo on the annual term) and study the form while doing it: identical to what a dual-EPYC buyer sees. That sameness is the property worth paying for, because onboarding that grows a passport step once an invoice passes some threshold was never privacy-conscious commerce - it was ordinary verification wearing a discount for small accounts. Here the login is a pseudonymous handle plus a passphrase, identical in kind from the smallest instance to the largest rack, without mutation.
The trap: choosing a mailbox you do not really own. Shared throwaway domains die without notice, and thousands of strangers hold keys to the same front door; an alias on a domain you control survives. The provisioning message is the sole key handed over at delivery - mislay it and recovery runs through a human, on the clock, rather than through a reset tied to a number you never gave. Signup, though, is only the public-facing half; behind it sits the retained record the shop keeps, and that inventory comes next.
The dossier, itemized
Vendors claiming they retain nothing are describing an impossibility: a shop that stored no access credentials could never let you back in, and one that kept no billing rows could never reconcile a chain credit. The defensible formulation is narrower and actually stronger - the stored record contains nothing that maps to your legal person unless you typed your name into it yourself. Four items survive an order here, and each answers a question an auditor would ask.
Item one, the login handle with its salted one-way hash, so returning sessions keep working. Item two, the billing rows: plan, term, facility, amounts, dates. Item three, the txid values proving which on-chain transactions settled which bills. Item four, network metadata - that a socket opened, when, at what volume - kept no longer than 24 hours for abuse disputes under the facility's legal system. Nothing deeper exists: no payload capture, no guest-side trail, no scoring product grading arriving wallets. The minimum-data checkout guide walks this inventory field by field.
That fourth item deserves precision, because summaries blur it. Connection metadata is the envelope, never the letter: timestamps and byte counts an abuse team can match against a complaint, expiring within a day of arrival. What is never written down is anything reconstructing activity inside the machine - no keystrokes, no payloads, no per-URL histories. Learn to hear that distinction on rival pages too; 'minimal logs kept' means nothing, while 'envelope for a day, letter never' is a sentence somebody can actually be held to.
Where buyers sabotage this themselves: volunteering what was never asked. A legal name typed into a profile field, a reverse-DNS record pointing at a corporate hostname, a ticket narrating employment details to whoever happens to be on shift - the archive only stays clean while its owner keeps it clean, and no deletion policy rescues volunteered data retroactively. With the shop-side inventory now itemized, the leftovers live in two places no hosting policy can touch, and those places come next.
Two archives you do not control
The exchange where coins were bought kept its file the day you onboarded there; the registrar holding your domain keeps its own, and both answer to rules entirely outside any hosting relationship. A WHOIS entry carrying a legal name publishes that name to every passer-by with a lookup tool, and an identified exchange's records outlive the exchange itself in some jurisdictions. A papers-free vendor can be spotless and still leave these two doors swinging open behind you.
Each door has a known fix, applied at acquisition time. Coins: buy for cash, mine, or route through a rail engineered for unlinkability - XMR obscures amounts and counterparties at the protocol level, as the Monero project's documentation explains, and the dedicated Monero page turns that into a payment walkthrough - rather than wiring from an exchange account in your own name. Domain: use a registrar with redaction, or skip naming entirely and hand out an onion address. Whatever layer you leave sloppy is the layer any curious party reads first, because it is the cheapest one to read.
Protocol research says the same thing at a lower level: metadata betrays what content conceals. RFC 7258 classifies pervasive monitoring as an attack rather than a nuisance, and the practical translation is blunt - encrypt the transport with TLS or route it through Tor, and apply the same skepticism to how the bill was funded that you apply to disk encryption. A single hardened layer never rescues a careless neighbor; investigators and adversaries both walk the path of least resistance, every time.
The self-inflicted version looks like this: coins withdrawn from an identified exchange straight to a machine whose hostname is the company name, then astonishment when a report connects the dots in an afternoon. Privacy is assembled, not inherited, and every component gets chosen at purchase time while choices are still cheap. The vendor side of the ledger is now fully mapped - enrollment, dossier, outside archives - which raises the question newcomers always ask: does any of this bend when the order grows from an instance to a rack?
Racks obey the same two-field rule
They do not bend. A dedicated order clears through the identical nineteen-asset checkout into an identical document-free login, and no threshold of invoice size summons a papers request. What scales is hardware and logistics: assembly takes hours, ECC memory arrives, disk arrays get built, and IPMI is released at the end of it - but the login that opens that console is still a handle plus a passphrase. Bigger metal, same intake.
Buy the Forge at $49 list ($39.20 annual-eff) when a 16c/32t Ryzen 9 with twin 1 TB NVMe suits the job; step to Summit, or to the dual-EPYC Monolith with 4 x 2 TB of flash, and the intake form does not gain a line. Every tier ships console access plus the standing DDoS shield as standard equipment. Pricing here attaches to silicon and disks, never to persons - precisely the property the label promises, and precisely the property worth re-checking on any rival's order page before wiring them anything.
Delivery is where the equality becomes tangible. Console access lands in the same handle-and-passphrase login after assembly; nobody requests a scan before the out-of-band console unlocks, and a reimage performed through it requires no ticket and no voice call. The RAID layout is built before hand-over, so first login finds a blank machine in the geometry you ordered rather than somebody else's golden image. Trust at this boundary is a property of the design, not of a checklist somebody performed on your behalf.
Logistics differ, though, and honestly so. An instance boots from a template that already exists, hence the minute; metal involves humans and screws, hence the multi-hour span before the mail arrives. Dispute handling also reads differently - an instance shares a chassis with strangers, while a rented rack is a single-tenant relationship under one facility's law. Neither difference has anything to do with identity; both belong to the category of delivery, which is the only category a tier should ever change. Suspicious of other shops' claims? The next section hands you a three-probe test.
Three probes for a rival's promise
Marketing copy cannot be trusted with this claim; order flow can. Probe one: does any spend level, any plan, any renewal summon a request for ID documents? Probe two: does the shop accept cards or bank rails at all - because those rails cannot operate without profiling their users? Probe three: does the privacy page enumerate exactly which records exist and how long each survives, or does it gesture at virtue? Run the probes in order; the first usually ends the evaluation.
Probe two cuts deepest. Card acceptance is not a payment option, it is a company with a license wedged into the middle of the sale, and that company is legally obliged to know its customers regardless of what the shop promises on its own pages. A catalog advertising BTC while onboarding through a processor has simply relocated the interrogation one firm over. The same holds for SEPA transfers and verified-wallet flows; the FATF standards name exactly who is compelled to identify whom, and the license trail always ends at a form field.
Probe three separates commitments from moods. Respect for privacy and minimal data are attitudes - rewordable by the next intern, meaningless in a dispute. Falsifiable sentences look like the privacy page here: what persists (an access string, its one-way digest, billing rows, transaction references, a day of connection envelopes) and what is never written down (payloads, guest-side trails). Prefer vendors who can be wrong in public, because only they can be corrected in public; bookmark the page and re-read it quarterly, since inventories drift exactly as quietly as signups do.
The composite failure is common enough to have a shape: a privacy-flaunting homepage, a card icon in the footer, and a chat agent requesting documents the moment a billing dispute opens. All three coexist happily on one site, and only the trio of questions catches the combination. Auditing costs ten minutes per vendor and belongs in every buyer's routine. That leaves the final decision in the chain - where the machine physically sits - which changes the answer to a different question entirely: not whose files exist, but whose courts can read them.
The flag writes the ending
Disputes, complaints, and legal process are answered under the law of the facility, which turns the geography picker into a menu of legal systems. Reykjavik sits under Iceland's tradition of no compelled retention; Stockholm inherits a press-freedom heritage; Amsterdam and Frankfurt answer under GDPR; Singapore and Tokyo run their own statutes; the offshore guide reads that same map with a different lens. Signup is identical at every flag - the divergence lives entirely in who can compel what, from whom, and how noisily.
Four flags cost extra, openly: Iceland +20%, Norway +20%, Switzerland +35%, Luxembourg +15%, with everything else at base list. Those surcharges exist because customers pay for legal texture - no mandated retention in one, a non-EU data statute in another, a data-trust framework in a third - and the premiums are the clearest market signal of which regimes buyers actually want. The locations table lists tier, uplink, and governing law per city, which is the reading this particular decision deserves.
Latency still votes, so weigh both axes honestly. EU audiences are served briskly from Frankfurt or Amsterdam; Southeast Asian readers sit nearest Singapore or Tokyo; a personal box nobody else touches belongs wherever the statute suits and ping is irrelevant. One price covers all cities bar the four surcharged ones, so geography gets decided on law and round-trip, never on billing - the invoice arithmetic is identical everywhere else. Choose the regime deliberately; check the ping afterwards; in that order.
The blunder: sorting by price, then acting surprised when a GDPR regime answers a takedown the way GDPR regimes do, or parking compliance-sensitive material under a retention statute nobody bothered to read. Disputes follow the facility's law from the day the invoice clears; your data inherits a legal system along with an IP address. Signup, dossier, outside archives, rack parity, rival auditing, regime - every component now sits on the table, and the closing section assembles them into a single runnable pass.
The no-KYC hosting setup, in the order to run it
Begin with geography, the one decision that cannot be revised later without migrating. Read the locations table - tier, uplink, statute for each of twelve cities - and select the regime matching your exposure, paying a premium only where the law itself is the point. Configure plan and term second; the entry machine covers most single-purpose deployments, and the annual term is the cheapest way to hold territory you intend to keep. Only then approach the form.
Complete the intake with an inbox you control for the machine's whole life - the provisioning message is the only key ever issued - and choose the paying asset with the same scrutiny you spent on the flag, since coins carry their acquisition history with them. A VPS boots roughly a minute after the chain credit; 2-4 h of assembly precedes metal's IPMI hand-over; a 12-character secret opens both. Nothing in the pipeline has asked who you are, and nothing downstream will.
While the machine builds, decide what the public record will say. Keep names out of profile fields, hostnames, and reverse DNS; register domains behind redaction or hand out onion addresses instead. At first login, inventory everything installed - the guest's own configuration is now the largest privacy surface under your control, and leaking it is nobody's fault but yours. Patch promptly, firewall tightly, and administer only over channels you would happily explain: keys rather than passwords, ssh(1) rather than a web panel.
Then audit the promise with the three probes: no papers requested at any spend, no card rails anywhere in the checkout, a privacy page stating its inventory in testable sentences. Any drift - a threshold demanding documents, a processor appearing at settlement, a rewritten retention clause - is a product change and deserves treatment as one. Ten minutes per quarter covers the whole check, and it remains the cheapest insurance attached to this entire purchase.
The whole pass, compressed: regime first, configuration second, credential intake third, funded-coin scrutiny fourth, record hygiene fifth, quarterly re-audit sixth. Privacy here is a chain of small personal decisions, each owned by you, each cheap at purchase time and expensive afterwards. Snap any single link and the remaining links labored for nothing - which is exactly why the sequence, run straight, is worth memorizing.
Is a disposable email address acceptable?
Yes, provided the inbox genuinely receives mail - the provisioning message and every subsequent bill land there. Shared throwaway domains evaporate without notice, so an alias under a name you administer is the durable option.
Do dedicated servers require ID?
No. Rack orders pass through the same document-free intake as instances, and the out-of-band console unlocks after the multi-hour assembly window. No invoice size triggers a papers request, and the form acquires no fields as the price climbs.
Does no-KYC mean zero data is kept?
No - a vendor archiving nothing could neither authenticate return visits nor reconcile on-chain settlements, so any such boast is fiction. The truthful inventory: a mailbox or token, a salted digest of the passphrase, billing rows, transaction references, and at most a day of connection envelopes. Nothing naming you enters it uninvited.
Does the checkout screen wallets or run AML checks?
It does not. Settlement logic observes an amount and a network, waits out the required block depth, and never grades the sending wallet - no scoring product exists on this side of the counter, so there is no dossier to hand a third party either.
Can KYC start later, above some spend?
Not here. No threshold activates a papers request, no tier carries a separate intake, and no clause ties policy to invoice size. Your login stays a handle plus a passphrase from first minute to last - the exact property worth re-testing quarterly on any vendor you use.
Primary sources
More ways to pay
Pay with Bitcoin · Pay with Monero · Pay with USDT (TRC-20/ERC-20/SPL) · Pay with Litecoin · Pay with Ethereum · Pay with Solana · Pay with x402 · Pay with Dogecoin · Pay with XRP · Pay with TRX · Monero on bare metal · Dedicated servers with crypto · Pick the jurisdiction first.
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.