Bahnhof alternative: ISP heritage, coins-only billing

Bahnhof's billing desk wants KYC; FYRHost's till takes 19 coins and nothing else. Scout VPS from $3.00/mo annual, live in 60 seconds.

Published 2026-08-30 · Updated 2026-10-10 · FYRHost Editorial · 9 min read

Bahnhof at a glance: the fabled Swedish ISP

Bahnhof is a fabled Swedish ISP: the operator behind the Pionen facility - the former civil-defense bunker that kept Wikileaks online when few dared - and a company that has spent decades turning network engineering into a public identity. That heritage is genuine and deserves better than competitor sniping. FYRHost's angle is narrower and deliberately different: their billing demands KYC; ours takes coins and nothing else.

The distinction is about layers. Bahnhof's network layer - fiber, peering, bunkers - is the craft of an ISP; its billing layer is a European invoice machine that needs a name, an address and often more. FYRHost's billing layer is a till of nineteen coins feeding an automated provisioner that boots a VPS about 60 seconds after credit, from an account built of an inbox or token plus a 12-character password. One layer is measured in milliseconds and defense in depth; the other is measured in how much it remembers about you.

Buy the heritage if the heritage is what you need - colocation next to serious Swedish engineering is a real product with real value. Buy the till if the till is what you need. The sections below give each its due: a verification checklist, the rails comparison, the honest wins, and a runbook for moving an edge or a server.

How to verify an ISP-grade host before you sign

ISP-grade sellers are verified differently from boutiques: their strengths are network-shaped, so the checklist probes the network and the paperwork around it. Run the same six checks on any operator of this class, FYRHost included, and keep written answers. A bunker with vague policies is just a cold room with opinions, and you deserve better on both counts.

• Ask for the network facts: peering policy, upstream mix, and the path your traffic actually takes from the facility to the exchange.
• Request the retention policy in writing - payload logs kept or not, metadata window in hours - since ISPs sit exactly where logs are easiest to collect.
• Ask which entity contracts you, in which country, and which courts the facility answers to under abuse complaints.
• Count the coins at payment and ask what happens when card or invoice rails are unavailable to you specifically.
• Confirm DDoS scope: L3/L4 included on every product, or quoted per incident with a capacity list.
• Read the AUP for the explicit banned list - CSAM, phishing, spam, attacks - and the process that follows a complaint.

FYRHost's standing answers: no payload logs ever written, metadata dropped within 24 hours, abuse handled under facility jurisdiction, an AUP that names the banned harms explicitly, L3/L4 filtering included on every plan, and a contract with WESTFALL AND CO. in Saint Kitts and Nevis. The jurisdiction page carries the long version. An ISP's craft deserves admiration; policies deserve documentation, and you are entitled to both.

Payment rails compared: the invoice desk versus the till

A European ISP bills like a utility: named invoices, bank rails, identity attached - because that is what its systems were built for, and because KYC is a feature of its home market. A coins-only till is built the other way: value arrives, identity does not. FYRHost's drawer holds nineteen coins - BTC, XMR, ETH, BNB, SOL, LTC, TRX, XRP, DOGE, DASH, ADA, GRAM on TON, and USDT across TRC-20, ERC-20, BEP-20, Polygon, Arbitrum, Optimism and SPL.

Speeds from the sheet: XRP 3 ledgers with no destination tag, TRC-20 USDT 19 blocks or about 1-3 minutes, DOGE 3 blocks, DASH 3, ADA 3, BNB 15, Monero 10 blocks, BTC 2 confirmations at 10-60 minutes. RFC 5321 is the standard behind the SMTP envelopes any invoice system mails with - a reminder that the billing layer is just software talking to software, and it can be built either way you like.

The comparison is honest in both directions: invoices give accounting departments what they need, and coins give privacy buyers what they need. If your employer requires named billing, the ISP's desk is correct for you. If the requirement is that the till learn nothing about you, nineteen rails and an inbox-and-password account are the answer - and the same flow serves renewal number fifty as it served renewal one. Nineteen rails also mean a renewal never waits on a bank holiday, which an invoice pipeline cannot honestly promise.

Where Bahnhof genuinely wins

