Anchor Browser Review 2026
Cloud browser sessions for AI agents, driven over CDP, with your own proxy set at session creation
Anchor Browser gives AI agents and automation code a real browser in the cloud. A session is created through the SDK or REST API and driven over CDP with Playwright or Puppeteer, through natural-language tasks, or through REST endpoints, with managed authentication, profiles, recordings and a live view around it.
Anchor publishes a free tier with $5 of credits a month, Starter at $50/month and Growth at $2,000/month. These figures are as published by Anchor.
What a session gives you
Four parts of the service, as Anchor describes them in its documentation.
Browser sessions over CDP
A session is created through the SDK or REST API and comes back with an id, a CDP URL and a live view URL. Playwright connects with connectOverCDP and Puppeteer with browserWSEndpoint, so existing automation code keeps working.
Bring your own proxy
The session body accepts a proxy object with type "custom", a server URL (http, https or socks5), a username and a password, so every request the cloud browser makes leaves through the proxy you chose.
Tasks and managed authentication
Besides raw sessions, Anchor runs natural-language web tasks, keeps authenticated identities with MFA, persistent profiles and volumes, and records sessions with a live view for debugging.
Published pricing
A free tier with $5 of credits a month, Starter at $50/month and Growth at $2,000/month; browser time is $0.05 per hour plus $0.01 per browser. Bring-your-own-proxy sits on the Growth and Enterprise plans in the docs pricing table (figures as published by Anchor).
Anchor sessions on PROXIES.SX exits
Pass the gateway as the custom proxy when you create the session. Use one sticky session id per agent task, so every page the task opens leaves from the same residential or mobile exit, and pick the country in the username.
"proxy": {
"active": true,
"type": "custom",
"server": "http://gw.proxies.sx:7000",
"username": "psx_ACCOUNT_ID-peer-us-rot-sticky-sid-TASK_ID",
"password": "PROXY_PASSWORD"
}SOCKS5 works the same way with socks5://gw.proxies.sx:7001. The session id must not contain a hyphen. Then connect to the returned CDP URL exactly as you would without a proxy; the exit is chosen by the PROXIES.SX username.
PROXIES.SX sells residential and mobile proxies per GB through gw.proxies.sx (HTTP on port 7000, SOCKS5 on 7001), from $4/GB down to $2.40/GB from 250 GB. For a whole dedicated device, Private modems rent a 4G/5G modem by the day, week or month.
Frequently asked questions
What is Anchor Browser?
Anchor Browser is cloud browser infrastructure for AI agents and automation. You create a browser session through its SDK or REST API, then drive it over CDP with Playwright or Puppeteer, through natural-language tasks, or through REST endpoints.
Can I use my own proxy with Anchor Browser?
Yes. At session creation, pass a proxy object with active true, type "custom", the proxy server URL, a username and a password. Anchor supports HTTP, HTTPS and SOCKS5 proxy servers. In its published pricing table, bring-your-own-proxy is listed on the Growth and Enterprise plans.
How much does Anchor Browser cost?
Anchor publishes a free tier with $5 of credits a month, Starter at $50/month and Growth at $2,000/month, with Enterprise on request. Infrastructure use is billed at $0.01 per browser and $0.05 per browser hour; Anchor's own proxy is $8 per GB, and egress through your own proxy is $0.20 per GB. These figures are as published by Anchor; check its pricing page before you plan a budget.
How does Anchor Browser fit with PROXIES.SX?
Set the custom proxy object to gw.proxies.sx with your PROXIES.SX pool credentials and one sticky session id per agent task. The cloud browser then runs on a residential or mobile exit in the country you chose, and the whole task keeps the same exit.