1984 Hosting Alternative: Coin Settlement Instead of Cash by Mail

1984 Hosting takes cash by mail; FYRHost settles in minutes across 19 coins: VPS from $3.00/mo annual, 40 locations, no KYC at any tier.

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

Position: envelopes and one harbor versus coins and forty doors

The thesis, verbatim: Iceland privacy institution with cash-by-mail. We stay coins-only and spread across regions. 1984 Hosting is one of the few providers older than the modern privacy-hosting genre, named after the book and acting like it: Icelandic jurisdiction, a long public record on data protection, and a payment option most of the industry abandoned — physical cash in an envelope. 1984.hosting is the institution's front door, and the longevity is genuine.

Cash by mail remains the deepest identity cut in hosting: no chain analysis, no processor, no account name beyond what the form asks for. It costs what it has always cost — days of postal latency, manual reconciliation, and a single-country operations base. The coins-only model keeps the identity cut and drops the latency: nineteen rails with quoted clearing, and forty locations across the map instead of one harbor, all behind the same three-field signup.

This page compares the two anonymity schools honestly — envelope versus chain — and then does the operational work: how to verify either kind of provider, where each genuinely wins, and a migration runbook for moving a workload between Reykjavik and the rest of the map without losing what the privacy posture was for.

How to verify an anonymity-first host

Anonymity claims invert the usual audit: instead of asking what the provider knows about you, ask what the provider cannot know, and what happens to the gap. The checklist below is tuned for providers whose identity story is the core product — it applies to envelope-takers and chain-settlers alike, and it takes about twenty minutes end to end.

• Trace the signup path end to end and list every field; anything beyond contact-plus-password is a leak surface.
• For cash rails, check the reconciliation address and whether the return path can identify you; for coin rails, read the confirmation policy per coin.
• Ask whether the account can be topped up anonymously after signup, not only created anonymously.
• Read the logging policy in both halves: payloads, and metadata — and how long each survives.
• Find the abuse jurisdiction in writing; anonymity at purchase means little if disputes unmask you by default.
• Check the exit: can the service be paid for, used and cancelled without a name ever entering a database?
• Test support with a neutral question and see whether the reply demands identity as a side effect.

The coins-only answers: signup is an inbox address or access token plus a twelve-character password; top-ups are coins — nineteen of them — with nothing entering a database beyond a chain reference; payload traffic is never logged and metadata lives at most 24 hours; abuse is adjudicated under the jurisdiction of the facility, not a head-office court, per the jurisdiction page. The entity is WESTFALL AND CO., St. Kitts and Nevis, and the content lines are the AUP's four: CSAM, phishing, spam, network attacks.

Payment rails compared, qualitatively

Envelope settlement is anonymity in its purest commercial form: bearer cash, no third party, no chain. Its costs are structural — postal days, manual matching, and the honest possibility of loss in transit — and its ceiling is low: it does not scale to a top-up at 2 a.m. before a launch. It is a heritage rail kept alive by conviction, and the providers who keep it alive deserve credit for the inconvenience they absorb on their customers' behalf.

Chain settlement keeps the bearer property and drops the post office: nineteen coins, cleared by consensus rather than by mail carriers. Quoted clearing on this side: BTC 2 confirmations, 10-60 minutes; XMR 10 blocks; TRC-20 USDT 19 blocks, 1-3 minutes; XRP 3 ledgers, no destination tag; DOGE, DASH and ADA 3 blocks; BNB 15. Chain analysis exists as a discipline, and coins differ in their exposure to it — Monero's design, drawing on the curve work standardized in RFC 8032, is built to resist it, per the project's own documentation.

The fair verdict: the envelope remains unbeaten for absolute name-detachment and unbeaten for slowness; coins trade a sliver of traceability for settlement in minutes and a checkout that never closes. A provider taking both rails would be ideal; this one takes coins only, on the theory that minutes matter more after the first month of any project's life.

Where 1984 Hosting genuinely wins

The institution is the win. A brand built across years of Icelandic privacy work carries a public record — position statements, community standing, a long history of taking unpopular customers — that functions as due diligence you do not have to redo. When the question is which provider will still be saying the same things in a decade, tenure in one place with one name is evidence, and the Icelandic original has it.