The network is the win, stated without envy. Decades of fiber ownership, exchange peering and bunker-grade facility engineering produce a performance and resilience story that resellers and newer operators cannot replicate by ordering capacity. If your workload wants to sit on genuinely excellent Swedish infrastructure, Bahnhof sells the real thing and has for a very long time. Pedigree like that compounds; every year of uptime adds to a story a newcomer cannot purchase at any price.

The heritage has civic weight, too: the operator that hosted Wikileaks in a nuclear bunker became part of internet history, and customers buy a piece of that story with every rack unit. There is also broad product depth around the core ISP business - broadband, colocation, enterprise networking - that a hosting specialist does not attempt. FYRHost sells servers and the policies around them, not fiber to your office.

So the honest split: Bahnhof wins on network pedigree and the cultural real estate that comes with it; FYRHost wins on billing privacy, till depth and provisioning speed. A company can be admirable and wrong for your requirements at the same time - the checklist above exists precisely to tell those two verdicts apart before money moves.

The heritage is real; the billing desk is too

Respect the bunker and read the invoice with the same care. A European ISP's billing systems attach names because European law and card rails reward it; that is a legitimate design for most customers and the wrong design for some. FYRHost's answer is structural: a SKN contract entity, an inbox-or-token account, a 12-character password, and a till that never learns more than a payment address. The papers do the arguing, which is what papers are for.

Structure extends to the product around the till. Scout to Sentinel runs 1/2/40/1G to 12/32/640 with 10 Gbps at the top; metal runs from the Shield's 8-core E-2388G with IPMI at $38.50 list to the Citadel's dual EPYC 9474F with 96 cores, 512 GB and 25 Gbps with L3/L7 filtering; Storage Depot holds archives at $24 per TB on annual terms. Provisioning: about 60 seconds for VPS, 2-4 hours for metal, all of it automated.

And the map answers the geography question a single-country ISP cannot: forty sites, with Iceland and Norway at +20 percent, Switzerland at +35 percent, Luxembourg, Cyprus and Panama at +15 percent, and the rest at base rate - the ladder is identical at every pin. One provider, many flags, same posture at each: no payload logs written, metadata gone inside 24 hours. Surcharges are printed, the posture is uniform, and the ladder does not shrink at the smaller pins.

Migration and dual-homing: edge and server moves

Moving from an ISP-grade provider usually means moving something network-shaped, so stage it like a network change: provision, observe, shift gradually, keep rollback armed. Book the replacement first - a Scout at $3.00 annual-effective boots in about 60 seconds - and let both sides run in parallel through at least one full week of traffic before you commit. Overlap weeks feel extravagant until the day a route flap proves exactly why they exist.

Firewall and edge rules move first in staging, not last: the pf.conf manual is the canonical read for the ruleset you will re-create, and relayd's manual covers the layer of redirects and health checks that sits above it. Translate rules deliberately rather than copying blindly - a ruleset is documentation of intent, and migrations are when old intentions get audited for free.

If you announce space or run sessions, give routing the respect RFC 4271 demands: BGP converges when it converges, and timers you inherited from the old site may not fit the new one. Keep both edges answering, watch graphs from outside both networks, and cancel the old service only after a quiet week. TCP, per RFC 9293, will forgive a planned handover; it punishes an unplanned one.

Trying FYRHost beside Bahnhof

Run the comparison empirically: open an account with an inbox or a token and a 12-character password, pay one month of Scout at $5.49 list or $3.00 on annual from any of nineteen coins, and time the boot - about 60 seconds from credit to shell. No invoice asked for a name; no form asked for an address; nothing arrived for you to countersign. The whole test is cash and clock: no paperwork enters, and the timer starts when the coin lands.

Then test the parts an ISP cannot print on a signup page: payload logs that are never written, metadata dropped within 24 hours, L3/L4 DDoS filtering included on every plan at all forty locations, and abuse handled under the jurisdiction of the facility rather than by improvised policy. Sentry, at $7.50 list or $6.00 annual, doubles the entry shape if the first tier feels tight within a week.

Close with the papers: the AUP's explicit banned list, the jurisdiction page on the SKN entity, and the no-KYC page documenting the signup flow end to end. If Swedish fiber is the requirement, buy the fiber - it is excellent. If the requirement is a till that stays silent, the comparison has already answered itself.