Skip to main content
Mailrify billing is usage-based and category-aware. Billing is tracked in two categories: TRANSACTIONAL and CAMPAIGN, and billing checks happen before the email is queued.

​
Core concepts

​
Categories

Usage is split into two categories:
  • TRANSACTIONAL: API sends and workflow sends (workflow is stored as source WORKFLOW but billed as transactional)
  • CAMPAIGN: Marketing campaign sends

​
Included quota and overage

Each category has:
  • Included quota: sends included in your base subscription. Billed as part of the subscription.
  • Pay-as-you-go overage: sends above your included quota are billed as pay-as-you-go.
  • Maximum overage: each category has a maximum overage allowance above the included quota.
  • Custom pay-as-you-go limit: you can set a lower project limit per category to cap pay-as-you-go usage.
When usage reaches either the maximum overage or your custom pay-as-you-go limit, new sends in that category are blocked.

​
Billing status

Paid projects can be marked as:
  • ACTIVE: billing is in good standing
  • DELINQUENT: payment issue detected, sending is blocked until recovery

​
Free plan behavior

Free projects use shared limits across both categories:
  • 1,000 emails per month
  • 100 emails per day
Free projects include a Mailrify badge in the email footer. Paid subscriptions use per-category quotas:
  • Sends within your included monthly volume are covered by your plan.
  • Sends above your included volume are billed as pay-as-you-go overage.
  • Sending stops when you reach your allowed sending limit for that category.
You can set per-category project limits to cap sending below the plan maximum.

​
Tiered feature limits

Your selected Plan tier also controls non-email limits such as:
  • max contacts
  • max custom domains
  • max team members
Downgrades are validated against current project usage. If your project exceeds the target tier limits, the downgrade is blocked until usage is reduced.

​
How usage is counted

  • Usage is reserved atomically before send to prevent limit overshoot under concurrency.
  • Campaign sends are preflight-checked against projected recipient count before scheduling/sending.

​
Attachments

Emails containing attachments count as 2 sending units. This applies to all usage, including:
  • included plan volume
  • pay-as-you-go overage

​
Plan changes and subscription lifecycle

  • Checkout creates a subscription and links it to a project.
  • Upgrades apply immediately with proration/invoice handling.
  • Downgrades are scheduled for the next billing cycle.
  • Scheduled downgrades can be canceled before they take effect.
  • Subscription cancellation resets project billing state to free defaults.

​
Notifications and blocking

Mailrify sends billing notifications when usage approaches or exceeds limits, and blocks sends when limits are reached. Delinquent projects are also blocked until payment status returns to active.
For related sending behavior, see Transactional Emails, Campaigns, and Templates.