Cash-by-mail itself is the product this checkout cannot offer: there is no envelope intake here, no postal reconciliation desk, and pretending otherwise would be silly. For a user whose only acceptable rail is bearer cash, the choice is already made and made correctly — this page will not pretend a coin is an envelope, because chain analysis is a profession and envelopes are not its subject.

Single-country depth has operational upsides too: one grid, one staff culture, one legal routine practiced for years. Where projects match that shape — Iceland-centric, low churn, cash-funded — the fit is real. Where projects expect to move, scale or settle quickly, the forty-door model with minute-clearing rails fits better, and the runbook below keeps the exit cheap enough to actually use.

Envelope clearing versus chain clearing

A payment rail is a clock as much as a pipe. An envelope's clock runs in postal days: send, sort, fly, sort, deliver, open, match, credit — the best case is under a week, the honest average is longer, and none of it is visible to the payer at any point. Chain clocks are public by design: every figure quoted on this page is observable on the network the moment it happens.

That observability changes planning. A Sentry at $7.50 list, $6.00 annual-eff, provisioned against a TRC-20 payment clears in 1-3 minutes after 19 blocks — inside a lunch break. The same order on Bitcoin settles within the 10-60 minute band of 2 confirmations; on Monero, within 10 blocks. An envelope order is a lesson in patience, which is a fair price for its properties, but it should be chosen with eyes open rather than inherited from habit.

One more operational note: chains also make receipts. The transaction ID that credits the account is the audit artifact for the whole relationship — useful for accounting, and a reminder that public chains are pseudonymous rather than invisible. Spend the paranoia where it pays: choose the rail per payment according to the threat model, instead of worrying evenly about everything at once.

Region spread as an operational hedge

One-harbor hosting concentrates more than law: it concentrates the grid, the upstreams, the staff and the natural risks in one place. Volcano-season jokes write themselves in Iceland, but the serious version is generic — any single site has weather, fiber cuts, power events and facility incidents, and a provider that cannot move a box geographically cannot hedge those for the customer. Geography is a risk parameter, whether or not the sales page admits it.

Spread converts relocation into a setting. Forty locations across the map mean the same checkout can follow the users, the law, or the latency budget without a vendor change. Surcharges publish the map's shape: Iceland and Norway +20%, Switzerland +35%, Luxembourg, Cyprus and Panama +15%, the remainder at list price — the VPS page carries the table, and every location shares the same coins-only account model.

Hedge mechanics are the runbook in miniature: keep a warm spare in a second region, replicate the data, and rehearse the flip quarterly. A spare Scout at $3.00 annual-eff is cheap insurance with a 60-second boot, and the discipline it buys is worth more than the hardware it runs on. WireGuard tunnels between regions make a sensible spine for the pairing — the published protocol notes explain the cryptography in an afternoon's reading, and the jurisdiction page helps pick the second court before the first one matters.

Migration and dual-homing runbook

Migrating off a cash-settled, single-country host is procedurally ordinary: provision here first — a Sentry, $7.50 list, $6.00 annual-eff, 2 vCPU, 60 GB NVMe, live about 60 seconds after a coin credit — then copy, verify, and flip. The special part is timing against the envelope economy if one is still in play: expect no refunds of posted cash, and plan coin top-ups from zero on this side of the move.

Copy with discipline: trees by rsync or tar over SSH; keys minted with ssh-keygen; daemon settings checked against the sshd(8) manual; databases dumped, restored, and counted; mail moved last with IMAP-aware tools. Whole-image moves use dd(1), but prefer a clean reinstall plus a data copy — decade-old boxes accumulate a decade of sediment, and a fresh install is the one free audit the migration hands you.

Verify before the flip: pin curl at the new address, exercise the login and checkout paths, then shorten the records' cache lifetimes and switch. Park the source for 48 hours and watch its logs go quiet. Dual-homing across jurisdictions — Reykjavik plus a mid-Atlantic or Alpine site — is the same loop with a longer overlap, and it is the recommended end state for anything censorship-adjacent: two independent harbors, one checkout, one coin habit.

Close the loop on identity hygiene: new account, new inbox or token, coins from a fresh address if the threat model asks, and a twelve-character password that shares nothing with the old one. The whole ritual costs minutes and preserves everything the migration was for — which is the point of doing it deliberately rather than reactively.