Meet Atlas: the Ferr session runtime
Atlas is the orchestration layer that turns a single browser call into a managed fleet.
Under every Ferr session is Atlas, the runtime that schedules browsers onto warm capacity, handles retries, and keeps state consistent when you fan out to thousands of pages at once.
One call, a whole fleet
Atlas exposes the same create-a-session surface whether you want one browser or ten thousand. You describe the work; Atlas places it, watches it, and cleans up after it.
from ferr import Ferr ferr = Ferr()fleet = ferr.fleet.map( urls, stealth=True, concurrency=250,) for result in fleet: save(result.url, result.data)Built for backpressure
When a target slows down, Atlas slows with it instead of hammering the site. That single behavior removes the most common reason large crawls get blocked.
Keep reading
All articlesFerr SDKs for Rust and Go
Typed, idiomatic clients for two languages systems teams live in — both wrapping the Sessions API.
How modern anti-bot defenses actually work
Fingerprinting, behavioral signals, and challenge flows — a field guide to what blocks browsers today.
Errors are the interface agents actually read
If your API errors are vague, your agent will be too. A case for error messages written for machines.