Offshore vs 'bulletproof' hosting: the line that matters

Two terms, blurred on purpose

The blur is not accidental, and it serves two camps at once.

Critics of privacy infrastructure flatten "offshore" into "bulletproof" because it makes lawful jurisdiction shopping sound criminal: if a Swiss server and a botnet C2 are the same category, the argument against both writes itself. Meanwhile, actual abuse-shielding operations borrow the word "offshore" because it lends them the respectability of a legal business model they do not have.

Both distortions collapse under one question: whose law does the host obey? An offshore privacy host declines foreign paperwork but answers fully to its own courts. A bulletproof host promises to answer to nobody — including the police of the country its racks sit in. That single distinction drives everything downstream: who the customers are, how long the infrastructure lives, what happens when pressure arrives, and whether you can build anything durable on top.

Offshore privacy hosting, defined

Offshore privacy hosting is a lawful business that selects jurisdictions deliberately. The legal position is public and coherent: servers are placed in countries chosen for strong due process, weak or absent retention mandates, and distance from foreign notice regimes — our jurisdiction comparison walks through all 6 of ours.

The posture has hard edges in both directions. Toward foreign paperwork: DMCA notices are not processed or answered, because the DMCA is a US statute with no force in our jurisdictions. Toward real law: a binding order from a court with jurisdiction over the specific server is complied with, narrowly and completely. And toward abuse: a published acceptable-use policy — no spam, no CSAM, no malware C2, no DoS launches, no phishing — enforced by the host on its own initiative.

Add an honest data inventory (what we hold: a handle, a password hash, a balance, server specs) and crypto-only billing, and you get the actual product: legal compute with the smallest possible compelled-disclosure surface.

Bulletproof hosting, defined

Bulletproof hosting is the opposite promise: that nothing will ever be taken down, no matter who asks — local court, local police, upstream carrier, anyone. It is marketed, usually in closed forums, directly to operations that cannot survive on lawful infrastructure: spam cannons, malware command-and-control, phishing kits, carding shops.

The operational reality follows from the customer base. Bulletproof providers run on rotating shell companies, leased or hijacked address space, and infrastructure resold through enough layers that the person you pay has often never seen the rack. The "abuse desk" exists to ignore the provider's own jurisdiction's law — which is the line no legal business can cross and stay one.

Note what bulletproof is not: it is not a stronger version of offshore. It is a different product for a different buyer, and the protection it sells is — as the next section shows — largely fictional.

Why bulletproof is a trap

Even taking the sales pitch at face value, bulletproof hosting fails its own customers in five predictable ways.

• It is a law-enforcement magnet. Concentrating criminal infrastructure in one network gives investigators a single high-value target. Entire bulletproof providers have been raided and dismantled — the CyberBunker datacenter takedown in 2019 ended with the operators convicted and every customer's data, lawful or not, seized into evidence.
• The neighbourhood effect. Your packets share address space with botnets. The ranges are on every blocklist that matters: mail is undeliverable, CDNs refuse you, peers de-prioritise the AS. You inherit the reputation of the worst tenant on the subnet.
• No recourse. The operator hides from its own government — it can certainly hide from you. Extortion at renewal, sudden disappearance, and quiet resale of customer data are documented patterns. You cannot sue a ghost.
• You become evidence. When the provider is the target, the warrant covers the racks — every disk goes into the van, yours included.
• The premium buys targeting, not protection. You pay multiples of market rate for infrastructure whose life expectancy is measured in months.

The risk ledger, side by side

Strip the marketing and compare the two models dimension by dimension:

• Legal exposure: offshore — none beyond your content's lawfulness where it is hosted; bulletproof — proximity to criminal infrastructure, with seizure risk priced in.
• Continuity: offshore — a business with an SLA (99.9% for us, with pro-rated credits); bulletproof — lasts until the raid, the exit scam, or the de-peering, whichever lands first.
• IP reputation: offshore — clean ranges, policed by the AUP, with rDNS you control; bulletproof — pre-burned space that no blocklist will ever delist.
• Payment: offshore — a prepaid crypto balance you fund from $30.00, refundable per the terms; bulletproof — payment to an anonymous counterparty with every incentive to keep both the money and the leverage.
• On a complaint: offshore — foreign notices produce nothing; a binding local court order is executed narrowly; bulletproof — nothing happens until everything happens at once.

The pattern is consistent: offshore converts legal risk into procedure, while bulletproof merely defers it — with interest. There is also a quieter dimension worth weighing: durability of the relationship. An offshore host wants you renewing for years, so its incentives point at clean ranges, working hardware and honest terms. A bulletproof operator's planning horizon ends at the next exit, and every incentive — pricing, data handling, what happens to your disks when they fold — points the other way.

Where privacy hosting legitimately fits

The honest use cases for offshore privacy hosting share one shape: lawful content, hostile environment.

• Journalists, sources and publishers who need infrastructure that does not fold to the first angry letter — Iceland exists in our fleet for exactly this.
• Researchers and archivists whose mirrors and datasets attract automated takedown fire despite being lawful.
• Businesses keeping client data out of broad-retention jurisdictions as a matter of policy, not evasion — Switzerland's statutory regime is the draw here.
• Crypto-native projects that want payment rails matching their stack: balance-funded servers paid in any of 17 currencies, no card processor in the loop.
• Communities and projects under deplatforming pressure for content that is controversial but legal where hosted.

For all of these, a VPS from $8.00/mo or dedicated server from $66.00/mo deploys against a handle and a balance — online in 15 min for VPS, 2–12 h for bare metal. No identity attached, and no pretence that the rules don't exist.

How to tell which one you're buying

Labels are free, so test the posture instead:

• A real offshore host names its jurisdictions and explains the legal theory behind each. Vague "offshore locations" usually means a reseller who doesn't know either.
• It publishes an AUP with teeth and visibly enforces it. A host that won't say no to phishing will eventually cost you your address-space reputation, then your uptime.
• It is specific about court orders: "we comply with binding orders from courts with jurisdiction over the specific server" is a defensible position. "We ignore everyone" is a countdown.
• It documents what it holds about you, because a vague data inventory means an unbounded disclosure surface.
• Its payment model matches the promise — identity-free signup loses its meaning when a card processor holds the kill switch.

If a provider winks that it will shield you from its own police, walk away: you have just been told how it treats the law, and you are on the other side of your next dispute with it. If you want the rules we actually operate under, they are short and public: the AUP and the no-KYC policy.