All articles
EngineeringJune 5, 2025· 4 min read
Why we built inactivity timeouts
A small feature that quietly saves you money and keeps stuck sessions from lingering.
FT
Ferr Team
Engineering
A browser that nobody is driving is just a meter running. Inactivity timeouts close a session automatically when it goes quiet, so a crashed agent never leaves a browser open for hours.
Sensible by default
- Close after a configurable idle period
- Protect against runaway costs
- Override per session when you need a long-lived browser
The result
Ferr gives you a browser API you can call from anywhere — launch a session, drive it with the SDK or plain CDP, and get logs and replay for free.
Build it on Ferr
Launch your first cloud browser for free.
Keep reading
All articlesEngineeringMay 29, 2026
Meet Atlas: the Ferr session runtime
Atlas is the orchestration layer that turns a single browser call into a managed fleet.
Read article7 min read
EngineeringMay 22, 2026
Ferr SDKs for Rust and Go
Typed, idiomatic clients for two languages systems teams live in — both wrapping the Sessions API.
Read article5 min read
EngineeringApril 2, 2026
How modern anti-bot defenses actually work
Fingerprinting, behavioral signals, and challenge flows — a field guide to what blocks browsers today.
Read article9 min read