pricing.
Two numbers. The second one is the pitch.
$0.10 / browser-hour
# metered per second — others round you up to the minute. billing stops the instant the browser is destroyed
$0 / GB
# bandwidth, proxy, egress — never metered. residential included.
- ▸ Residential egress on every browser — the thing others meter at $4–5/GB — included here.
- ▸ One isolated browser per session, full CDP.
- ▸ No seats, no minimums, no idle charges.
- ▸ $10 of credit to start — 100 browser-hours. No card.
────────────────────────────────────────────────────────────────
## the math against a bandwidth meter
Metered-proxy pricing looks cheap until your agent actually browses. A one-hour session that pulls 250MB through a residential proxy:
elsewhere $0.02/hr + 0.25GB × $5/GB = $1.27
guise $0.10/hr + 0.25GB × $0 = $0.10
The heavier your agent, the wider that gap gets. We can do this because our egress is ours — not rented by the gigabyte.
────────────────────────────────────────────────────────────────
## what's a browser-hour
One browser, alive for one hour of wall-clock time — from the moment your POST returns to the moment the session is destroyed, by you or by its TTL. Not CPU time, not "active" time. It adds up across sessions:
1 browser × 60 min = 1 browser-hour = $0.10
30 browsers × 2 min = 1 browser-hour = $0.10
1 browser × 90 sec = 90 seconds = $0.0025
DELETE early, pay less. Forget to clean up and the TTL caps the damage.