Step 1 — pick a plan, pick a location
The /deploy/ configurator walks you through plan tier, datacenter, OS, optional add-ons (extra IPv4, larger disk). It's a six-step progressive form; each step appears as you fill the previous. No account is required to reach the payment step.
The configurator doesn't ask for an email until the very end, and even there it's the email you want server credentials sent to — it's not used for verification or marketing. You can use any working email, including aliases (anonaddy, simplelogin, mailtm).
Step 2 — order created, redirect to /pay/
Submitting the configurator creates a server-side order record, generates a unique order ID (CS-ORD-XXXXXXXXXX), and redirects you to /pay/
Important: your root password (if you set one) is never persisted on our side. We hash a confirmation flag and forget the plaintext. The only way to recover it is to set it on first SSH login via cloud-init, which is the standard pattern.
Step 3 — pick the coin you want to pay in
You'll see a shortlist of supported coins, filtered live against current liquidity: BTC, XMR, LTC, ETH, USDT-ERC20, USDT-TRC20, DASH, BCH, DOGE, SOL. The list adjusts in real time — coins that are temporarily disabled (rare, but happens during chain congestion) drop out.
There's no preferred coin from our side — pay in whatever you hold. Behind the scenes the checkout settles to either Monero or USDT regardless of what you sent, so your coin choice is purely an ergonomic decision (lowest fees: LTC/DOGE; most private: XMR; most stable: USDT).
Step 4 — locked-rate deposit address
Choosing a coin returns a deposit address specific to your order, plus the exact amount to send and a 30-minute rate window. The amount is the USD price of your plan converted at the rate quoted at that moment; if you send less, the system tops up the difference at the new rate; if you send more, the surplus credits to your account.
30 minutes is enough for any coin on this list — even Bitcoin gets one confirmation within that window with a normal-priority fee. The system also supports late payments: if you pay 4 hours later at a different rate, we still credit it correctly, you just may need to top up a small delta.
Step 5 — sending the payment
Send from any wallet. Hardware wallets (Ledger, Trezor), Monero CLI, Sparrow, Electrum, mobile wallets, exchange withdrawals — all work. We don't fingerprint where the funds came from, and we don't share that data with anyone.
QR code is provided for mobile wallets. The deposit address is single-use per order — sending to it after the order completes will not credit a new server (it'll bounce back into the float and you'd need to contact support to recover it).
Step 6 — confirmation and provisioning
Status moves through `awaiting → confirming → paid` as the network confirms your tx. Most coins paid: 1–3 confirmations are enough; the threshold scales with the value being moved (small plans = 1 confirmation; dedicated tiers = 3). The /pay/ page polls every few seconds; you don't need to refresh.
On `paid`, the orchestrator picks up the order from the queue and provisions the server. Median end-to-end time from confirmed payment to a working SSH login is 41 seconds for VPS, 2–4 hours for dedicated (because it involves physical racking and IPMI setup).
Credentials land in the email you provided, encrypted to a one-time key bound to the order ID. They also appear in your /panel/ if you opted to create an account; account-less customers receive everything by email.
What we settle into — and why it matters
Internally, every payment settles into either Monero or USDT, regardless of the coin you sent. The choice depends on liquidity and routing at that moment; in practice ~70% of orders settle to USDT (cheapest hop), the rest to Monero (preferred when the inbound was already privacy-routed).
Why this matters to you: it means we don't accumulate piles of dust in a dozen different chains. We hold treasury in two coins, with predictable accounting and minimal chain-analysis surface. From your side it's invisible — you sent BTC, the server provisioned, and our books show what we needed them to show.
It also means: if you sent a coin we don't directly settle into (LTC, DOGE, DASH, BCH), there's a small spread between what you paid and what we received. We absorb that spread; you're charged the USD price of the plan, period.
Failure modes and how they resolve
Underpayment (you sent slightly less than the quoted amount): the system shows an underpayment notice and a top-up address. Send the delta, the order proceeds.
Overpayment (you sent more than the quoted amount): the surplus credits to your account; on next renewal it's automatically applied. You can also request a refund to a different address.
Late payment (the rate window expired): the system computes the new amount in your coin at the current rate and shows a refreshed quote. Your already-sent funds count toward the new total.
Wrong coin sent (you used a BTC wallet to pay an LTC invoice — happens more than you'd think): contact support with the tx hash; we recover the funds and credit them to a fresh order. Worst case takes 48 hours.
Network congestion delays the confirmation: the order sits in `confirming` until the threshold is met. We've seen Bitcoin take 45 minutes during peak congestion; we don't time out the order until the rate window expires, and then we just re-quote.