CryptoServers
Server starten

Bitcoin-VPS-Hosting — in BTC bezahlt, kein KYC

A Bitcoin VPS is a virtual private server you can buy with on-chain BTC or a Lightning invoice — no card, no PayPal, no payment processor in the loop. Cryptoservers issues a fresh deposit address per invoice (BIP-32 HD), absorbs the network fee, and provisions your VM on the first confirmation (~10 minutes on Bitcoin mainnet). Five tiers from $16.99/mo, four offshore jurisdictions, no KYC.

Deploy with BTC Wie BTC zahlt
Bereitstellung nach 1 Bestätigung Lightning unterstützt Neue Adresse pro Rechnung Kein KYC, keine Protokolle
Bitcoin VPS hosting — pay in BTC and Lightning

Bitcoin-Zahlungsablauf — sechs Schritte

Von „Bereitstellen klicken" bis Root-SSH auf einem frisch bereitgestellten VPS in sechs einzelnen Schritten. Schritt 4 ist On-Chain (10 Min.) für BTC oder unter einer Sekunde für Lightning; alles andere wird in Sekunden gemessen.

  1. 1Pick a plan and select Bitcoin. Five VPS tiers, four offshore regions. The deploy form shows BTC as the first option in the coin selector.
  2. 2Fresh deposit address generated. We derive a new receive address from a BIP-32 HD path on our hot wallet. The address has never been used and will never be reused — no clustering for chain-analysis tools to lock onto.
  3. 3Pay on-chain or via Lightning. For invoices < $200 we also display a BOLT-11 Lightning invoice; pick whichever your wallet supports. Send the exact amount; we absorb the network fee.
  4. 4First confirmation (~10 min on-chain, instant on Lightning). Bitcoin block time averages 10 minutes (Difficulty Adjustment Algorithm targets a 10-minute average). One block is sufficient for VPS-tier amounts. Lightning settles as soon as the HTLC resolves — typically under 5 seconds.
  5. 5Orchestrator deploys the VM. In parallel with the broadcast, the orchestrator pre-stages the disk image and the network ACLs. By the time the block confirms, the VM is already booting.
  6. 6SSH credentials emailed. IPv4, IPv6, root password (or your provided pubkey) and a one-time panel-claim link land in your inbox. Median total time, broadcast to root login, is under twelve minutes for on-chain BTC and under two minutes for Lightning.

BTC, Lightning, und die anderen Coins

Wann welche Zahlungsschiene zu verwenden ist. Wir akzeptieren sieben Coins; nachfolgend ein flacher Vergleich von Gebühren, Abwicklungszeit und Datenschutzeigenschaften für VPS-Rechnungen.

Schiene Abwicklung Netzwerkgebühr Datenschutz auf der Chain Am besten für
BTC on-chain~10 min1–10 sat/vB (we absorb)Pseudonym, öffentlicher UTXO-GraphJede Rechnungsgröße, insbesondere > 200 $
BTC Lightning< 5 sMinimale Routing-Gebühr (wir übernehmen sie)Off-Chain-Hops, Quelle nicht auf der ChainKleine Rechnungen, schnelle Iteration
XMR (Monero)~2 min~0.0002 XMRRingCT + Stealth-Adressen (privat)Datenschutz-first-Käufer — siehe /monero-vps/
LTC (Litecoin)~2.5 min< 1 centPseudonym, öffentliches LedgerSchnelle Bestätigungen, niedrige Gebühr
ETH~30 s (1 conf)$0.30–$3Öffentliches Ledger, KontomodellKäufer bereits im ETH-Ökosystem
DASH~3 s (InstantSend)< 1 centÖffentlich, optionales PrivateSendSchnelle Retail-Zahlungen
BCH / DOGE~1–10 min< 1 centPseudonym, öffentliches LedgerKäufer, die einen der Coins halten

Detaillierter Datenschutzvergleich: <a href="/de/guides/bitcoin-vs-monero-payments/">Bitcoin vs. Monero-Zahlungen</a>.

Plan-Übersicht für Bitcoin-Käufer

Dieselben fünf Stufen wie auf der Hauptseite /vps/, als einzelne Vergleichstabelle für den BTC-bezahlten Checkout aufgestellt. Preise in USD, beim Erstellen Ihrer Rechnung zum Spotpreis in BTC umgerechnet.

