Know before you pay

Email API pricing models — what you are actually paying for

Event-based, email-based, per-contact, per-seat — email API pricing varies widely. This page explains how else.events works and how it compares to the alternatives.

Why email API pricing is confusing

Per-event pricing can be expensive at scale

If every event costs money — even ones that result in no email being sent — costs can scale faster than your email volume.

Per-contact pricing penalises large user bases

Tools that charge per stored contact push you to delete contacts aggressively or pay for users who have not received an email in months.

Overage tiers are rarely transparent upfront

Many providers show the base price prominently and bury the overage rate deep in their pricing page. The real cost at scale is harder to calculate.

Bundled marketing + transactional pricing inflates costs

Paying for a marketing automation suite when you only need transactional email sends is a common cost trap.

else.events: priced per email sent, not per event fired

Pay for emails, not events

You fire events to else.events. Only emails that are actually matched, rendered and sent count toward your quota.

No contact storage fees

Recipient data comes from your event payload. else.events does not store contacts or charge per stored address.

Transparent overage

If you exceed your plan's included volume, overage is charged at a flat per-1 000-emails rate. Shown clearly on the pricing page.

No marketing bloat

else.events is a transactional email workflow layer. You are not paying for campaign tools, segmentation engines or CRM features you do not use.

Email API pricing model comparison

ModelHow it scalesGood forWatch out for
Per email sent (else.events)Scales with actual send volumeSaaS teams with variable event loadsOverage on high-volume spikes (billing cycles, trials)
Per event firedScales with event volumeLow-event, high-send setupsEvents that match no rule still cost money
Per contactScales with contact list sizeList-based marketingPenalises large user bases with low send frequency
Per seatFixed regardless of volumeSmall teams with high volumeWrong unit for transactional email — volume decoupled from team size

else.events uses the per-email-sent model. Only emails that are matched and delivered count.

Frequently asked questions

Does else.events charge if my event fires but no email is sent?
No. Only emails that are matched by a rule, rendered and sent to a provider count toward your quota. Unmatched events are not billed.
What is an overage and how is it priced?
If you send more emails than your plan includes in a billing period, the excess is charged at a flat rate per 1 000 emails. The exact rate is shown on the pricing page.
Are there any contact or storage fees?
No. Recipient data is provided in the event payload. else.events does not store contact lists or charge per stored address.
Is there a free tier?
else.events is free during the public beta. Pricing will be introduced with advance notice before billing begins.

Simple, email-volume-based pricing for your SaaS

No per-contact fees, no per-seat surprises. Pay for the emails you actually send.

  • Free during public beta
  • Priced per email sent
  • No contact storage fees