Serious hardware.No paperwork.
Dedicated Zen 5 cores, ECC DDR5 and Gen4 NVMe, in thirty-four cities. You pay in coin, you get root in under a minute, and nobody ever asks you for a photograph of your passport.
Five lines. Nothing entry-level.
We deleted the cheap tier in 2021. It was the source of nine out of ten support tickets and every abuse report we ever received.
Why it is quick
Most of the hosting industry sells you a fraction of a core and calls it a core. We do not do that, which is the entire reason our prices start where they do.
The short version: nothing is oversold, and nothing is two generations old.
Fig. 01Node layout, EPYC 9354P host, single socket
Dedicated cores, always
A core you buy is a core no one else is scheduled on. There is no burst credit, no steal time, no noisy neighbour, and no fine print that says otherwise.
Zen 5 and Zen 4, only
Ryzen 9 9950X for single-thread work, EPYC 9354P where core count and ECC matter. Nothing older than the current generation is in production anywhere in the fleet.
DDR5, ECC on the server line
DDR5-5600 on Ryzen nodes, registered ECC DDR5-4800 on EPYC. Memory errors get corrected and logged rather than silently corrupting your database.
Gen4 NVMe in mirrored pairs
Enterprise drives with power-loss protection, mirrored, with a hot spare per node. Reads come off the mirror; writes are acknowledged from cache backed by capacitors.
10 to 40 Gbit/s per port
Ports are dedicated, not shared with the rack. Traffic is unmetered under fair use, and we publish what fair use actually means rather than leaving it as a threat.
Filtering that stays on
Up to 12 Tbit/s of scrubbing at the edge, permanently in path. There is no button to press when an attack starts, because it is already filtering when it does.
Thirty-four cities, twenty-nine countries
Pick the jurisdiction as carefully as the latency. Both matter, and for most of our customers the first matters more.
Latency figures are measured medians from our own probes, not vendor brochures. They move; the page updates when they do.
| Site | Country | Live since | Uplink | Stock |
|---|---|---|---|---|
| AMS-01 | Amsterdam, Netherlands | 2019 | 400 Gbit/s | In stock |
| FRA-01 | Frankfurt, Germany | 2019 | 400 Gbit/s | In stock |
| BUH-01 | Bucharest, Romania | 2019 | 200 Gbit/s | In stock |
| LON-01 | London, United Kingdom | 2019 | 200 Gbit/s | In stock |
| NYC-01 | New York, United States | 2019 | 400 Gbit/s | In stock |
| DAL-01 | Dallas, United States | 2021 | 200 Gbit/s | In stock |
| SIN-01 | Singapore, Singapore | 2020 | 200 Gbit/s | In stock |
What “no KYC” actually means here
A lot of hosts advertise no-KYC and then ask for a scan of your driving licence the first time an invoice looks unusual. Here is the whole of our position, in three sentences.
It is a policy, not a marketing slogan. It is written down, and it is testable.
An email address, and that is all
Sign-up takes an address that can receive mail. Not a name, not a phone number, not a company, not a billing address. Throwaway domains work. So does your own mail server.
No document ever, at any threshold
There is no order value, no payment volume and no support scenario that triggers a document request. If we ever need to introduce one, the warrant canary changes before the policy does.
We keep almost nothing
Panel access logs live for seven days, then they are gone. We do not store payment addresses after settlement, we do not run analytics, and we do not log the traffic passing through your instance.
Everything we hold about an account
Read the full policy| Data | Kept for | Why it exists |
|---|---|---|
| Email address | Life of the account | Password resets and invoice delivery. Nothing else. |
| Password hash | Life of the account | scrypt, N=2^16. Never reversible, never exported. |
| Panel access log | 7 days | Detecting account takeover, then discarded. |
| Invoice records | 24 months | So you can prove what you bought. Contains no identity. |
| Crypto payment reference | Until settled | Matching a payment to an invoice. Purged after settlement. |
| Instance traffic | Never recorded | We route packets. We do not read them. |
| IP address at sign-up | Never recorded | It is not written to disk in the first place. |
Coin in, server out
Thirty-odd assets across the major chains, with the network fee shown before you commit. An invoice confirms as soon as the chain does, and provisioning starts on the same event.
Settlement is handled by OxaPay. We never see a card, and neither do you.
- 01
Choose an asset
Bitcoin, Monero, Ethereum, Litecoin, USDT on four chains, and roughly two dozen more. Pick whichever is cheapest to move today.
- 02
Send once
A single address, valid for that invoice only, with the exact amount and the network fee already accounted for.
- 03
Confirmations clear
Most assets settle in one to three confirmations. The dashboard tracks it live; you can close the tab.
- 04
The server exists
Provisioning fires on the settlement webhook. Root credentials arrive by mail, median forty-seven seconds later.
Balance top-ups work the same way and are the sensible option if you run a lot of small instances — pay once, spend it down, and stop watching the mempool every renewal.
The short version of five years
We have never taken outside money, never been acquired, and never changed who runs the network. That is the whole corporate history.
- 2019
Three racks and a bad idea
Amsterdam, Frankfurt, London and Bucharest, all lit in the same eight weeks. The bad idea was accepting Bitcoin only, which lasted until the first customer asked for Monero.
- 2020
Six more sites, and the first big attack
Helsinki, Zurich, Paris, Warsaw, Chișinău and Miami. A 340 Gbit/s attack in October took AMS-01 offline for eleven minutes and paid for the scrubbing tier we have run ever since.
- 2021
The cheap tier is deleted
We dropped the €4 plan. Revenue fell for a quarter, abuse reports fell by ninety percent, and the support queue emptied. We have sold only high-end hardware since.
- 2022
Zen 4 everywhere
Every node in the fleet moved to EPYC 9004 or Ryzen 7000 within nine months. Six new sites, including Reykjavík and Panama City, opened directly on the new generation.
- 2023
GPUs, and a canary
Passthrough GPU instances in Frankfurt, Dallas and Singapore. The warrant canary started publishing in March and has been signed every month since.
- 2024
Zen 5, and 40 Gbit/s ports
Ryzen 9950X nodes shipped in the first quarter. Forty-gigabit ports became an option on EPYC, storage and metal at every site with the upstream capacity.
- 2025
Thirty-four sites
Vienna, Dubai and Santiago opened. Median deploy time fell below a minute for the first time after the provisioning queue was rewritten.
- 2026
Where we are now
Johannesburg is racked and taking pre-orders. Platform revision 5.4 rolled out in June with per-instance snapshot scheduling and a public API.
What we promise, in writing
The SLA is one page. You should be able to read a hosting contract in four minutes.
Contractual monthly uptime. Miss it and the credit is automatic — you do not have to ask, and there is no form.
Median first response on a ticket, measured across the last quarter, at every hour of the day.
Full refund, no reason required, on any first order. Crypto refunds go back in the asset you paid with.
Overselling ratio. Cores, memory and NVMe are allocated once and not counted twice.
What people tell us
Shortened for length, published with permission, attributed the way each person asked.
“I moved eleven instances across in a weekend and the only thing I had to ask support was whether the /48 was routed or proxied. It was routed.”
“Four years, two attacks, one dead NVMe replaced without me noticing. That is the entire list of events.”
“The part I did not expect was the refund policy actually working. I asked on day five and the coin was back the same afternoon.”
Questions we actually get
Correct. There is no threshold, no escalation path and no exception in the terms. If that ever changes it changes on the canary page first, and existing accounts would be grandfathered.
Anything that attacks a third party, child sexual abuse material, and open mail relays. Everything else is between you and the law of the site you chose. The acceptable use policy is short and specific about this.
No. Crypto only, through OxaPay. That is not a philosophical stance, it is what keeps sign-up down to an email address — a card would drag identity in with it.
We answer what the law of the relevant site requires and nothing beyond it. Where we are permitted to notify you, we do. What we can actually hand over is short, because there is very little to hand over — see the retention table above.
Unmetered under a published fair-use figure that scales with your port. Cross it consistently and we will email you about a dedicated port, not send you a surprise invoice.
Median forty-seven seconds from settled invoice to credentials, ninety-fifth percentile just under four minutes. Custom ISO installs are manual and take longer — usually within the hour.
A hardening baseline and patch management, yes. Full application management, no. We are an infrastructure company and we are not good at pretending otherwise.
Yes, on metal and on EPYC from the E-32 upward, at sites where the upstream permits it. Open a ticket with your object details and we will tell you within a day.
Pick a city. Pick a size. Pay in coin.
No forms about who you are, no wait for a human to approve you, no phone call to verify anything. The invoice clears and the credentials land in your inbox.