The path in five steps
- Top up your balance with USDT on one of the four networks.
- Open the deploy page and choose a Windows Server image: 2019, 2022 or 2025.
- Pick a plan that can run Windows (Standard, Pro or Beast) and a city.
- Wait for Windows to finish setup, then press "Show password" on the server page.
- Connect with a Remote Desktop client to the server's IP on port 3389 as
Administrator.
Step 1: top up with USDT
USDT goes to your balance through our own payment server on Tron (TRC-20), BNB Chain (BEP-20), Ethereum (ERC-20) or Polygon. The minimum is $5 on any of them, and the balance is held in dollars: 1 USDT credits $1. Tether lists every chain it issues USDT on in its supported protocols page, and the token is the same on all of them. What differs is the network you send it over, so the network in your wallet or exchange must match the one you chose in the payment window.
How long it takes, measured from opening the payment window to a credited balance, including the time you spend copying the address and confirming in your wallet:
- USDT on BNB Chain: median 2.4 minutes, nine payments in ten within 7.1
- USDT on Tron: median 2.6 minutes, nine in ten within 12.2
- USDT on Ethereum: median 4.8 minutes, nine in ten within 10.1
The full breakdown, including other coins and cards, is in how long a crypto payment really takes. If a transfer seems stuck, look it up by its hash on the chain's explorer, such as Tronscan for Tron or BscScan for BNB Chain, to see whether it has left your wallet yet. Network fees and the wrong-network mistake are covered in the USDT top-up guide, and the USDT page has the short version.
How much to top up
Windows has its own price list, because the licence is a real cost on top of the machine. All three plans are billed by the hour from your balance:
| Plan | vCPU | RAM | Disk | Traffic | Monthly | Hourly |
|---|---|---|---|---|---|---|
| Standard | 2 | 4 GB | 80 GB | 3 TB | $79 | $0.108219 |
| Pro | 4 | 8 GB | 160 GB | 4 TB | $159 | $0.217808 |
| Beast | 6 | 16 GB | 320 GB | 5 TB | $269 | $0.368493 |
A deploy goes through once the balance covers one hour of everything on the account, the new server included. So the $5 USDT minimum is enough to start a Standard Windows server, and it keeps one running for about 46 hours. A server is never charged more than its monthly price in a calendar month, and destroying it stops the charge in the same hour.
Top-ups are final: the balance stays on the account as credit for hosting and is not paid back out. The usual pattern is to top up what you expect to use over the next weeks and add more when the warning emails start. Linux plans and every other price are on the price list.
Step 2: deploy Windows Server
On the deploy page choose a Windows image. Three versions are offered: Windows Server 2019, 2022 and 2025. Microsoft's support dates are a reasonable way to choose. Windows Server 2025 is in mainstream support until November 2029 and extended support until November 2034. Windows Server 2022 left mainstream support in October 2026 and gets security updates until October 2031. Windows Server 2019 is supported until January 2029. Pick an older version only when the software you want to run asks for it.
Once Windows is selected, the plan list narrows to Standard, Pro and Beast. The smaller plans cannot run Windows. Microsoft's hardware requirements put the floor for Windows Server 2025 with the desktop at 2 GB of RAM and recommend 4 GB, and 4 GB is where our Windows plans begin.
Windows runs on the Vultr backend only. DigitalOcean, Linode and Hetzner do not offer Windows images through us, so the city list shrinks to Vultr's locations where the chosen plan is stocked. The deploy page only offers combinations that will actually create.
Step 3: get the password and connect over RDP
Windows takes longer to come up than Linux. Our panel estimates a Windows reinstall at around ten minutes against a couple for Linux, and a new server goes through the same setup before it accepts logins. Until setup is done, "Show password" answers that Windows is still finishing setup and asks you to try again in a minute.
When it is ready, the "Windows access (RDP)" card on the server page shows the address as IP:3389, the user Administrator, and the password behind "Show password", with a copy button. That is the password from the install. Change it inside Windows after your first login.
Any RDP client works. Microsoft lists its own clients for Windows, macOS, iOS, iPadOS, Android and the web in Connect to Remote Desktop Services: the Remote Desktop client on Windows, and Windows App on the other platforms. On Linux, Remmina and FreeRDP both connect.
If you lock yourself out of RDP later, the "Console" button on the server page opens a browser console to the same machine. Before you put anything valuable on the server, spend ten minutes on securing RDP: allow port 3389 only from your IP, keep Network Level Authentication on and set an account lockout.
When the balance runs low
You get up to three warning emails, at about 72, 24 and 6 hours of balance left. If the balance does run out, a Windows server is treated like any regular server: it is suspended, its disk is snapshotted, and the snapshot is kept for 7 days. A top-up within that window rebuilds the server from the snapshot with your files and a new IP address. If the Administrator password does not work after such a restore, message support. The whole sequence is described in what happens when the balance runs out.
More on running a Windows VPS paid in crypto, and on what it is good for, is on the Windows VPS page and in the overview of Windows with crypto. Traders choosing a city for MetaTrader have their own guide.