More at once
Community runs 2 headless browsers, or 1 headful. Paid plans start at 5 threads and go to thousands — a test suite or crawler stops queueing.
cdpfleet / Community vs paid
Community → paid
Outgrowing free? Here is what changes.
Community is for trying cdpfleet and small projects. A paid plan starts at $7.50 a month and removes the limits you hit first: more threads, more minutes, longer sessions, priority over free traffic, and the features Community leaves out.
- 5+threads (Community 2)
- 8×the daily minutes per thread, or unlimited
- 24 hsessions (Community 15 min)
- $7.50a month to start
At a glance
| Community (free) | Shared (from $7.50/month) | Dedicated ($8.50/thread/month) | |
|---|---|---|---|
| Threads at once | 2 | 5–1,000 | 5–10,000, custom above |
| Browser-minutes | 60 per thread a day (120 in all) | 60 / 120 / 240 / 480 per thread a day, pooled across threads | Unlimited, 24/7 |
| Session length | Up to 15 minutes | Up to 24 hours | Up to 24 hours |
| Idle timeout | Up to 5 minutes | Up to 10 minutes | Up to 24 hours |
| Capacity | Lowest priority, one cap shared by all free users; gives way first | Priority over Community; 15-minute leases | Reserved — never reclaimed |
| Per session | 50 pages, 2 GB memory | 50 pages, 4 GB memory | 50 pages, 6 GB memory |
| Proxies | Included Community proxy (shared, slower at peak) or your own | Your own at full speed, residential, or the Community proxy | Your own at full speed, residential, or the Community proxy |
| Recordings | No | Yes; HD recording plans to add | Yes; HD recording plans to add |
| Persistent profiles | No | 20 per thread (at least 100) | 30 per thread (at least 100) |
| Kept downloads | No | Yes, 2 days | Yes, 2 days |
| Functions | Pooled browser | Pooled, or your own browser and device | Pooled, or your own browser and device |
| Function jobs — batch, crawl, map, watch, warmup | No | Yes | Yes |
| Monitors — a page checked on a schedule | No | Yes, every 15 minutes or more | Yes, every 5 minutes or more |
keep_alive (reconnect) | No | No | Yes |
| Your request data | May be used to learn which setups work (Terms 4A) | Private | Private |
Why people upgrade
More minutes
60 minutes per thread a day goes fast. Shared plans give 60, 120, 240, 480 minutes per thread a day; dedicated threads run around the clock.
Long sessions
Community ends every session after 15 minutes. Paid sessions last up to 24 hours, with longer idle timeouts for human-in-the-loop work.
No "busy, retry"
Free capacity is shared and gives way to paid traffic first, so peaks bring 503 community_capacity_full. Paid plans get priority; dedicated capacity is reserved for you.
Recordings and profiles
Watch any session back as video, and keep logins, cookies and storage across sessions with persistent profiles — both included in every paid plan.
Learn more →Jobs and monitors
Crawl a whole site, run thousands of URLs as a batch, watch a page live or get told when it changes — Function jobs and monitors run on paid plans only.
Learn more →Privacy and speed
Paid sessions are private, and your own proxies run at full speed instead of through the shared free proxy.
Which plan to pick
- Just more than Community: Shared 60 with 5 threads — $7.50 a month, 300 browser-minutes a day.
- Daily jobs and CI: a bigger Shared plan; minutes pool across threads, and up to 25% of the day's pool can go in any hour.
- Always-on or long-running work: Dedicated threads at $8.50 each — unlimited minutes, reserved capacity and
keep_alive.
Every price and size is on the pricing page; the threads page explains how threads and minutes are counted.
How to switch
- Open the dashboard and go to Subscriptions.
- Pick a plan and size and pay with Stripe. The paid plan replaces Community at once — your API keys, proxies and settings stay as they are.
- Changed your mind later? A paid plan can move back to Community at the end of its billing period.