Billing & plan
How the organization's plan works, the event quota, and what happens when it's exceeded.
The billing axis is the event, not the domain
Unlike most CMPs, tripticonsent doesn't bill per site or per domain. Each organization has a single monthly quota of consent events (consent.record + preference.record), consumed across all of its sites combined. Adding a new site never changes the price.
Plans
| Plan | Includes | Overage |
|---|---|---|
| Hobby | 1,000 events/month, free, no card required | Not applicable — see below for what happens at the limit |
| Growth | 10,000 events/month included | Billed per additional event, aggregated into the monthly invoice |
| Scale | Negotiated volume, by contract | Volume-discounted rate |
No paid plan gates functionality — webhooks, TCF, DSAR, the cookie scanner and MCP access are available on every plan. The plan only determines volume and support level.
What happens past the quota
- Hobby: a 20% grace band applies above the included events. Past that, new writes are rejected until the plan is upgraded — a consent event is never silently dropped, the request fails explicitly instead.
- Growth and Scale: never blocked. Overage is billed once on the next invoice, not as standalone charges per event block — one predictable line item, not a stream of micro-charges.
Spending ceiling (optional)
On Growth, a monthly overage spending ceiling can be set from Settings → Billing. Recording keeps working normally up to that ceiling (with the same 20% grace band); past it, recording pauses until the next period or until the ceiling is raised. It's an explicit choice by the organization owner, not a default behavior.
Changing plan
From Settings → Billing: Upgrade to Growth opens Stripe Checkout; once subscribed, the organization sees a Manage in Stripe button, which opens the Stripe billing portal to change plan, update the payment method, or cancel.