Simple by design
Start with the essentials, then add scale and operational depth when your product needs it. Billing is coming later; these plans are illustrative.
Preview pricing — billing is not enabled yet.
Launch
For a product shipping its first reliable notification flow.
Scale
For growing teams that need visibility and room to move.
Control
For critical workloads with high volume and deeper support.
| Launch | Scale | Control | |
|---|---|---|---|
| Applications | 1 | 5 | Unlimited |
| Monthly notifications | 25,000 | 500,000 | 5 million |
| Event history | 7 days | 30 days | 90 days |
| Team members | 3 | 10 | Unlimited |
| Provider credentials | ✓ | ✓ | ✓ |
| Delivery analytics | — | ✓ | ✓ |
| Priority support | — | — | ✓ |
“Push infrastructure should disappear when it works—and explain itself when it doesn’t.”
FAQ
Yes. The current plans are placeholders while we validate usage and operational needs with early teams.
One provider delivery attempt to one installation counts as one notification. Retries caused by Pushctl do not count twice.
Absolutely. Plans are designed around usage, so you will be able to move up or down as your product changes.
Yes. Teams above the Control allowance will be able to arrange custom volume, retention, and support.