# Remote Browser

Official pricing: https://remote-browser.dev/pricing  
Category: browser · Isolation: container

## Pricing regimes (raw)

- **Purchased browser-hour packs** (sizes): Purchased browser-hour packs ? vCPU/? GiB $0.245/h

## Features

Yes: idle auto-stop, ≥24 h sessions, browser, computer-use API, browser automation API, anti-bot stealth, residential IPs, preinstalled agents, open internet, EU data residency, scoped API keys

No: snapshots, memory snapshots, fork/clone, pause/resume, persistent disk, volumes, start from your own snapshot, your own Docker/OCI image, full VM (own kernel), Docker inside, nested virtualization, desktop GUI, desktop control API, browser + desktop control, CAPTCHA solving, SSH, public IPv4, HTTPS preview URLs, egress allowlist, static egress IP, self-hosting, BYOC, open source, SOC 2, HIPAA, SSO, GPU, arm64, Windows, macOS, Python, Node.js, GPU desktop, HTTP method/path egress rules, wake on request, live resize, live fork (no pause), memory fork, MCP server, automatic snapshots, snapshots on demand, agent harness API, hosted agent API (their own agent), gVisor or VM (no shared kernel), inbound access rules, firewall inside (nftables), secret proxy, secret proxy for any API, extra volumes, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/remote-browser.json → feature_evidence

## Caveats

- Storage, snapshot GiB-month and public IPv 4 prices are not published in the reviewed sources; null is not free.
- No guaranteed vCPU allocation published; browser-hour is not a verified 4-vCPU/8-GiB VM equivalent. The sizes card keeps unknown hardware null; do not coerce it to zero or auto-rank against resource-guaranteed VMs.
- Browser RAM is not published unless a specific mode overrides it.
- Each session is a Kubernetes pod, not a dedicated resource-guaranteed VM. Active browser-hour means alive runtime, not active CPU time.
- Model the top-up as a 20-hour purchase block, not unlimited metered $.245/hour. Credit expiry, proxy bandwidth, CPU/RAM, CAPTCHA fee and storage GiB price not published.
- OS (verified 2026-09-28, remote-browser.dev/architecture): 'Remote-browser runs on Kubernetes. Each session is a pod'; 'One Chromium per pod'. Sessions are Linux containers, so os = ['linux'] (a browser product, not a Linux machine you control).
- SSH: sessions are Chromium pods reached over a CDP socket (remote-browser.dev/architecture, 2026-09-28); no shell/SSH access is offered. ssh = false.
- Default session timeout is 5 minutes (integration env REMOTE_BROWSER_TIMEOUT_MINUTES=5; profile CDP URL '...&timeout=5'); browser-hours accrue until the idle-timeout controller kills the pod or the client terminates it, so every abandoned session carries up to ~5 billed minutes.
- Hard caps, no overage meter: when included browser-hours run out, more runtime only comes from $4.90/20 h one-time packs ('Simple caps, no surprise bills'; billing integration has 'Plan-aware caps'). Bandwidth and recording bytes are metered per org and bandwidth is throttled per session/plan, but no price is published.
- Homepage claims 'Real Chromium in 14 regions' (API region example 'fra1', default 'auto') but publishes no region list (features.regions left null). It also advertises Web Tasks (/v1/tasks), Custom Models routing and 'Remote-browser v3', none of which are in the pricing table; SSH access is mentioned but not documented (ssh=false kept).

## How this provider charges


As of 2026-09-28. USD unless explicitly stated; public list prices unless a row is marked promotion, historical, or quote-only.

## Regime table

| Regime | When it applies | How billed | Numbers / terms | Source |
|---|---|---|---|---|
| Recurring subscription | Managed sessions | Monthly quota | Free 1 h; Developer $4.90/30 h, first month $.10 promo | https://remote-browser.dev/pricing |
| Top-up | Either tier | One-time hour pack | $4.90/20 h; no subscription needed | https://remote-browser.dev/pricing |
| Runtime | Session alive | Browser-hours | Idle timeout closes sessions; stop to end billing | https://remote-browser.dev/pricing |
| Managed or BYO proxy | Regional egress | Price unpublished | Residential country routing, disabled proxy, BYOP documented | https://remote-browser.dev/documentation/browser/proxies |
| Free | Account plan | Monthly fee / commitment | $0; concurrency 1; 1 browser-hour/month; 1 viewer and profile; 1-day recording retention. | https://remote-browser.dev/pricing |
| Developer | Account plan | Monthly fee / commitment | $4.9; concurrency 10; 30 included hours valued at pack rate; 3 viewers/browser,20 profiles,7-day recording retention. First month $.10 promotion. | https://remote-browser.dev/pricing |

## Gotchas

- Each session is a Kubernetes pod, not a dedicated resource-guaranteed VM. Active browser-hour means alive runtime, not active CPU time.

- Model the top-up as a 20-hour purchase block, not unlimited metered $.245/hour. Credit expiry, proxy bandwidth, CPU/RAM, CAPTCHA fee and storage GiB price not published.

- Storage, snapshot GiB-month and public IPv 4 prices are not published in the reviewed sources; null is not free.

- No guaranteed vCPU allocation published; browser-hour is not a verified 4-vCPU/8-GiB VM equivalent. The sizes card keeps unknown hardware null; do not coerce it to zero or auto-rank against resource-guaranteed VMs.

- Browser RAM is not published unless a specific mode overrides it.

## Browser and desktop dimensions

```json
{
  "hour_usd": 0.245,
  "included_hours": null,
  "proxy_residential_gb_usd": null,
  "proxy_datacenter_gb_usd": null,
  "captcha_solve_usd": null,
  "stealth_surcharge_usd": null,
  "recording_storage_gib_month_usd": null,
  "recording_retention": "1 day Free,7 days Developer",
  "persistent_profiles": true,
  "resolution": null,
  "gpu_desktops": null,
  "os_options": [],
  "browsers": [
    "Hardened Chromium"
  ]
}
```

## Worked example

Requested: 4 vCPU / 8 GiB; 50 concurrent × 8 hours/day × 22 days = **8,800 runtime hours**, 1,100 eight-hour starts if recreated daily; 30% CPU; 50 GiB-month snapshots; 100 GiB egress.

50 simultaneous browsers exceeds Developer 10; no eligible public plan. Ignoring that limit, time-only Developer would require ceil((8800−30)/20)=439 packs: $4.90+439×$4.90=$2,156.00, not a valid 50-concurrency quote. Network, hardware and snapshot requirements remain unknown.

## Sources

- https://remote-browser.dev/pricing

- https://remote-browser.dev/llms.txt

- https://remote-browser.dev/architecture

- https://remote-browser.dev/documentation/browser/proxies

- https://remote-browser.dev/documentation/browser/live-preview-recording

- https://remote-browser.dev/documentation/browser/authentication/profiles