Plans and limits
What a licence may download and fetch per day, what happens over a limit, and how to stay under it. Prices and what each plan includes are on Pricing.
In short
- Licensed build downloads: 20 per minute and 30 per 24 hours of the same build. Launches that find the build in their cache never count.
- Different personas per day: 750 on Free, 1,000,000 on paid plans. Relaunching a seed you already used today is free.
- Over a limit you get HTTP 429. Keep the browser cache on a volume and reuse a fixed pool of seeds.
Download limits
Downloads of the licensed build are rate-limited per licence, so a setup that fetches the full archive on every start can't run away. A launch that finds the build in its cache doesn't download anything and never counts — only real downloads do.
| Limit | Applies to | Counts |
|---|---|---|
| 20 downloads per minute and 30 per 24 hours | Every licence, per build (version + OS) | Archive downloads of the same build. A new release starts with a fresh budget. |
| 10 different builds per 24 hours | Free licences | Distinct builds fetched. A build you already downloaded today costs nothing again. |
| 60 checks per minute | Per IP address | The build check every launch makes to /api/v1/download/pro, cached or not. |
Over a limit, the SDK gets HTTP 429 with a JSON body — code is DOWNLOAD_RATE_LIMITED (per-build budget) or DOWNLOAD_LIMIT_EXCEEDED (free plan) — and a Retry-After header: the seconds until that limit resets. Launches whose build is already cached keep working. From SDK 0.62.0, a launch that cannot download a new build starts the newest build of the same Chromium version already in its cache instead of failing, and waits for Retry-After before it tries that download again. A launch pinned to an exact revision (r50) still gets that build or an error.
You hit these when many fresh machines or containers start at once, each with an empty cache. Download each build once per machine instead of once per start — starts get faster too, without a ~460 MB download:
- Keep the cache on a volume. Point
CLEARCOTE_CACHEat a directory that survives restarts. Starts that share it wait for the first download and reuse it. - Bake the browser into your image. Run
clearcote installat build time, so every container starts with the build in place. Rebuild the image when you upgrade.
# 1. a shared, persistent cache
docker run -v clearcote-cache:/clearcote-cache -e CLEARCOTE_CACHE=/clearcote-cache …
# 2. or in your Dockerfile: download once while the image is built (the key stays out of the layers)
ENV CLEARCOTE_CACHE=/opt/clearcote-cache
RUN --mount=type=secret,id=clearcote_key \
CLEARCOTE_LICENSE_KEY="$(cat /run/secrets/clearcote_key)" clearcote installNeed a higher limit? Tell us how you run Clearcote and we'll raise it for your licence.
Chat with usPersona limits
Every launch fetches its persona (the fingerprint that seed and options describe) from the persona service. Each licence can fetch a set number of different personas per day. Fetching a persona you already used today costs nothing, so a fixed set of profiles can relaunch as often as you like.
| Plan | Different personas per day |
|---|---|
| Free | 750 |
| Pro and other paid plans | 1,000,000 |
A persona is one seed with one set of fingerprint options (brand, platform and so on), so the same seed as Chrome and as Edge counts twice. The count resets at 00:00 UTC. Over the limit, the launch fails with HTTP 429 from the persona service (daily persona quota reached) until the reset.
You hit this when every launch uses a brand-new random seed. Reuse a fixed pool of seeds instead, for example a list of a few hundred names you rotate through: each one keeps the same fingerprint every time it starts, and relaunching it never counts again.