cdpfleet Pre-launch Get early access

cdpfleet / Community plan

Free plan · invite-only for now

Real browsers in the cloud, free.

The Community plan gives you 2 threads with 60 browser-minutes each per day, every browser on the fleet and a proxy included — for trying cdpfleet and for small projects. No trial expiry, no charges.

  • 2threads
  • 60min per thread per day
  • 15min per session
  • $0forever

What you get

Community is a shared plan with the same fleet as the paid ones: Google Chrome with its channels, Edge, Brave, Opera, Firefox, Camoufox, WebKit and the stealth builds — 12 desktop browsers, driven with Playwright from Node.js, Python, Java, C# or Go, or over CDP.

A headless browser takes 1 thread and a headful one 2, so you can run two headless sessions or one headful session at a time. Minutes are counted per thread: a headful session uses both threads' minutes — up to 60 minutes of headful a day, the same as two headless sessions of 60 minutes. The allowance resets at midnight UTC.

Community — free

Free forever, for trying cdpfleet and small projects: every browser on the fleet, with proxies included. No trial expiry and no charges — you verify a card once, one account per card. Invite-only while we open up: join the waitlist.

Threads
2 (a headful browser takes both)
Browser-minutes
60 per thread per day
Session length
Up to 15 minutes
Proxies
Included, shared — slower at peak
Priority
Lowest; capacity shared by all Community users
Not included
Recordings, persistent profiles, keep-alive

The residential proxy can be added as on any plan. Request data from Community sessions may be used to learn which browser setups work on which sites, so don't sign in to accounts on it (Terms, section 4A).

A proxy is included

Every cdpfleet session goes through a proxy. On Community the plan brings its own: leave proxy out of the launch and the session uses the Community proxy, or send a cdpfleet-plan token to choose an exit country and keep the same IP for a while — the dashboard's Proxies page builds the token for you.

The Community proxy is shared by everyone on the plan, so pages load slower at peak times. Your own proxies work too, and the residential proxy can be added from a prepaid balance exactly as on a paid plan.

A Community session through the included proxy, exiting in the US
// npm install [email protected]
// Browsers run on cdpfleet, so no `npx playwright install` is needed.
import { chromium } from 'playwright';

const KEY = process.env.CDPFLEET_API_KEY;

// 1. Launch the browser
const res = await fetch('https://starter.cdpfleet.com/chromium/session', {
  method: 'POST',
  headers: { 'x-api-key': KEY, 'content-type': 'application/json' },
  body: JSON.stringify({
    proxy: 'cdpfleet-plan-country-us',
    headless: 'new',
  }),
});
if (!res.ok) throw new Error(`launch failed: ${res.status} ${await res.text()}`);
const { wsUrl } = await res.json();

// 2. Connect and drive it
const browser = await chromium.connect(wsUrl, { headers: { 'x-api-key': KEY } });
const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());
await browser.close(); // ends the session and stops billing

Limits, and what isn't included

  • Sessions last up to 15 minutes. Within a session the idle timeout is 120 seconds by default; set up to 5 minutes with inactivity_timeout.
  • Lowest priority. All Community users share one capacity cap; when it is full a launch gets 503 community_capacity_full and should retry after Retry-After. When paid plans need room, Community sessions give way first — their leases renew every 5 minutes instead of 15.
  • Up to 25% of the day's minutes in any rolling hour, like every shared plan.
  • Not included: session recordings, persistent profiles (a profile launch gets 403 profiles_disabled) and keep_alive.

How to get it

  1. Signups are invite-only while we open up: join the waitlist and we'll send an invitation.
  2. Sign in to the dashboard and choose Verify a card and activate. Stripe checks the card — it is never charged — and one card holds one Community account.
  3. Create an API key, pick a browser in the code generator, and run the program it writes — or press Launch interactive to try the browser live first.

Outgrow it any time: a paid plan is one click in the dashboard. A paid plan can also move back to Community at the end of its billing period.

Your data on Community

Request data from Community sessions may be used to learn which browser setups work on which sites. Don't sign in to accounts or handle personal data on it; the details are in the Terms, section 4A. Paid plans add privacy, priority, more threads, recordings and profiles.