Billing, usage & spend cap
Flat plans capped by reachable MAU, what counts, and how the spend cap works.
#What you pay for — flat plans, capped by reachable MAU
Pushlane charges a flat monthly fee per plan, capped by your reachable monthly active users (MAU). Your reachable figure is the intersection of two sets, recomputed each calendar month (UTC):
- Active this month — distinct users with at least one event in the current calendar month, straight from the ClickHouse event ledger (the single source of usage truth).
- Reachable — the user has at least one active device and has not opted out of marketing. This mirrors the delivery gate exactly: a user we would not push to never counts toward your cap.
#How the price is computed
Each plan is a flat monthly fee with a hard cap on reachable MAU. There is no per-user overage and no usage meter — within your cap everything is included; when you outgrow it you move up to the next plan (or to Enterprise):
| Plan | Price / mo | Reachable MAU cap | When you exceed |
|---|---|---|---|
| Free | $0 | 1,000 | hard cap — upgrade to Growth |
| Growth | $299 | 100,000 | upgrade to Enterprise |
| Scale | $1,299 | 500,000 | upgrade to Enterprise |
| Enterprise | Custom | Custom | contact sales |
Your subscription is a flat monthly charge — nothing is metered or reported per-MAU. The dashboard always shows your live reachable MAU against your plan's cap, straight from the ClickHouse event ledger.
AI features are gated by plan — the AI flow builder and auto-translate are included from Growth, and Autopilot from Scale. AI credits are the monthly usage allowance for those features on plans that include them: 25 on Free, 200 on Growth, 2,000 on Scale, and 25,000 on Enterprise (on Free, credits apply to the AI surfaces Free does include, like dashboard generation). If you run out mid-month, credit packs can be bought from Settings → AI credits.
#The spend cap
A spend cap is an optional hard ceiling on your monthly spend, in dollars. Set it in Settings → Billing. Pushlane converts your cap into an equivalent MAU ceiling for your plan, then enforces it before every send:
- While you are under the cap, everything sends normally.
- Once your reachable MAU reaches the cap's MAU-equivalent, sends to users you have not yet pushed this month are suppressed — reaching a not-yet-counted user would take you past your plan's reachable-MAU cap. Those users simply wait until next month.
- Users you have already pushed this month — from any of your flows — are exempt: they are already counted in this month's billable MAU, so a further send to them costs nothing extra and keeps flowing.
The exemption is measured per user, across all your flows, by whether we have already delivered a push to that user this month (not by which flow). This is a deliberately conservative stand-in for “already billable”: it never lets a genuinely new user through the cap, and at most it may briefly hold a user who became billable through activity we have not yet pushed on.
Every suppression is logged in decision_log with reason spend_cap (visible in Logs), and the Billing screen shows how many sends the cap held back this month. Nothing is ever silently dropped, and a send is never faked as delivered.