System requirements & VPS

Use this page when a profile will not start, the VPS feels "too small," or you are sizing a Windows host for Botlord + antidetect. Proxy and campaign settings are usually fine — free RAM and desktop session are what break most VPS setups.

Related: Resources & signup stack · Logs

Local Windows PC

The desktop app is built for Windows. Close other heavy apps before your first antidetect test so enough RAM stays free for Electron and a real browser profile.

What uses RAM

A typical antidetect run is not "just the bot" — several processes stack on top of each other:

• Botlord Platform (Electron shell)
• MultiLogin MLX Agent or AdsPower (when antidetect is enabled)
• Each real browser profile (non-headless uses the most RAM)
• CAPTCHA and proxy traffic are light — RAM is almost always the bottleneck

VPS sizing

For 24/7 runs, use a Windows VPS from the resources stack (Hyonix and alternatives). One core can work for a single profile, but RAM matters more than CPU for first-time setup.

Windows Server & RDP

Many operators use Windows Server 2019 VPS images. That is fine when you respect how antidetect browsers launch profiles:

• headless_mode=false (a visible browser profile) usually needs an active desktop session — connect with RDP and keep the session open while workers run.
• Disconnecting RDP in a way that locks the console can make profiles fail even when RAM looks adequate.
• Server Core or session-less automation hosts are a poor fit for non-headless MultiLogin or AdsPower profiles.

Profile won't start on a VPS

Work through this list in order before opening a code defect with support:

1. Step 1

   Check free RAM first

   Open Task Manager on the VPS. If free RAM is only a few hundred MB (e.g. ~275 MB on a 2 GB box), the stack cannot start — Botlord + Electron + MLX Agent + a real profile will not fit.

2. Step 2

   Upgrade and reboot

   Move to an 8 GB RAM plan (or higher), reboot the VPS, and confirm several GB are free before you start anything.

3. Step 3

   Keep RDP open

   On Windows Server, non-headless profiles (headless_mode=false) often need an active desktop session. Connect via RDP, start the profile, and avoid closing the session in a way that locks the console.

4. Step 4

   Start one profile manually

   In MultiLogin or AdsPower, launch a single profile by hand. If that fails, it is provider/MLX territory — not a Botlord code issue.

5. Step 5

   When to contact whom

   Manual profile start works on a roomy VPS but the bot still fails → TheBotLord support with logs. Manual profile start fails even with 8 GB+ free → MultiLogin/MLX support.

When it's not a code bug

If proxies and campaign fields look correct but nothing launches, assume hosting until proven otherwise:

• Manual profile start fails on the same VPS → MultiLogin / MLX support.
• Manual profile start works with plenty of free RAM but the bot fails → TheBotLord support with Logs / debug output.
• We are exploring an in-app low free RAM warning before Start to cut down support tickets — for now, check Task Manager yourself.