# Ferr

> ferr.dev | Compute; 1 record: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/ferr/ | JSON https://fshy.ajam.dev/api/v1/entity/ferr.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## Ferr

- `compute/ferr` | qualifies-with-caveat | evidence documented | binding request-rate | category browser host
- identity a placeholder: card and phone unknown | verified 2026-11-04T05:24:24.920Z (live) | stale on 2026-12-05
- url https://ferr.dev/
- free tier: up to 50 browser hours a month with 3 concurrent sessions on the free tier | unit: hours | metered on: wall-clock | read on: 2026-10-22 | source: [1]
- per-object cap: not stated | source: [1]
- retention: not stated | source: [1] | note: not stated
- egress: not published: the page read states no egress allowance and no overage price per TB | metered: no | source: [1]
- identity: email
- interface: rest
- limits:
  - request-rate (binding): 50 browser hours a month on the free tier; 3 concurrent sessions [1]
  - write-gated: the self-hosted CLI path runs the browser on a user's own machine and is a different product from the hosted hours [1]
- limits note: not stated
- interface detail: Sessions API, Chrome DevTools Protocol, SDKs for Python, Node, Rust and Go; a ferr CLI that runs the open-source browser on the user's own machine
- tooling: Sessions API plus CDP; Python, Node, Rust and Go SDKs
- composes with: the same as limits note
- reliability: no reliability event recorded
- notes: The free tier is metered in browser hours on the vendor's 'warm capacity', not on a machine the user supplies.
- evidence note: the pricing page was read on 2026-10-22 and states the free tier's browser-hour allowance and concurrency.
- extras:
  - keep_rate_basis: no field in the source
  - billing_model: unclassified
  - session_cap.restart_required: no
  - session_cap.note: the month's 50 hours is the bound; sub-second cold starts mean a session need not be held open
  - free_tier_kind: allowance
  - ps.price: profiles store cookies and local storage and are reused across sessions
  - ps.durability: saved profile
  - ps.on_stop: yes
  - ps.on_destroy: no
  - ps.retention: until the profile is deleted
  - net.out: yes
  - net.in: no
  - net.allowance: rotating consumer-connection proxies and an unmarked browser profile mode included
- evidence:
  - [1] 2026-10-02: 
  - [1] 2026-10-22: 'Start free, scale when you do' with 'Up to 50 browser hours / mo' and '3 concurrent sessions' on the free tier, and 'Sub-second cold starts on warm capacity', quoted
  - [1] 2026-11-03: the pricing section meters browser hours and states no egress allowance or overage price | capture: sha256:cccb413be4152e99ba64085a886b467e0c95e441b7cb300a852185951c91af3e | quote: Up to 50 browser hours / mo
  - [1] 2026-11-03: sessions are created over a Sessions API and driven by SDK or CDP | capture: sha256:cccb413be4152e99ba64085a886b467e0c95e441b7cb300a852185951c91af3e | quote: Create a session, get a live browser in the cloud, and drive it with the SDK or plain Chrome DevTools Protocol.
- sources:
  - [1] https://ferr.dev/