Tier vCPU RAM NVMe Bandbreite Price
Starter
AMD EPYC 7443P		24 GB DDR4 ECC60 GB1 Gbps unbegrenzt$16.99/mo
Growth
AMD EPYC 7443P		48 GB DDR4 ECC120 GB2.5 Gbps unmetered$26.99/mo
Business
Intel Xeon Gold 6430		616 GB DDR5 ECC240 GB5 Gbps unmetered$39.99/mo
Pro
Intel Xeon Gold 6430		824 GB DDR5 ECC400 GB5 Gbps unmetered$54.99/mo
Scale
AMD EPYC 9454P		1232 GB DDR5 ECC640 GB10 Gbps unbegrenzt$69.00/mo
Bereitstellen und in BTC bezahlen

Einen Bitcoin-Node betreiben auf einem Bitcoin-VPS

Dimensionierung für Full-Nodes, beschnittene Nodes und Lightning-Routing-Nodes — drei unterschiedliche Workloads mit sehr verschiedenen Speicher- und CPU-Profilen.

Full node (unpruned, with txindex). Mainnet plus indexes is approximately 600 GB as of mid-2026, growing roughly 80 GB per year. RAM: 8 GB minimum, 16 GB comfortable for index lookups. CPU: a single fast core (initial block download is mostly serial); ongoing operation is light. Recommended tier: <strong>Pro</strong> (400 GB) if you can prune <code>txindex</code>, otherwise <strong>Scale</strong> (640 GB) — or jump to a small dedicated server. Initial sync from cold takes 8–24 hours on Gen4 NVMe.

Pruned node. Bitcoin Core supports pruning the historical block files while keeping a fully validated chainstate. With <code>prune=8000</code> (8 GB block storage) plus a few GB of UTXO set and chainstate, the on-disk footprint sits around 8–12 GB. Recommended tier: <strong>Starter</strong> (60 GB NVMe) is fine. Useful for wallets, mempool monitoring, fee-estimation oracles and personal Lightning nodes.

Lightning routing node. Storage is negligible (channel state + gossip is a few hundred MB). RAM around 2–4 GB. CPU light. Bandwidth is the variable: a busy routing node moves a steady 5–20 Mbps of gossip and HTLC traffic. Recommended tier: <strong>Starter</strong> or <strong>Growth</strong>. Pair with a Bitcoin Core full node on the same box (Scale tier) or run the Lightning node alongside a remote Core node (cheaper).

Port hygiene: open <code>8333</code> for inbound P2P (more peers help the network and improve your own gossip), <code>9735</code> for Lightning channel listening if you want inbound channels, and <em>do not</em> expose RPC port <code>8332</code> publicly — bind it to localhost or a Tailscale interface and proxy as needed.

Adresswiederverwendung und Datenschutzhygiene

Bitcoin ist pseudonym, nicht anonym. Jede Transaktion ist für immer öffentlich; was Sie am Rand tun (Wallet-Hygiene, Adressstrategie, Wechselgeldbehandlung) bestimmt, ob Ihre Aktivität ein Wald unzusammenhängender UTXOs bleibt oder sich zu einem Cluster zusammenschließt, den ein Chain-Analyse-Anbieter verkaufen kann.

Our side: fresh address per invoice. Cryptoservers derives every deposit address from a BIP-32 HD path on a watch-only wallet. We never display the same address twice and we never reuse one across invoices. This means the only thing chain-analysis can correlate from public data is "an unknown wallet sent funds to an unknown address" — neither side's identity is on the chain.

Your side: hygiene tips that cost nothing.

  • Use a wallet that supports HD addresses by default (Bitcoin Core, Electrum, Sparrow, Wasabi, Phoenix, Blixt). Avoid wallets that reuse a single deposit address.
  • Send to our address from a UTXO that did not come directly from a KYC exchange withdrawal labelled with your name. If you must use a KYC source, use a coinjoin (Wasabi, JoinMarket) or send via Lightning instead of on-chain.
  • Do not consolidate UTXOs from multiple Cryptoservers invoices in your refund destination. We will refund to fresh addresses; you should keep the resulting UTXOs unconsolidated.
  • If you maintain multiple VPS over time, use a separate wallet (or at least a separate account) per VPS — that way the on-chain footprint of your "VPS payments" cannot be linked to the rest of your spending.

