The 14-Eyes alliance, for hosting buyers

Five, Nine, Fourteen Eyes is an intelligence-sharing map, not a hosting statute. Compare flags and plans from $4.80/mo annual with the trade-offs stated.
Five, Nine, Fourteen Eyes is an intelligence-sharing map, not a hosting statute. Compare flags and plans from $4.80/mo annual with the trade-offs stated.
A sharing map, not a hosting statute
The counter-intuitive fact about the Five, Nine and Fourteen Eyes — the rings of 5, 9 and 14 states — is that no treaty in the series regulates hosting at all. The alliances move signals intelligence between member agencies under standing agreements; they do not license data centers, define allowed content or bind what a provider may rent to you. Buyers borrow the map as shorthand — a fast way to guess how easily subscriber data might travel between governments — and the shorthand is useful precisely because it is not law.
Treat the rings as a sorting heuristic applied to one narrow question: would a local agency pass your account data to a foreign counterpart casually, or only through documented process? Membership in the alliance is a proxy for the answer, which is why serious comparisons put the map next to KYC policy and the coin list rather than treating it as a verdict. RFC 7258 names pervasive monitoring as an attack in the IETF's own words — state-scale interception is the environment the alliances exist for, and pretending otherwise helps nobody.
What the treaties organize is trust between agencies: intercepts and records move with less ceremony inside the club than across its borders, because the sharing agreements are standing rather than negotiated case by case. For a rented rack, that translates into the speed and formality of legal process — how many signatures a request needs, how much review it receives — and not into different hardware, different plans or different rules about what you may host.
Where buyers go wrong is letting the map answer questions it cannot. No Eyes treaty regulates what a host may host; a member state does not make your workload illegal, and a non-member does not make an inbox private. The AUP, the KYC posture and your own operational hygiene each outweigh latitude, which is why the no-KYC requirements guide belongs next to this one on your reading list before you order anything.
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 nowThe three rings, counted correctly
The inner ring — Five Eyes — binds the United States, the United Kingdom, Canada, Australia and New Zealand, five states whose signals-intelligence agreements date to the wartime and postwar era and still define the deepest routine sharing. The UKUSA-derived relationship lets intercepts and requests travel among the five with minimal friction, which is why the inner ring gets its own name while the outer circles are known mostly by headcount.
Nine Eyes adds Denmark, Norway, the Netherlands and France, bringing the group to 9 members. Fourteen completes the standard map with Germany, Belgium, Italy, Spain and Sweden, for 14 in total. Bigger numbers circulate in commentary — 17 and 41 eyes appear in forum graphics — but those lack the documented treaty basis the fourteen have, and a careful buyer treats them as folklore until a primary document shows up with names attached.
Treat the roster as historically solid but project it forward only with care. Treaties outlive governments: a member's enthusiasm for sharing waxes and wanes with politics, while the legal plumbing that enables exchange stays built. Buyers therefore get more mileage from reading what each country's own statutes compel — retention duties, disclosure thresholds, judicial review — than from memorizing which anniversary edition of the diagram a country appears in. The diagram is a legend; the statutes are the terrain, and only one of them arrives with citations you can check.
The membership list surprises people twice. The Netherlands and Sweden are inside the club while Iceland and Switzerland sit outside it, inverting what European privacy folklore implies. And the catalog's four APAC sites — Tokyo, Singapore, Hong Kong, Taipei — stand outside the Western alliances entirely, governed by their own statutes rather than by any ring's choreography, which is a different kind of distance than the map suggests.
The counting mistake is quoting a meme table as if it were treaty text; the decision mistake is weighting the roster so heavily that latency, cost and acceptance policy never get compared at all. Both fix themselves the moment you read the membership from a primary source and move on to the criteria that actually price and shape your deployment. The rings are a map of sharing, and a map is not the territory your server lives in.
Why hosting buyers borrow the term
Hosting buyers borrow the term because the operative question for a server is narrow: how casually does account data cross a border here? Inside a member state, the practical answer trends toward faster, less-visible transfers; outside it, toward more process per request. Neither answer changes what the box can run, but both shape how a legal request about your account would travel and who would review it along the way.
That is why offshore comparisons put the map beside KYC policy and the coin list: together they are the three cheap-to-check signals of how much paper accumulates behind an account. The requirements guide covers identity, the anonymity guide covers the surfaces you can actually control, and RFC 6973 supplies the protocol designers' warning that metadata collection is a privacy problem in its own right, independent of content.
A practical exercise makes the abstraction concrete: pick two candidate cities from the catalog and trace what happens to a hypothetical records request in each. Who receives it, under which statute, what standing a foreign agency needs, how long judicial review takes — every step is public knowledge, and writing the two pathways side by side turns a slogan into a comparison. Buyers who run this exercise usually discover the flags they feared and the flags they preferred swap places once actual procedure enters the picture.
The heuristic also ages: memberships are stable, but practice drifts with politics and technology. A judgment formed in 2013 may flatter or slander a country today, so use the map to generate questions — how does process work here, what does retention law require — rather than to hand down verdicts. The twelve-site catalog makes those questions answerable per site, because the governing law of each facility is published rather than guessed at.
The error is stopping at the map entirely. A cheap metal box outside the alliance still needs an acceptable workload under the AUP, and a member-state rack may still be the right answer when round-trip latency to your users is the binding constraint. Both trades are public, and you get to make them consciously. The ordering section below puts jurisdiction in its honest place in the purchase sequence — useful, but never first.
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 without blocking lawful process. Neither setting changes a single mechanical fact about the server you rented: the same CPUs, the same KVM layer, the same out-of-band console and the same provisioning pipeline.
The United Kingdom's Investigatory Powers Act of 2016 — the statute is public — shows the domestic machinery plainly: retention obligations and intercept powers written into national law, exercised by national authorities under national oversight. That is the model to expect in every state on the map. The local statute book, not the alliance, is the document a facility's compliance team actually answers to when someone comes asking.
The corollary deserves its own paragraph because comparison sites skip it: the alliance tells you about government-to-government transfers, while the overwhelming majority of account data movement is commercial and mundane — billing reconciliations, payment-processor queries, abuse reports between providers. Those flows obey contract law and the facility's statutes, not any intelligence compact. A buyer modeling exposure should spend more time on which companies sit in the payment and registrar chains than on which agencies share a treaty, because the boring flows touch the account every day and the dramatic ones almost never do.
Provisioning and product mechanics run on the same clock at every flag: a VPS images about a minute after the invoice credits, dedicated metal takes a few hours with IPMI handed over last, and 1 Gbps to 10 Gbps unmetered ports appear on both sides of the alliance line. Nothing in the order form knows where the map draws its circles, and nothing in the datacenter asks.
The misstep is assuming the club changes the product — that a Fourteen-Eyes rack ships older CPUs or slower provisioning, or that a non-member rack ships faster ones. Hardware, timelines and ports are catalog-wide constants; jurisdiction operates on paperwork, and paperwork is where you should evaluate it. If the distinction matters for your workload, evaluate it there and then move on to sizing, because the silicon itself will not tell the difference.
What membership does not change
Alliance membership neither voids GDPR, FADP or local criminal procedure, nor makes a Bitcoin invoice hard to read. GDPR applies because a facility stands in the EU, not because of anyone's treaty roster; the Swiss FADP applies in Zurich for the same local reason. Data rules come from the facility's statute book, and the club's membership roster is simply not the operative document for what happens to your rack.
Another invariant deserves stating plainly: the platform's technical facts do not shift with geography. A machine in a non-member state boots the same image, presents the same console, and honors the same firewall rules as its twin inside the alliance, and a snapshot taken in one city restores in another without translation. Buyers who verify this once stop paying the geography premium in their heads; the only columns in the site table that change behavior are governing law, uplink and the premium multiplier, and all three are printed.
Public blockchains print their records regardless of latitude: a BTC or USDT payment leaves a permanent public trail that analytics firms read identically in Reykjavik and in Amsterdam. A buyer wanting a quieter corridor picks XMR — the Monero guide covers the mechanics — and a buyer wanting process distance picks the flag. Those are different dials, and turning one does not turn the other.
The independence runs both ways: hosting outside the alliances does not exempt a workload from the laws that do apply. Iceland's no-mandatory-retention posture reduces what the facility is obliged to keep; it does not license content the AUP bans, and it does not repeal the criminal law of the place where your users live. Lawful work stays lawful, banned work stays banned, and the map changes neither.
The fantasy to avoid is composite: a non-member flag plus a crypto invoice equals an unregulated box. Every facility answers to some jurisdiction with a name and a court system, and the honest question is which one, under what process. The site table answers it per location rather than per legend — read the governing-law column first and the peering column second, in that order.
Members inside this catalog
Amsterdam sits inside the club, and the rack is still listed: AMS-IX and DE-CIX peering make it the lowest-latency EU site in the catalog, and the trade is published rather than hidden. Buyers who weigh the alliance heavily simply pick a different flag. The point of a twelve-site map is that the decision stays yours instead of being made by a default.
Outside the alliance, the catalog offers genuinely different postures. Iceland pairs a non-EU rack with no mandatory retention at +20%; Switzerland runs FADP process at +35%; Luxembourg's data-trust regime costs +15%; Norway extends EEA GDPR at +20%. Tokyo, Singapore, Hong Kong and Taipei sit outside the Western alliances altogether, each under its own statute — a different governing logic rather than a stronger or weaker one.
Distance between the flags also has a practical edge: replication. An operator who keeps a warm copy of configuration and data in a second country inherits resilience that no single site can offer, and the catalog's spread across two continents makes the pairing trivial to arrange. Choose the pair for orthogonal properties — one low-latency for users, one far away for procedure — and rehearse the cutover twice a year. A quarter hour of rehearsal converts a scary hypothetical into a runbook, the cheapest insurance available in this trade.
For a first deployment, the practical recipe is to shortlist two flags — one for law, one for latency — and price both. One list price covers the twelve sites except the published premiums, and yearly billing subtracts the same twenty percent everywhere. Bring the test workload up on Core at $6/mo list — $4.80 on the annual term — and benchmark from your own desk before committing the production machine.
Reading the premium as a quality signal or a penalty is the first misread — it is neither, just the published cost of the site. The second misread is assuming the APAC flags are cheaper or more private; they are not. They are differently governed, which is a reason to read their statutes, not a reason to assume anything. Deliberation is free; assumptions are the expensive part.
Ranking criteria for a purchase
Order the decision the way failures actually happen. Acceptable use comes first, because no jurisdiction rescues a banned workload: CSAM, phishing, spam and attack traffic are out on every plan, and the AUP reads the same at every flag. KYC posture comes second — whether the account needs documents or just credentials. Coin support comes third. Jurisdiction, with the Eyes map inside it, comes fourth — and below latency to your users.
Write the ranking down as a literal checklist before opening any pricing page, with a line per criterion and a pass-or-fail mark beside each. The discipline sounds bureaucratic until the first borderline case appears: a country you like with a coin you cannot use, or a plan that fits the workload but only in a jurisdiction you had ruled out. Checklists convert those moments from debates into lookups, and they leave a record of why the choice was made — which future-you, staring at a migration, will want more than the rationale for any single line.
This ordering is unpopular in comparison articles, which lead with the jurisdiction banner and skip the workload entirely. It is also how real people get burned: not by treaty, but by assuming a safe country excuses whatever the box does. The crypto VPS FAQ and the 2026 no-KYC roundup cover the payment and identity layers in the depth this section only sketches.
When the workload is bulk storage or heavy compute, the machine itself starts to matter more than the map. Step up to Forge at $49/mo list — $39.20 on the annual term — for 32 GB DDR5 and 2 x 1 TB NVMe with IPMI on every tier, and size from there. Pick the country for its law, then size the metal for the job, and never let the second step silently undo the first.
The classic inversion is buying jurisdiction first and discovering the plan cannot hold the workload, or the coin list does not include the one wallet you actually use. Five minutes with the ordering above saves the refund emails and the migration weekend. Criteria have an order for the same reason checklists do: the expensive mistakes happen when the steps are taken out of sequence.
The law a rack answers to
Every facility sits under a specific statute book, and the abuse pipeline runs under the law of the facility location, not of the company office. VPSbit is operated by Meridian Node Ltd., registered in Saint Kitts and Nevis, while the racks live in 12 cities whose governing law the site table lists per location. A request to the Amsterdam facility proceeds under Dutch and EU process; a request to the Reykjavik facility under Icelandic process.
That split is ordinary in hosting and surprises nobody who has rented colocation before: the building answers to its own police and courts. What the split means for you is that jurisdiction questions have a concrete answer per server — the site's law — rather than an abstract one about where a company filed its papers. Ask about the rack and you get a city; ask about the registry and you get a flag that governs less than you think.
Practical consequence: when a jurisdiction question actually matters, address it to the site, not to the brand. The governing-law column, the retention posture of that country, and the process a local authority must follow are the operative facts; corporate domicile mostly determines which court hears a contract dispute about the invoice itself. Buyers who conflate the two layers write angry letters to the wrong audience. Separate them once, in writing, and every later jurisdictional question resolves itself in seconds.
Retention and disclosure practice differs accordingly. Iceland imposes no mandatory data retention; EU member sites operate under GDPR's constraints on lawful basis and process; the APAC sites run PDPA- and APPI-family statutes. The privacy page states the platform's own practices — no payload logging, connection metadata kept at most 24 hours — and the AUP governs what may travel through the pipe in the first place.
The confusion to avoid: citing the company registry as the operative jurisdiction — the company is registered offshore, so EU law cannot reach the rack — which is wrong twice. The facility's law governs the facility, and the workload's law follows the users and the traffic rather than the registry. Two legal layers, two different questions, and conflating them is how buyers convince themselves of protections that do not exist.
The 14-Eyes decision, in the order to run it
Run the decision in this order. First, define the workload and check it against the AUP — everything else is noise if the workload is out of bounds. Second, decide the identity posture: credential-only signup with a token or an email, no documents anywhere in the flow. Third, pick the coin from the nineteen available and the billing term, knowing twelve-month billing applies its twenty percent discount uniformly across every site in the catalog.
Fourth, place the flag. Shortlist by law — Iceland for no mandatory retention, Switzerland for FADP, Amsterdam for EU latency, an APAC site for distance from the Western alliances — and check each against the premiums: +20% for Iceland and Norway, +35% for Switzerland, +15% for Luxembourg. Fifth, size the machine: a VPS tier for services, dedicated metal with IPMI when the workload needs whole cores and local NVMe under your sole control.
Sixth, order and benchmark from your own vantage point: a minute of provisioning for a VPS means the latency test can run the same hour you pay. Seventh, set up keys, firewall and backups before the real workload lands, not after. Eighth, revisit the choice yearly — alliances drift, statutes move, and a twelve-site map makes migration a redeploy rather than a project with movers and paperwork.
A closing habit rounds out the sequence: keep a one-page memo of the finished decision — flag, tier, term, coin, and the reason for each — inside the same notes as your keys. Six months later, when a law changes or a new site opens, the memo turns a foggy re-deliberation into a diff against recorded intent. Decisions that live only in memory get remade badly under pressure; decisions that live in a file get amended, which is what governance looks like at one-person scale.
Kept in that order, the Eyes map takes its honest place: one input among five, useful for process-distance questions, useless for everything the workload itself decides. A rack is a legal object before it is a technical one, and the map is a sketch of one corner of that legality. Buyers who keep the sketch and the statute book separate end up with both a faster decision and a defensible one.
Is the Netherlands in 14 Eyes?
Yes. Amsterdam sits inside the alliance, and the rack is still offered because AMS-IX latency is the best in the catalog — the trade is published rather than hidden. Buyers for whom the map is the deciding criterion can pick Iceland, Switzerland or any of the four APAC flags instead, at the same base list price except the published location premiums.
Is Iceland outside the alliance?
Yes. Reykjavik belongs to none of the Five, Nine or Fourteen groups, adds a non-EU rack with no mandatory data-retention law, and carries the published +20% location premium on the list price. For buyers whose threat model starts with intelligence sharing, it is the default European candidate, with Switzerland as the process-minded alternative.
Does hosting outside the club make a VPS safe?
No single factor does. The AUP, the KYC posture, the coin you pay with and your own operational hygiene each carry weight, and jurisdiction changes the speed and formality of legal process rather than the physics of what the server does. Treat the map as one dial among several and rank the whole decision, or the safest-looking flag will host the riskiest defaults.
Do the coins or prices change by jurisdiction?
No. Nineteen coins clear invoices at every site, and one list price covers all flags except the published premiums — Iceland and Norway at +20%, Switzerland at +35%, Luxembourg at +15%. Yearly billing subtracts the same twenty percent everywhere, so the flag decision costs only the premium difference and the thought you put into it.
Where does dedicated metal fit into this decision?
Identically at every flag: IPMI, ECC memory and RAID ship on all three dedicated tiers, from the 16-core Forge upward, and provisioning runs on the same clock on both sides of the alliance line. Pick the country for its law, then size the box for the workload — the alliance never enters the sizing math, and the sizing math never rescues the wrong country.
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.