CryptoServers
Decision aid · 8 min read

Choosing a jurisdiction: Iceland, Netherlands, Romania, Switzerland

We operate in four jurisdictions on purpose — each one trades off legal posture, network reach, and price differently. Picking the right one rarely comes down to a single dimension; this guide walks the dimensions in the order most workloads actually weight them.

No KYC, ever DMCA ignored No traffic logs Live in 60 seconds

The four locations at a glance

Iceland (Reykjavík) — strong free-press constitution, no MLAT with the US for civil matters, geothermal grid. The most legally pristine jurisdiction we operate in, but transatlantic latency penalises some workloads.

Netherlands (Amsterdam) — Tier-1 carrier dense, AMS-IX peering hub, lowest median EU latency. EU/GDPR jurisdiction. The right pick for game servers, public Matrix homeservers, and seedboxes where reach matters more than legal exoticism.

Romania (Bucharest) — EU jurisdiction but the Constitutional Court has rejected EU data retention twice (2009 and 2014), the lowest cost of electricity in the EU, strong eastern-European peering. Underrated for crypto nodes and dev sandboxes.

Switzerland (Zürich) — Swiss Federal Data Protection Act, foreign DMCA notices have no force without a Swiss court order, outside the EU and the 14-Eyes. The highest legal floor of the four, paid for in slightly higher hosting cost.

Decision dimension 1 — DMCA / takedown tolerance

All four jurisdictions sit outside the US, so US DMCA takedown notices have no statutory force in any of them. The differences are in how the local copyright law operates and how fast a rights-holder can escalate to a local court.

Switzerland is the cleanest: a Swiss court order is required before we act, and that bar is high. We've never received one against a non-CSAM workload in the lifetime of the company.

Iceland has the strongest free-press tradition; the IMMI legislation (Iceland Modern Media Initiative) explicitly protects intermediaries from foreign takedown demands. In practice equivalent to Switzerland for our use cases.

Romania is EU but operationally tolerant — local courts rarely process foreign takedowns absent a translated, notarised filing, and that filing is itself a slow process. Good for seedboxes and similar workloads.

Netherlands is EU and faster about it — copyright holders with a Dutch presence can escalate via NTD (Notice and Takedown) more efficiently. We push back on most NTD claims, but the threshold is lower than in the other three.

Decision dimension 2 — data retention law

Iceland: no mandatory data retention. Routine billing logs only.

Switzerland: Federal Act on Telecommunication Surveillance (BÜPF) applies to providers of certain sizes, but cryptoservers as a hosting provider sits below the threshold for surveillance obligations. No data is retained that would let us answer a content-targeted subpoena even if served.

Romania: post-2014 Constitutional Court ruling, no general retention obligation.

Netherlands: the EU's e-Privacy regime requires the ability to comply with lawful retention orders, but we do not pre-emptively retain. In practice this means a court order can compel future logging, not retroactive disclosure of what we never stored.

Decision dimension 3 — network reach and latency

Netherlands wins on Western European latency: median RTT under 30 ms to most of WE from AMS, and direct transatlantic fibre keeps US latency competitive.

Romania is the second-best EU pick, with good peering across Eastern Europe and the Balkans. AMS is one transit hop away.

Switzerland is well-peered to both DACH and Italy, but adds 5–10 ms to UK and Northern European routes vs. NL.

Iceland adds 30–50 ms transatlantic latency penalty to most users — that's a significant cost for game servers and competitive multiplayer, but not for batch workloads (Bitcoin/Monero nodes, mail, seedboxes).

Decision dimension 4 — price

Same plan tiers, same prices everywhere — we don't price-discriminate by location. The cost differential the customer feels is bandwidth-bound: in practice, all four locations ship identical unmetered uplinks at the advertised plan rate, so the price is identical for the customer.

Where it differs is at the dedicated tiers: power and rack costs in Switzerland and Iceland run higher than in NL or RO, but our pricing absorbs that — you pay the same regardless. Choose by the dimensions above, not by trying to game the price.

Workload-to-jurisdiction matrix

Tor exits, mail servers, public Matrix homeservers — Iceland (cleanest legal posture, no abuse-mail backlash) or Switzerland.

Bitcoin Core, Monero remote nodes, Lightning routing — Switzerland (best legal floor for long-running crypto-adjacent infra) or Romania (cheapest power, good peering).

Game servers, dev sandboxes, public-facing web infra — Netherlands (lowest WE latency, AMS-IX reach).

Seedboxes — Netherlands or Romania (DMCA tolerance + bandwidth depth) for active libraries; Iceland for archival.

VPN exits — pick by your audience: NL for WE users, CH for DACH, RO for SE Europe, IS for users who specifically don't want EU egress IPs.

Multi-jurisdiction patterns

Lightning watchtower in a different jurisdiction from your routing node. We've seen customers run the routing node in Switzerland and the watchtower in Iceland — a single seizure or DDoS event can't compromise both.

Mail with rDNS in Switzerland, scraping/inbound traffic from a Netherlands sandbox. The mail-bound IP gets the strong legal posture; the scraping IP gets the AMS reach.

Bitcoin Core in Romania (cheap power, good IBD time) + Lightning routing in Switzerland (legal floor). They peer over Tor or a private WireGuard between them.

Quick answers

Frequently asked

What if a court order does come — what do you actually do?
If it's a valid Swiss / Icelandic / Romanian / Dutch court order issued by a local court with jurisdiction, we comply with the narrow scope of the order. We don't roll over for unsigned requests, and we never honour foreign court orders that haven't been domesticated through a local court. Our /canary/ confirms weekly that no sealed order has been served.
Can I move my server between jurisdictions later?
Yes. Provision the new server in the target jurisdiction, rsync your dataset over the public internet (we don't have a private cross-DC fabric), cut over via DNS or IP failover, destroy the old server. Your account, billing, and panel state stay the same — only the server moves.
Are there workloads you'll only host in specific jurisdictions?
No. Anything our AUP allows runs in any of the four. We'll suggest a fit based on the workload's needs (the matrix above), but if you want a Tor exit in Romania or a game server in Iceland, that's your call. We respect it.
How do you handle MLAT / mutual legal assistance requests?
We don't process them ourselves — they go through the relevant national authority, who then decides whether to issue a domestic order. None of our jurisdictions has a general MLAT for civil intellectual-property matters with the US; criminal MLATs require a domestic legal process before they reach us. The canary covers any sealed order received through any channel.
Why not host in more jurisdictions?
Because each jurisdiction we add is a legal entity, a banking relationship, a local presence, and a set of compliance obligations we have to actually understand. Four is the number where we know each one's law in detail and can answer customer questions accurately. Adding a fifth that we couldn't speak to with the same precision would be a downgrade.
Apply this

Workloads this guide applies to

Each card opens a workload-specific page with sizing recommendations and a sysadmin FAQ.

Read enough? Deploy in 60 seconds

No email verification, no ID, no account. Pick a plan, pay in any cryptocurrency, get root.