Crypto VPS hosting. Bitcoin, Monero, and nothing else.

The causal chain runs like this, and it runs in one direction only:

Cards → chargebacks → fraud liability → identity verification.

A host accepting cards inherits chargeback liability. A fraudster buys a server with a stolen card, uses it for a week, the real cardholder disputes the charge, and the host eats the loss plus a dispute fee. At scale that is existential, so the host builds fraud controls, and the cheapest effective one is demanding identity documents. Once identity is collected for payments it is retained, reused for account recovery, exported to a CRM, and eventually breached.

Cryptocurrency payments are push transactions. They cannot be reversed unilaterally. No chargeback exposure means no fraud-control case for identity collection means the field is never created. That is why no-KYC and crypto-only are the same decision rather than two separate features.

Payments go straight to our own wallets — there is no processor in between — across 8 assets on five chains. The most-used at checkout:

• Bitcoin (BTC)
• Monero (XMR)
• Litecoin (LTC)
• Ethereum (ETH)
• Tron (TRX)
• Solana (SOL)
• USDT (TRC-20 / ERC-20)
• USDC (TRC-20 / ERC-20)

Stablecoins are the most popular choice by volume, because they remove exchange-rate risk from a recurring bill. Monero is the strongest choice for privacy. Bitcoin remains the most requested and is the slowest to confirm.

1. Configure the server. The configurator prices every unit openly and shows the USD total before you commit to anything.
2. Enter an email address. That is the only personal detail requested, and it exists so root credentials have somewhere to go. Aliased addresses are fine.
3. An invoice opens. Pick your coin and network. You get an address and a QR code, and the exchange rate is locked for the invoice lifetime — 90 minutes — so a moving market cannot change what you owe.
4. Send the payment. The invoice tracks the transaction as it propagates and the status page updates itself.
5. Deployment starts at the first network confirmation. Our published target from that confirmation to a server accepting SSH is 5 minutes.

No account is created, no password is set, and nothing is stored beyond the email address and the transaction reference.

Deployment triggers on the first network confirmation, so the coin you pick determines how long you wait:

If you need a server immediately, pay in USDT on TRC-20. If you need privacy above all, pay in Monero. If you have Bitcoin and no urgency, that is fine too — just set an adequate fee.

Underpayment. Invoices carry a 2.5% tolerance, so ordinary network-fee shortfalls settle normally. Below that the payment is held and support resolves it — you are not silently out of pocket.

Overpayment. The surplus is credited to your service and applied against the next renewal. Ask and we refund it to an address you nominate instead.

The invoice expired before your transaction confirmed. Nothing is lost. Open a ticket with the transaction hash and we match the payment to the order manually. This is routine, especially with Bitcoin.

You sent the wrong asset or the wrong chain. Open a ticket with the transaction hash straight away. Whether anything can be done here is decided by the two networks involved rather than by how hard we are willing to work: some of these come back with the payment processor's cooperation, some need a retrieval path that the receiving chain simply does not have, and some are final from the moment they confirm. We will find out which of the three you are in and say so plainly, including when the answer is that the funds are gone.

You want a refund. The 7-day money-back guarantee pays out to any cryptocurrency address you nominate, less network fees. You do not have to take the refund in the asset you paid with.

There is no stored payment method, because there is nothing to store — crypto payments are push, not pull, so nobody can charge you automatically. Renewal works like this instead:

• Renewal notices go out 7 days, 3 days and 1 day before expiry.
• Each notice contains a payment link for the exact amount due.
• If payment has not confirmed by expiry the server is suspended but preserved intact, and data is retained for a further 7 days.
• Paying the outstanding invoice within that grace period restores the server exactly as it was. There are no late fees.

You can also pre-pay credit against your service and let renewals draw down from the balance, which is the closest thing to autopay that a push-payment system allows. Longer terms are the simpler answer: an annual term takes 20% off and removes eleven renewals from your calendar.