$ man node-dedicated
// NAME
node/dedicated — no-KYC offshore dedicated servers, no-KYC crypto billing (XMR / BTC / Lightning / LTC / ETH / USDT via OxaPay), deployed in Iceland and Romania.
// SYNOPSIS
xmrhost-cli provision --type=<slug> --region=<is|ro>// 4 plans returned. all xmr-billed.
// WHEN TO PICK DEDICATED
Dedicated is the right pick when the workload needs full hardware isolation, a custom kernel, sustained line-rate bandwidth, or hardware features (true RNG, ECC RAM, IPMI console, hardware RAID) that VPS virtualization abstracts away. The xmrhost dedicated catalog targets four real workloads: high-traffic Tor exit relays (dedicated bandwidth, not shared); SecureDrop or leak-intake hosting (full-disk encryption with grub LUKS + dropbear-initramfs, customer-controlled keys); large Matrix federations (Synapse + Postgres + media repo at federation scale); and crypto-node hosting (Bitcoin core / Ethereum execution + consensus / Monero node) where the chain syncs benefit from the NVMe headroom and unmetered bandwidth.
Dedicated is not the right pick for: small workloads that fit in a VPS tier (you'll pay for headroom you don't use), GPU inference (use /node/gpu), short-lived experiments (the dedicated SLA assumes a 30-day commit, the VPS does not). The customer panel exposes a downgrade path back to VPS if the workload turns out to be smaller than the chassis can fit.
Iceland-only at MVP — the Romanian racks are spec'd for VPS density rather than bare-metal chassis. The Iceland datacenter has hydroelectric / geothermal power, RIPE PI v4 + v6, and the jurisdictional posture documented at /location/is. Dedicated tiers are billed monthly with a 30-day minimum; cancellation runs to the end of the paid month with no early-termination fee.
// TIER COMPARISON
ds-lite (Xeon E-class, 32 GB RAM, 2× NVMe) is the baseline — sized for a single high-traffic workload. ds-mid (Xeon Silver, 64 GB RAM, 2× NVMe + 4× HDD) is the recommendation for a federated Matrix homeserver or an OSS-mirror node. ds-pro (dual Xeon Silver, 128 GB RAM, 2× NVMe + 8× HDD) and ds-beast (dual Xeon Gold, 256 GB RAM, all-NVMe) are sized for crypto-node + multi-service hosting, with the headroom to run a hardened hypervisor on top if the customer wants to operate sub-VMs.
Bandwidth scales with tier (1-10 Gbps unmetered on the contracted port). IPMI / iDRAC / iLO console access is included on every tier, accessible via the wireguard management VLAN — the IPMI port is not exposed to the public internet in any tier.
// FAQ
Q.Is this real bare-metal or just an unfair fight VPS?
A.Real bare-metal — no virtualization layer between the OS and the silicon. The customer can install any OS with cloud-init or a standard ISO, run any kernel they want (linux-hardened, grsec-flavoured if a subscription is held, OpenBSD if the chassis HAL accepts it), and configure full-disk encryption with their own keys. IPMI / iDRAC / iLO console access is included.
Q.Where is the dedicated server hosted?
A.Iceland (Reykjavik) at MVP. Hydroelectric / geothermal power, RIPE PI v4 + v6, the jurisdictional posture at /location/is. Romania dedicated is on the roadmap once the racks are spec'd for it, but the dedicated catalog stays Iceland-only until the operator can deliver the same hardware-quality SLA in both regions.
Q.Can I use full-disk encryption with remote unlock?
A.Yes — grub LUKS + dropbear-initramfs is a supported install pattern. The customer holds the LUKS passphrase; the operator does not have a copy. Remote-unlock is over SSH-to-dropbear in initramfs; the operator can advise via /contact at provisioning.
Q.What's the SLA?
A.99.9% monthly on the contracted port, 4-hour hardware-swap on confirmed-failed diagnostics, service credits per the /legal/sla schedule. The honest framing is at /uptime — synthetic 99.99% badges are not used.
Q.Can I run a Tor exit on a dedicated server?
A.Yes — the dedicated tier is the right pick for exit relays because of the bandwidth headroom. The AUP (/legal/aup) permits middle, exit, and bridge relays. The xmrhost operator does not process third-party abuse reports against tenant traffic (see /contact 'WHAT WE DO NOT PROCESS'); the customer publishes their own ContactInfo on the relay descriptor for upstream-network coordination.
// SEE ALSO
// no-kyc crypto billing (xmr recommended; btc / ltn / ltc / eth / usdt accepted) — why-monero covers the rationale, payments the flow.