To see what you'll pay and when new events might be refused, open Settings, then Plan and billing. Your organization is on one plan. It sets how many billable units are included each month and how long events are kept. Every app in the organization shares the included units. Only owners can manage the plan.
What a unit is
By default, a unit is one event sent to one destination. Each further destination the event matches adds a quarter of a unit, and every started 128 KiB (131,072 bytes) of payload counts the event again. An event no destination receives counts half a unit. A negotiated plan can set other weights.
Retries and resends of a delivery don't count.
The free plan
A new organization is on the free plan, without a subscription or a payment method. It includes a small number of units each month, enough to integrate and test. Settings shows the exact number.
Once the organization has used its included units for the month, POST /v1/events answers 402 with the code quota_exceeded, and test events from the console are refused the same way. Nothing is stored for a refused request, and reads still work. The refusal ends within the first hour of the next month in UTC, or when the organization chooses a paid plan.
Paid plans
A paid plan has a monthly fee, more included units and longer retention. Units past the included ones are billed in tiers that get cheaper at volume, and the events are accepted as usual. Settings lists the plans and their prices. Prices are in euros and exclude tax; checkout adds the tax for your billing address.
To choose a plan, an owner selects Choose next to it and completes the Stripe Checkout page. The plan applies as soon as the payment succeeds. The subscription renews on the first of each month, and the first payment covers the rest of the current month.
An owner can switch an active subscription to another plan from the same list. The switch applies at once, and the difference is prorated on the next invoice. A switch to a plan that keeps events for less time applies that retention at once too: events older than it are deleted within a minute and can't be restored. Settings asks you to confirm first.
Plan limits
Settings lists each plan's limits, and the limits of your current plan. Every plan has all of them.
- Destinations. How many destinations each app can have. Creating one past the limit answers
400. Delete one, or choose a larger plan. - Event size. The same on every plan: a request to
POST /v1/eventsor a source URL may be at most 262,144 bytes (256 KiB). A larger request answers413. - Delivery rate. The most requests a second PayloadPuffin sends to one destination. A destination's rate limit and burst may be at most this number. A destination left on the defaults is sent at the plan's rate.
- Ingest rate. The events a second the organization may send, shared by every app and API key. It may send two seconds' worth at once. Past that,
POST /v1/eventsanswers429with the coderate_limitedand aRetry-Afterheader; retry after that many seconds. The rate is per second, not averaged over a longer period. - Ingest volume. The request bytes the organization may send, shared like the ingest rate. At your plan's ingest rate, each event may average one 128 KiB size unit; the per-minute cap is 30 seconds of that. Settings shows both numbers. A quiet organization may send at the per-second cap until the minute's bytes run out. Past either cap,
POST /v1/eventsand a source URL answer429withRetry-After, as for the ingest rate. - Team. Members and pending invitations together. Inviting someone past the limit answers
400.
Every plan also caps an app at 3,500,000 events held within the plan's retention. Past that, POST /v1/events answers 429 with the code rate_limited, the reason app_event_ceiling, and a Retry-After for when the oldest events expire. Choose a plan with shorter retention, or send fewer events to that app.
After a move to a smaller plan, existing destinations and members stay. Shorter event retention can delete older events, as described under Paid plans. Destinations past the limit keep delivering, but you can't create a new one. A destination whose rate or burst is above the new plan's delivery rate is sent at the plan's rate, and its settings show that rate. Members stay, and only new invitations are refused.
Refuse events instead of paying for overage
An owner of a paid plan can choose Refuse with 402 under When the included units run out. Events past the included units are then refused with quota_exceeded instead of billed. Choose Keep accepting, bill per unit to bill them again.
Usage
Settings shows the organization's units this month, across every app, against the included units. The count is updated a few times a day, so it can trail the live count. The meter in the sidebar shows the same organization-wide usage.
To read one app's usage, use the API:
curl "https://api.payloadpuffin.com/v1/analytics/usage" \
-H "Authorization: Bearer $PAYLOADPUFFIN_API_KEY"unitsThisMonth counts billable units for the API key's app only. unitQuota is the organization's included units per month, shared by every app. quotaExceeded is true while the organization refuses ingestion because its included units have run out. This response doesn't give the organization's total usage; use Settings for that.
Because usage is counted a few times a day, the refusal can start a few hours after the included units run out. Events accepted in that time stay accepted. They aren't billed when the organization is on the free plan or has chosen Refuse with 402.
Invoices, payment method and canceling
An owner selects Manage billing to open the Stripe billing portal. There you update the card, download invoices, and cancel the subscription at the end of the period. After the subscription ends, the organization is on the free plan again, and its included units and the refusal past them apply at once.
Its data isn't cut to the free plan's retention at once. When a subscription ends, the paid plan's retention stays in force for as many days as it keeps events: 14 days after a plan that keeps events 14 days, 28 after one that keeps them 28. By then every event from before the end has expired under the paid plan's retention anyway. Settings shows the date events older than the free plan's retention will be deleted, and how many days of events that is. Choosing a plan before that date ends the wait, and its retention applies at once.
Any other change to your plan's retention applies at once.
If a payment fails, Stripe retries it. Until it succeeds, events past the included ones are refused rather than billed. If every retry fails, Stripe ends the subscription, and the organization is on the free plan with the same wait as any ended subscription.
Deleting an organization is final: it can't be restored. It reports the usage counted so far and sets its subscription to end at the end of the period. Stripe sends the last invoice then, with that usage, and charges nothing more after it. The organization's data is wiped on the next daily cleanup, and its Stripe customer record is deleted once that last invoice is paid. Deleting an app changes nothing in billing: usage it counted stays on the bill, and the organization keeps its plan.
Plans that change
A plan's terms can change for new subscriptions. An existing subscription keeps its price until it changes plan.