Bitcoin dedicated server — metal on a 2-confirmation invoice

A whole server on a Bitcoin invoice: 2 confirmations to credit, rate locked at creation. Forge from $39.20/mo annual-eff, IPMI included, no KYC.
A whole server on a Bitcoin invoice: 2 confirmations to credit, rate locked at creation. Forge from $39.20/mo annual-eff, IPMI included, no KYC.
AMD Ryzen 9 9950X → 2× AMD EPYC 9554PECC DDR5NVMe RAID 0/1/5/10IPMI on all1–25 Gbps unmetered19 coins + XMR
Plan ledger
| Plan | CPU | RAM | NVMe | RAID | Port | IPMI | Price |
|---|---|---|---|---|---|---|---|
| Forge | 16c / 32t | 32 GB DDR5 | 2 x 1 TB NVMe RAID 0/1 | 0/1 | 1 Gbps | IPMI + DDoS | $49 list · $39.20/mo annual |
| Summit | 32c / 64t | 64 GB DDR5 ECC | 2 x 2 TB NVMe RAID 0/1 | 0/1 | 10 Gbps | IPMI + DDoS | $89 list · $71.20/mo annual |
| Monolith | 128c / 256t dual | 128 GB DDR5 ECC | 4 x 2 TB NVMe Gen4 RAID 0/1/5/10 | 0/1/5/10 | 25 Gbps | L3/L7 scrubber | $149 list · $119.20/mo annual |
Full ledger: all dedicated SKUs.
12 locations · 19 coins · SLA 99.95% · no KYC · public canary
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 nowBitcoin dedicated servers: two blocks between payment and racking
A whole server on a Bitcoin invoice credits after exactly 2 confirmations — ten minutes to an hour of wall-clock depending on mempool weather — and then the rack builds your machine. The entry tier is Forge at $49.00 list, $39.20/mo annual-eff: a Ryzen 9 9950X with 16 cores, 32 GB of DDR5, a 2 × 1 TB NVMe pair, IPMI and DDoS filtering inside the base invoice. Signup takes a 32-character token or an email; no KYC document appears at any step of the order.
| Plan | CPU | RAM | NVMe | Port | List / annual-eff | Deploy |
|---|---|---|---|---|---|---|
| Forge | AMD Ryzen 9 9950X, 16c/32t | 32 GB DDR5 | 2 × 1 TB NVMe, RAID 0/1 | 1 Gbps unmetered, IPMI + DDoS | $49.00 / $39.20 | Deploy Forge, pay in BTC |
| Summit | AMD EPYC 9354P, 32c/64t | 64 GB DDR5 ECC | 2 × 2 TB NVMe, RAID 0/1 | 10 Gbps unmetered, IPMI + DDoS | $89.00 / $71.20 | Deploy Summit, pay in BTC |
| Monolith | 2 × AMD EPYC 9554P, 128c/256t | 128 GB DDR5 ECC | 4 × 2 TB NVMe Gen4, RAID 0/1/5/10 | 25 Gbps unmetered, L3/L7 scrubber | $149.00 / $119.20 | Deploy Monolith, pay in BTC |
The checkout divides your USD total by a live BTC rate and prints an address plus a figure to eight decimals; that stored amount is what the payment watcher matches, and the rate locks at invoice creation. Mempool congestion moves only the wait, never the figure. Send the exact printed amount once, on the base layer — Lightning and Liquid are not part of this checkout, and an underpaid transfer stalls the invoice rather than crediting partial.
Why two blocks and not zero or six? Zero-confirmation credit is reversible by reorg, and six turns a small invoice into an afternoon; two is the point where a double-spend against a chain with real fees becomes uneconomical in practice. The same rule applies at every tier and on every flag, so the ladder above prices the wait at zero regardless of which row you pick.
What the invoice looks like at creation, screen by screen
Configure the machine, pick the annual term so the $39.20 figure lands, choose one of the twelve flags, then open the payment page and select Bitcoin. The panel prints an address and the exact BTC amount; the watcher credits on the second block and flips the order to paid. Racking runs 2–4 hours, and IPMI credentials land in the panel — root from first boot, out-of-band console and rebuilds after that.
Three practical notes keep the flow single-pass. Paying from an exchange wallet works only if the withdrawal sends the exact amount on the base layer in one transfer — batched payouts or skimmed network fees make the watcher wait, so a self-custody wallet is the smoother path. An RBF-bumped replacement credits once, on the first matching confirmation. If anything stalls, a ticket with the transaction ID beats sending a second transfer, because the watcher matches amounts, not intentions.
The invoice window runs three days, so a cold-wallet round trip fits without asking support for anything. Rate moves inside that window change the BTC figure only at creation — the printed amount is the contract — and no satoshi margin is ever needed on top, because the watcher matches the stored figure exactly, to the eighth decimal, on every tier from Forge to Monolith.
What BTC does and does not do for your privacy
Bitcoin is pseudonymous, not private: the chain is public, and a coin with history can be read by anyone with a chain-analysis subscription — the Bitcoin developer documentation describes exactly how much metadata a transaction carries. Pairing BTC with a no-KYC signup still strips the usual card-processor identity layer out of the order, and that part is structural rather than marketing: no processor means nobody upstream of the facility holds a name attached to your rack.
When the payment side needs to be quiet too, the same invoice page takes Monero on the identical ladder — the quieter rail walks the same rows, the same prices and the same three-day window — and the token signup means the account itself holds no name. Payment hygiene stays yours: a fresh address per invoice by design, no address reuse, and the exact printed figure every time. The chain-analysis caveat is worth repeating before you plan anything around it.
One structural point settles most of the debate: the privacy of the payment and the privacy of the server are separate questions. BTC changes the first; the token account and the facility's log policy govern the second — no payload or guest traffic logs, connection metadata kept at most 24 hours. Neither rail edits the public blockchain's memory of the coins you spent, and no checkout anywhere can.
The honest section: what paying in Bitcoin will not do for you
It will not launder the machine. The AUP bans CSAM, phishing, spam and network attacks at every location, and the local law of the facility location applies to everything on the disk; a crypto invoice changes the settlement rail, not the jurisdiction. Court orders issued where the rack stands work exactly as they would against a card-paying customer — the coin on the invoice is irrelevant to a judge.
It will not make the account anonymous. The account is a token, and the IP addresses registered to that token sit in the facility's records; connection metadata is kept at most 24 hours, while billing and panel records persist. Bitcoin's ledger is public — if the coins you spend carry history, that history is readable, and no signup form undoes it. Nineteen coins are accepted here, and XMR exists on the same page precisely because BTC is not the quiet rail.
It will not hold the price for you beyond the invoice window. The rate locks at creation; if BTC moves after you create the invoice, the payable amount neither rises nor refunds the difference once it credits. And the catalog stays closed at twelve locations — a coin does not widen the map. If your project needs a flag outside those twelve, the honest answer is that this checkout cannot sell it, at any coin or any tier.
What a BTC invoice does not buy: different hardware, different law, different rules. The metal is the same ledger row with IPMI, ECC and RAID, the contract lives under the jurisdiction of the facility, and the AUP applies with the same force it applies to any rack. Bitcoin changes settlement, not the obligations. Renewals bill the same way: a fresh invoice, a fresh rate, the same ladder.
Against the page-one results, priced honestly
The page-one names for this query at the October 2026 check — ServerWhere and Shinjiru among them — sell BTC billing on offshore metal, and several publish formal SLA credits or a longer location list; a buyer who needs a specific small flag may find it there and not here, which is worth saying plainly. Their entry racks, though, typically start well above $49 list for last-generation Xeon or older EPYC silicon, with thinner published specs per row.
The comparison that matters is per dollar of current-generation core: Forge puts a 9950X behind your BTC invoice at $39.20 annual-eff with IPMI printed in the base price, 2 confirmations to credit and token signup with no KYC step. Where a rival wins on a need you actually have — a specific flag, a longer SLA — buy there; the dated ledger behind the deploy links keeps the like-for-like rows current for exactly that check.
Date-stamp your own comparison, too: entry prices, confirmation policies and KYC steps at rivals move quarter to quarter, and marketing pages lag order pages. The three checks that stay useful are printed specs per row, a published confirmations policy, and an invoice that names the asset and the rate — if a seller hides any of the three, the gap is the answer.
Metal instead of a VPS slice: where the line sits
A Bitcoin invoice for a slice starts at $4.80 annual-eff, and for many nodes that is the right plate. The step up to metal is about neighbors and ceilings: a whole 9950X means no noisy neighbor on the core, 2 × 1 TB of local NVMe means the chain database stops fighting for IOPS, and a 1 Gbps unmetered port means peer limits stop being a budget question. Full nodes that serve light clients, archive nodes and indexers feel the difference within weeks.
Metal also changes recovery. IPMI means a kernel panic is a console session rather than a ticket, and a rebuild runs from the panel without touching the disk layout you configured. If the sizing question is live, work it from usage graphs — CPU steal, iowait, p95 port utilization — rather than from vibes; when two of the three run hot for a month, the plate is too small and the ladder above is the next shelf.
One warning in the other direction: if the workload is a single lightweight wallet or a low-traffic relay, metal is overspend — the slice stays the right answer, and an honest ladder keeps saying so. Buy the smallest plate that holds your p95, upgrade on evidence, and let the 9950X wait until the graphs ask for it.
Fees, mempool and the three-day window
A BTC invoice stays open for three days, long enough for a wallet round-trip from cold storage, and mempool weather moves only the wait: a crowded hour stretches the two-block credit toward the sixty-minute end. Fee estimation is your wallet's job — the invoice needs its exact amount regardless of the fee you attach, and an RBF-bumped replacement credits once, on the first matching confirmation. No surcharge is added on top of the live rate at creation.
Underpaid by a few satoshis? The watcher stalls the invoice instead of crediting partial; a ticket with the transaction ID resolves it, which is also the right move after a duplicate send. Fresh address per invoice, no reuse, no exceptions — that hygiene is the core project's own advice and this checkout's default. If BTC's confirmations feel slow on a given day, the same invoice page takes XMR, USDT on seven networks and sixteen other assets, and the ladder does not move.
None of this changes the pricing: Forge, Summit and Monolith settle on the same rails at the same discounts — 20% on the annual term, 10% on the quarterly one — and the 99.95% SLA holds across all three rows, on every flag from Reykjavik to Taipei. The coin chooses the wait; the invoice stays the contract.
Forge on Bitcoin: $39.20 annual-eff, two blocks, twelve racks
That is the whole proposition: a current-generation rack — 9950X, 32 GB DDR5, NVMe, IPMI — settled in BTC at 2 confirmations, rate locked at creation, from $39.20/mo annual-eff with no KYC at any step. Twelve elite locations behind it, nineteen coins if the rail changes, and the same ladder from Forge to Monolith as every other checkout on the site. Two blocks, 2–4 hours of racking, then root.
If slices fit the job better, the Bitcoin VPS route starts at $4.80 annual-eff on the same two-block credit; the no-KYC dedicated flow page checks the whole document-free order step by step; the USDT variant prices the identical ladder on stablecoin rails inside the same checkout; and the general coin-payment flow works for every other asset on the invoice. Related reading: no-KYC dedicated worldwide for the flag map.
Hold onto the parameters when you compare: $39.20/mo annual-eff at the door ($49.00 list), 2 confirmations to credit, 2–4 hours from payment to IPMI, twelve elite locations in the closed catalog and nineteen coins on the same invoice page. That is the whole product; the rest of this page only explains where its edges sit.
How many Bitcoin confirmations do you require?
Two blocks after your single on-chain transfer — roughly 10 to 60 minutes depending on the mempool — followed by 2–4 hours of racking before IPMI hand-over. The figure printed at invoice creation is what the watcher matches, and it locks at creation.
Can I pay from an exchange wallet?
Yes, if the exchange sends the exact amount on the base layer in one transfer. Withdrawals that batch payouts or skim network fee make the watcher wait, so a self-custody wallet is the smoother path; a ticket with the transaction ID resolves a stalled credit.
Is buying a dedicated server with Bitcoin anonymous?
Partly. The order carries no ID because signup is token-or-email with no KYC, but Bitcoin itself is a public ledger and coin history is readable. For a quiet payment rail, the same invoice page takes XMR on the identical ladder.
What does the BTC price lock cover?
The exact BTC figure stored at invoice creation. Later ticker moves neither raise the payable amount nor refund the difference after the invoice credits, so the lock is on the figure, not on the market.
Do you accept Lightning?
No. The watcher credits base-layer transactions only, so set the invoice amount in an on-chain send and keep the printed figure exact; Liquid is likewise outside this checkout, and no side rail changes the two-block rule.
What does the annual-eff figure actually buy here?
$39.20/mo annual-eff buys Forge: a Ryzen 9 9950X with 16 cores and 32 threads, 32 GB of DDR5, 2 × 1 TB NVMe and a 1 Gbps unmetered port with IPMI and DDoS filtering in the base invoice. Summit and Monolith sit at $71.20 and $119.20 annual-eff.
Primary sources
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.