Plans & billing
- Written for
- ＋ Written for
- Deprecated
- ＋ Deprecated
- Applies to
- ＋ Applies to
Plans & billing
Cookie Munch prices per organization, not per domain — properties are effectively unlimited on every tier. What actually differs between tiers is monthly consent events, team seats, how many organizations you're allowed to own, and a handful of advanced features. Manage all of it from Account → Plan & usage.
The tiers
Plan | Price | Properties | Monthly events | Seats | Orgs you can own |
|---|---|---|---|---|---|
Free | $0/mo | 50 | 50,000 | 1 | 1 |
Starter | $29/mo | 50 | 500,000 | 3 | 3 |
Pro | $99/mo | 50 | 5,000,000 | 10 | 10 |
Scale | $399/mo | 50 | Unlimited | Unlimited | Unlimited |
"Monthly events" counts consent decisions recorded across every property in the organization combined. "Seats" counts team members with access to the org (see Organization & members). Property count is capped at 50 per org on every plan — it's a ceiling, not something upgrading meaningfully changes; you're paying for headroom on usage and features, not for more domains.
Feature gating
Some capabilities only turn on from Pro upward:
Feature | Free | Starter | Pro | Scale |
|---|---|---|---|---|
Auto-blocking, Consent Mode, geo-targeting | Yes | Yes | Yes | Yes |
IAB TCF v2.2 / GPP / US Privacy | Yes | Yes | ||
Remove Cookie Munch branding (white-label) | Yes | Yes | ||
Enterprise SSO (SAML/OIDC) | Yes | Yes | ||
A/B testing | Yes |
Where a gated control shows up elsewhere in the dashboard (the TCF toggle or the A/B testing switch in Banner Studio settings, for example), it appears disabled with a badge naming the tier that unlocks it, rather than being hidden — so you always know what upgrading buys you before you hit a wall. This gating is enforced server-side too, when a config is saved, not only reflected in the UI.
Viewing usage
Account → Plan & usage shows your current plan name plus a live usage panel with a progress bar for each dimension the API tracks — domains, monthly events, and seats. A badge at the top of the card reads "within limits" when everything's under cap, or "over a limit" the moment any single dimension exceeds it, so you know before something breaks rather than after.
Below the current-plan summary, a "unlock more" section lists premium features you don't have yet on your current tier, each tagged with the tier that grants it — handy for deciding whether an upgrade is worth it before you hit a hard limit.
Upgrading or switching plans
The Plans picker sits at the top of the same card. Each tier shows its price and, depending on your current plan:
Upgrade — shown for any tier higher than the one you're on.
Switch plan — shown for a lateral move between paid tiers.
The Free tier shows no action button when it's your current plan; moving down to Free from a paid plan is done through Manage billing (below), not this picker.
Your current tier is visually highlighted and marked with a Current badge instead of a button.
Clicking a paid tier's button starts a Stripe Checkout session in a new navigation — you're redirected to Stripe to complete payment, then returned to /account?upgraded=1, where the dashboard shows a confirmation toast and immediately reloads your usage with the new plan applied.
If billing isn't configured on your Cookie Munch instance yet (no live Stripe keys set by whoever runs it), choosing a plan shows a friendly "billing coming soon" message instead of failing silently.
Managing billing
Click Manage billing to open the Stripe customer portal in a new navigation, where you can update your payment method, view past invoices, or cancel/downgrade your subscription. If your organization has never had a Stripe customer created for it (typically because it's still on Free and has never upgraded), this shows a "no billing set up yet" message rather than an empty portal.
Tips and gotchas
Because pricing is per-organization, splitting properties across several organizations to save money defeats the purpose of team collaboration (each org has its own separate member list) without actually lowering plan-relevant usage in any useful way — a single org handles many domains fine.
Seat and event limits reset expectations are per billing cycle for events; seats and org-ownership limits are simply hard caps checked live, not something you can temporarily exceed.
If you're inviting a teammate and the button is disabled, check the usage panel first — it's very likely the seat limit, and the hint text links straight to the plan picker.
Downgrades take effect through the Stripe portal, not the in-app picker — don't look for a "downgrade" button next to Free.
Next steps
Organization & members — seat usage and role management in detail.
Properties — the property cap in context.
Overview — how TCF, geo, and other gated features fit into the bigger picture.