Crypto-paid servers
A server of your own, live minutes after you pay
Pay in Bitcoin, USDT or any of 300+ other coins. There is no card form, no bank, no KYC form — and nobody here has to approve anything. The moment your payment confirms, your machine starts building itself, and when it comes up the IP address and root password are waiting in your dashboard.
From $17/mo · full root SSH · NVMe · Ubuntu 24.04 · cancel by not renewing
3live tiers
each one a measured quantity, listed in full below
5regions
across the catalogue — not every tier is offered in every one
24.04Ubuntu LTS
the only image offered, because it is the only one that installs cleanly
2months free
on a 12-month prepay — you pay 10
A tier is a quantity, not an adjective
“Pro” means nothing on its own. Here is what the tiers actually differ by, drawn to scale off the same rows the checkout reads.
The step that matters is where the cores stop being shared
The lower tiers run on shared vCPU and SSD, which is the right trade for a spot exchange finding its first traders. Above that, CPU and memory are reserved to your machine alone and the disk becomes NVMe — and that is the line to look for if you are running the Ecosystem stack, matching, or anything with a websocket fan-out at peak.
Read the bars, not the names. Every figure in the diagram is the plan row itself, so it cannot drift from what you are charged for.
One thing worth knowing before you pick: there is no in-place resize. Moving up a tier means deploying the bigger server and migrating onto it, so buy for a few months out rather than for this week.
Plans
Pick a term. Annual is exactly two months off.
Choose a hostname and a region, and pay in crypto. A 12-month prepay is billed as 10 months — that is the whole discount, and it is the same arithmetic on every tier.
Sized off real Bicrypto deployments
Bicrypto core
A lean spot exchange on the Bicrypto core — enough headroom for your first wave of traders.
Fits on Trader · $17/mo
Configure TraderCore + Ecosystem & addons
Running the Ecosystem stack, staking, P2P, or several addons? This is where cores stop being shared and disk becomes NVMe.
Fits on Pro · $95/mo
Configure ProFull stack + high volume
Every addon, serious daily volume, and room to grow into — dedicated-class resources without the dedicated price.
Fits on Enterprise · $172/mo
Configure EnterprisePick the region first
5 regions across the catalogue — but not every tier is offered in every one, and a region is not something you can change after the fact.
Websocket latency is a distance problem, and distance is bought at checkout
A trader in Singapore on a server in Chicago pays for that round trip on every order book tick, and no amount of CPU fixes it. Choose for where your traders are, not for where you are.
The matrix is the honest version of “global coverage”: a filled cell is a pair you can actually buy today. If the tier you want is not in the region you want, the configurator will tell you the same thing — this just tells you before you have picked.
A late payment suspends your server. It does not delete it.
This is the question every host answers vaguely, so here is the actual timetable — including the part where the automatic road simply ends.
On manual billing there is no destroy step at all
Your server is suspended the moment its paid-until date passes — there is no grace before that, and we would rather you knew than discovered it. Three days later it is marked expired. And then nothing else happens: no sweep deletes it, no timer runs out. Renewing brings it back.
The only path that ends in a destroyed machine is one you have to switch on yourself. With auto-renew enabled, the wallet charge is attempted from 24 hours before the date and keeps retrying — throttled to one attempt every 20 hours — right across the suspension, so a top-up two days late still saves the box. That opt-in path is the only one with a 14-day terminus.
Before any of it, three reminders: ten days out, three days out, one day out. Each sent once.
Your root password is generated, encrypted, and typed by nobody
No human at MashDiv chooses it, sees it in a ticket, or pastes it anywhere. It has three homes and exactly one door back out.
Twenty characters out of a deliberately boring alphabet
Drawn from crypto.randomBytes over 56 symbols with the ambiguous ones removed — no capital I, no lowercase l, no O, no zero, no one — because the first thing that happens to a root password is that somebody reads it off a screen and types it somewhere else.
It is written into the machine’s own first-boot configuration rather than typed in afterwards, so it is already set before the box has finished starting and there is no window in which anyone could have read it in transit. At rest it is AES-256-GCM — a 12-byte IV and a 16-byte authentication tag in front of the ciphertext, which is what makes tampering detectable rather than merely unlikely.
The one way back out is an ownership-checked action in your own dashboard. And if you would rather it were a different secret entirely, a reinstall rotates it.
It is your machine. These are the controls.
Listed as what they are rather than as a longer list — the buttons below are the ones that exist.
Power, from your own dashboard
Stop and start your server yourself. It is a button on the server card, not a ticket, and it takes effect on the machine immediately.
Reinstall the OS, and get a new root password with it
A reinstall wipes the machine back to Ubuntu 24.04 and rotates the root password in the same move — the new one is encrypted and waiting in your dashboard when the server comes back. It is the recovery path for a box you have painted yourself into a corner on.
Real root, not a panel account
You get the actual root credentials for the actual machine. Nothing on it is ours: install what you like, break what you like, and no support ticket stands between you and your own server.
One OS image, on purpose
Ubuntu 24.04 LTS and nothing else. 22.04 cannot run Bicrypto and 26.04 is not production-graded yet, so offering a menu of images would mostly be offering a menu of ways to fail an install.
Overpay in crypto and the difference comes back
Send more than the invoice and the excess is converted to USD and credited to your store wallet, once, idempotently. Under fifty cents it is treated as dust and dropped, because moving it costs more than it is worth.
A replayed payment callback cannot deploy a second server
Every callback is signature-checked with HMAC-SHA512 over key-sorted JSON and then de-duplicated on the payment and status it claims to be. Three independent guards sit on that path, so a duplicate notification, an admin retry and the five-minute recovery sweep all arrive at the same harmless no-op.
A stuck order fixes itself
If a payment settles and provisioning does not, a sweep running every five minutes picks the order back up ten minutes later and finishes it. Nobody has to notice, and you do not have to ask.
FAQ
The questions worth asking before you pay
Configure a server. It deploys itself.
Pick a tier and a region, choose a hostname, and check out with any of 300+ cryptocurrencies. The next human involved is you, over SSH.
No card, no bank, no KYC form · add a domain · have us install it