The 14-Eyes alliance, for hosting buyers

Five, Nine, Fourteen Eyes is an intelligence-sharing map, not a hosting statute. Who the members are, what membership changes for a rack, what it does not.

Published 2026-08-30 · Updated 2026-09-29 · NulNet Editorial

The three rings

Five Eyes — the US, UK, Canada, Australia and New Zealand — share signals intelligence under standing agreements. Nine adds Denmark, Norway, the Netherlands and France. Fourteen completes with Germany, Belgium, Italy, Spain and Sweden. The club moves intercepts between agencies; buyers borrow its map as shorthand for where subscriber data might travel without much ceremony.

Why hosting buyers borrow the term

The operative question for a server is narrow: would a local agency pass account data to a foreign counterpart casually, or only through documented process? Membership in the alliance is a proxy for that answer, which is why offshore VPS comparisons put the map next to KYC policy and coin list. A sorting heuristic, not a statute — no Eyes treaty regulates what a host may host.

Members inside this catalog

Amsterdam sits inside the club, and we still rack there because AMS-IX is the best latency in the catalog — the trade is published. Outside the alliance, Iceland pairs a non-EU rack with no mandatory retention, Switzerland runs FADP process at a +35% premium, and Bucharest pairs EU transit with retention law struck down in 2014. Twenty-one flags total, one list price apart except those two premiums.

What membership changes for a rack

Inside a member state, account data can move between agencies faster than a buyer might like, and national law still governs anything the facility receives. Outside the club, distance and treaty friction slow the same pathways. Neither setting touches the mechanics of hosting: IPMI, ECC memory and RAID ship identically on every dedicated tier in every city, and provisioning runs on the same clock.

What it does not change

Alliance membership neither voids GDPR, FADP or local criminal procedure nor makes a Bitcoin invoice hard to read — public chains print their records regardless of latitude. Data rules come from the facility's statute book, not from the club's membership roster. A buyer wanting a quieter rail picks Monero; a buyer wanting process distance picks the flag. Different dials.

Ranking criteria for a purchase

Order the decision the way failures actually happen: acceptable use first, KYC posture second, coin support third, jurisdiction fourth — and the Eyes map somewhere after latency to your users. A cheap metal box outside the alliance still needs the right workload inside the AUP. Whole-core CPU or out-of-band console points at the dedicated lineup from $30.80 annual-eff with IPMI at every tier; bulk data at the storage tiers from $24.