Bitcoin Optech publishes excellent ongoing guidance on UTXO management; the bitcoin.it wiki has a long-standing reference on <a href="https://en.bitcoin.it/wiki/Address_reuse" rel="nofollow noopener">why address reuse is harmful</a>. Both worth reading.

Bitcoin-VPS FAQ

Die acht häufigsten Fragen von Bitcoin-Käufern.

How long does a Bitcoin payment take to confirm at Cryptoservers?
We deploy on the first network confirmation, which on Bitcoin is on average 10 minutes (one block). The orchestrator pre-stages your VM the moment we see the transaction in our mempool, so by the time the block lands the VPS is already booting. Median time from "broadcast" to "ssh root@" is just under twelve minutes for on-chain BTC. Lightning payments settle in seconds and we deploy as soon as the HTLC resolves.
Akzeptieren Sie Bitcoin Lightning?
Yes — for invoices under $200 we issue both an on-chain address and a BOLT-11 invoice at checkout. Pick whichever your wallet of choice supports best. Lightning settles in seconds (no on-chain wait), with a tiny routing fee that we absorb. Above $200 we recommend on-chain because Lightning channel capacity along common routes can fragment a large invoice.
Can I run a Bitcoin full node on a Bitcoin VPS?
Yes. The mainnet chain plus indexes is roughly 600 GB as of mid-2026 and growing about 80 GB per year. The Pro tier (400 GB) handles a pruned node comfortably; for an unpruned full node with txindex and addrindex we recommend the Scale tier (640 GB) or a small dedicated server. Lightning routing nodes need negligible storage and run perfectly on Starter or Growth.
Do you reuse Bitcoin deposit addresses between invoices?
No. Every invoice gets a fresh deposit address derived from a BIP-32 HD path on our receive wallet. We never display the same address twice and we never accept a re-payment to a previously-used address — even if you accidentally send to one, the funds will not auto-credit. Address reuse hurts privacy on both sides; we engineer it out.
What if I send the wrong amount of BTC?
Underpayments stay in the invoice as a partial credit; send the difference to the same address within 24 hours and the deploy fires when totals match. Overpayments are credited to your customer record and either applied to the next month or refunded on request to a destination address you supply. Email [email protected] for refund processing — we do not auto-refund because we cannot prove the destination is yours without you telling us.
Do you accept BTC from KYC exchanges?
Yes. From our side an inbound transaction is just a UTXO; we do not cluster sender wallets, we do not cross-reference with chain-analysis vendors, and we do not refuse known-exchange inputs. The privacy property of "your KYC exchange withdrawal that paid for this VPS" is a question for the public chain, not for us — but our records do not enrich it.
Is there a transaction-fee surcharge for paying in Bitcoin?
No. We absorb the network fee on our side. The price you see at checkout is the price we expect to receive net of mempool fees; if the fee market spikes between invoice generation and broadcast and your wallet underpays the network fee, the transaction will simply confirm slower (we wait up to 24 hours for the first confirmation before voiding).
Can I get a refund in Bitcoin to a different address than I paid from?
Yes — refunds within the 7-day money-back window go to whatever destination address you specify, not back to the source UTXO. This is by design: forcing a refund to the source would link our wallet to yours twice and degrade privacy on the chain. Send us a fresh address from a wallet you control and we will pay the refund there.

Weiterführende Lektüre und externe Quellen

Bitcoin-Protokollquellen:
bitcoin.org — Developer Guide (confirmations, transactions)
Bitcoin Optech — weekly developer newsletter and topics index
Bitcoin Wiki — Address reuse
BIP-32 — Hierarchical Deterministic Wallets
BOLT-11 — Lightning invoice encoding

Bezahlen Sie Ihren VPS in BTC.

Fünf Stufen, vier Rechtsgebiete, kein KYC, nach der ersten Bestätigung abgewickelt. On-Chain oder Lightning.

Mit Bitcoin bereitstellen Oder in XMR bezahlen →