Billing & Subscription Quotas
Manage subscriptions easily. Access secure billing portals powered by Stripe and enjoy automatic plan quota updates.
Billing is enforced at the API layer rather than in the interface, which is a design decision worth explaining: it determines what happens when you reach a limit, and whether reaching one can ever cost you money you did not expect.
Limits prompt rather than charge
Plan entitlements - sending domains, mailboxes per domain, concurrent campaigns - are checked server-side on every request that would consume them. Attempting to exceed one returns a prompt to upgrade rather than silently permitting the action and billing for overage. The distinction matters: usage-based billing surprises are among the most common complaints about infrastructure products, and enforcing at the API means the surprise is structurally impossible here.
Why pricing is not per message
Per-message pricing is the norm for platforms sending from their own infrastructure, where each message carries a marginal cost to the vendor. Here, messages leave through mailboxes you already pay your email provider to operate. Charging again per message would be billing you for infrastructure you have already bought. Capacity - domains and mailboxes - is what the platform actually provides, so that is what is priced.
Currency and self-service changes
Checkout runs through Stripe in either USD or PKR, chosen at the point of subscribing. Upgrades, downgrades and cancellation are all self-service through the billing portal and take effect from the next cycle. Cancelling stops future charges while access continues for the period already paid, so moving down a tier after a heavy month carries no penalty beyond the timing.
What happens to your data at the end
On account closure, lists, campaigns and analytics are removed. Suppression hashes are retained deliberately - discarding them would mean a later account could re-contact people who had already opted out, which is the one thing suppression exists to prevent.
Why enforcement lives in the API rather than the interface
A limit enforced only by hiding a button in the interface is not a limit. Anything that talks to the API directly, or any interface state that gets out of sync, will bypass it. Entitlement checks therefore run server-side on the request itself, which means the same rules apply however the action is initiated. This is unglamorous and it is the reason plan limits behave predictably rather than approximately.
What counts against your plan
Three quantities are metered: authenticated sending domains, mailboxes per domain, and concurrently active campaigns. Messages sent are deliberately not metered. A campaign that has finished releases its slot, so the campaign limit constrains how much runs at once rather than how much you may run in total over a month.
Feature Breakdown
Stripe Subscription Billing Integration
Secure checkout experiences and subscription management portals powered by Stripe.
Technical Capabilities:
Spec Sheet
Need a Deep Dive?
See exactly how this module manages background queues, encryption, and delivery logic in our sequence flowchart.
View technical guideReady to Connect Your Nodes?
Scale your deliverability with our intelligent sharding relay. Add your domains and start landing in the inbox.
Billing & Subscription Quotas questions.
The specifics people ask about before relying on this part of the platform.
How does billing work?
Subscriptions are handled through Stripe and billed monthly in advance. You can upgrade, downgrade or cancel yourself from the billing portal in your dashboard.
Can I pay in Pakistani Rupees?
Yes. Checkout supports both USD and PKR, and you choose your currency when subscribing.
What happens if I try to exceed my plan limits?
Limits on domains, sending accounts and active campaigns are enforced in the API, so you are prompted to upgrade rather than being charged automatically for overage.
What happens to my data if I cancel?
You keep access until the end of the period you have paid for. After closure, lists, campaigns and analytics are removed; suppression hashes are retained so that people who opted out are never contacted again by a later account.