Botlord Platform setup
Antidetect browsers, CAPTCHA APIs, proxies, and VPS — everything to run the unified desktop app at scale. Start with the service signups below, then use the guides at the bottom to install and configure the desktop app.
Before you install
The built-in browser does not require an AdsPower or MultiLogin account. Managed browser providers, CAPTCHA solvers, proxy services and hosting are external options with separate costs. Configure the options your workflow uses; a paid account for every category is not required to save an inactive campaign.
Setting up Botlord Platform uses the same setup steps listed below.
Start with a ready browser runtime and a valid inactive campaign. Add a solver if challenges require it, a proxy source if your workflow needs it, and hosting if you need an always-on machine. Review the module setup checklist before enabling a campaign.
Step 1 — Browser runtime (managed provider optional)
OptionalThe built-in browser runs locally without a separate provider account. AdsPower or MultiLogin is optional when you need their managed profiles.
Note
A separate subscription is needed only for the managed provider you choose. Size its profile allowance to your intended use; do not buy a fixed tier solely to complete this checklist.
What to do
MultiLogin is supported in Configuration if you already have seats.
Step 2 — CAPTCHA solver (if needed)
OptionalConfigure a supported solver if your workflow encounters CAPTCHA challenges. Solver services are separate from your Botlord subscription.
Note
Add about $5–10 USD prepaid balance after signup so solves are available during runs.
What to do
Providers you can use — pick one:
CapMonster
Browser extension CAPTCHA solver — add ~$5–10 USD balance
CapSolver
Browser extension CAPTCHA solver for CapSolver accounts
2captcha
Browser extension CAPTCHA solver backed by 2Captcha
Anti-Captcha
Browser extension CAPTCHA solver for Anti-Captcha accounts
SolveCaptcha
Browser extension CAPTCHA solver for SolveCaptcha accounts
Step 3 — Proxies (optional)
OptionalRotating residential or mobile IPs reduce detection. Useful for production; you can skip this for quick local tests.
Note
Optional for local testing. Recommended for production — use rotating residential or mobile IPs, not your home connection.
What to do
Providers you can use — pick one:
Webshare and GridPanel also work if you already use them.
Step 4 — Windows VPS (optional)
OptionalA VPS keeps campaigns running when your local PC is off or asleep.
Note
8 GB RAM minimum on the VPS — not 2 GB. Windows Server needs an open RDP session for non-headless profiles.
What to do
ProfitServer for budget VPS. ubiDesktop for a full cloud Windows desktop.
VPS sizing & profile troubleshooting →Accounts ready? Use these for install and bot configuration.
Profile won't start on a VPS? Check system requirements (RAM and RDP) before proxy or campaign settings.
Stuck? Contact support — see the Platform guide for install and module overview.