Cloud GPU rental: frequently asked questions

The model is boring on purpose: we commit capacity in verified datacenters at wholesale, price from the public marketplace median minus 30%, and skip the expensive parts of a cloud business (sales teams, card-fraud losses, free-tier subsidies). The price is the marketing.

No. GPU seconds at rate/3600, storage at allocated GB-seconds, bandwidth at bytes transferred. The ledger shows raw numbers; totals round only at display time.

Every top-up generates a receipt with its on-chain reference, and the billing page exports a monthly usage statement (CSV/JSON) suitable for accounting.

They stay on the account — credits do not expire. See the terms for the (narrow) refund policy: unused credits are refundable in the original coin on request, minus network fees.

Dedicated. A deployed GPU is passed through to your instance alone — no MIG slicing, no time-sharing, no noisy neighbours on the silicon. CPU cores and RAM are likewise reserved.

Yes — the console lists individual machines with CPU, RAM, disk bandwidth, network and port budget. Deploy targets that machine, and start/stop returns to the same machine class.

Containers are Linux. Full VMs can boot a Windows image you licence yourself (BYOL) — most rendering shops use the Linux builds of their tools instead.

Hosts run the current NVIDIA production branch; templates carry CUDA 12.4–13.0 userspace. The offer card shows the max CUDA per machine — filter if you need a floor.

USDT (TRC-20 and ERC-20), Bitcoin, Monero, Litecoin, Ethereum, TRON and Solana. No cards, no bank transfers, no KYC.

Underpaid: the payment page shows the exact remainder to send to the same address. Overpaid: the excess credits automatically. Sent after expiry or on the wrong network: open a ticket with the tx hash — recoverable cases are recovered.

Card processing means chargebacks, fraud-scoring users, and identity paperwork. Crypto settlement is final and lets us keep zero payment PII — which is also why we can afford not to store IP addresses. It is a privacy feature and a margin feature at once.

Email, Argon2id password hash, balances, instance metadata and tickets. No names, no addresses, no cards, no stored IPs. The privacy policy is short because the data is.

Sub-accounts with separate balances and API keys ship with enterprise reservations; for self-serve, one account per human plus per-consumer API keys covers most teams.

Reset link from the sign-in modal to your account email. Note that a password change signs out other sessions but leaves API keys valid — revoke keys separately if compromised.

Tickets in the console, 24/7, median first answer under two hours. Every answer also lands in your email inbox. There is deliberately no public support email address — tickets authenticate you and keep account context attached.

Yes — /status shows live per-region state, component health and 90-day uptime, no login needed.