Short answer: a Windows RDP is the right home for bots that need Windows or a real desktop: game clients, Windows-only automation tools and browser bots. Count on roughly 1–2 GB of RAM per bot that runs a game client or a full browser; the 6 GB plan ($13 a month) runs two to four light bots, the 12 GB plans more. Scripts without a screen run cheaper on a Linux VPS. Bots must follow the rules of the service they use, and spam, fake account farms or attacks get a server shut down.
Running a bot on your own PC means the PC can never sleep, restart or be used for anything heavy. An RDP moves the bot onto a server that runs around the clock with a fast connection, and you check on it from anywhere with Remote Desktop. Here's how to size it and keep it running.
01Windows RDP or Linux VPS?
| Your bot | Use | Why |
|---|---|---|
| Game client bots, Windows-only automation tools (.exe) | Windows RDP | They only run on Windows |
| Browser bots you want to watch (Selenium, Playwright headed) | Windows RDP | A real desktop and browser |
| Headless browser automation, scrapers, API bots | Linux VPS | Cheaper and lighter, from $3.90 |
| Telegram and Discord bots | Linux VPS | No desktop needed; see Telegram bots |
| Trading bots, MetaTrader | Either | See VPS for trading bots |
02How Much RAM and CPU per Bot
RAM runs out long before CPU does.
Rough guide from typical workloads; measure your own bot in Task Manager after an hour of running:
| Bot | RAM per instance | Rdp.Vision plan that fits |
|---|---|---|
| Light script or tool, no UI | 100–300 MB | 6 GB runs many |
| Browser with one tab | 0.5–1 GB | 6 GB: 3–4 bots |
| Game client (2D / older 3D) | 1–2 GB | 6 GB: 2–3 bots |
| Game client (modern 3D) | 2–4 GB | 12 GB plans |
There is no GPU on our servers. Games run with software rendering, which works for older and lightweight clients but not for modern 3D games at decent frame rates. Test one bot on the smallest plan before scaling up.
Full RDP access · NVMe storage · DDoS protection · No setup fee
03Keeping Bots Running 24/7
Disconnect, don't log off
Closing the Remote Desktop window keeps your session and its programs running. "Sign out" closes them.
Start bots at boot
Put a shortcut in the Startup folder (shell:startup) or use Task Scheduler with "run whether user is logged on or not" for tools that don't need a window.
Control Windows Updates
Set active hours in Windows Update so restarts happen when you choose.
Watch it from outside
A heartbeat to a Telegram bot or an uptime monitor tells you when something stops.
Keep a backup
of bot configs and scripts off the server; a reinstall wipes everything.
04Game Rules: Know Before You Bot
Many online games forbid bots and automation in their terms of service and ban accounts that use them. That's a contract between you and the game, not something we police, but it means your game account is at risk, whatever server the bot runs on. A server doesn't make a bot undetectable.
05What Isn't Allowed
Some "bots" are just abuse. These get a server suspended:
- Spam of any kind, by email, messenger or comments. Outgoing mail on port 25 is blocked on every server.
- Mass fake account creation and credential stuffing.
- Attacks: DDoS, brute force, port scanning.
- Anything illegal, including fraud and unauthorised access.
The full list is in the Terms of Service. Keeping these out is what keeps our IP addresses clean, so your bots don't hit captchas and blocks.
06Multiple Bots, Multiple IPs?
Each server has one IPv4 address. If your bots need separate addresses, run them on separate servers, possibly in different locations: Amsterdam, Frankfurt, Warsaw, Romania, New York and Hong Kong.
Running the bot on Linux instead? Our guides cover Telegram bots, Discord bots and any Python script as a service that restarts itself.
A Windows server you connect to with Remote Desktop and use to run bots around the clock, so they don't depend on your own computer.
- botting rdp
- rdp for bots
- bot rdp
- windows rdp for automation
- rdp for game bots
- vps for bots
- browser automation server