The email API costs that don't show up on the pricing page

The advertised per-tier price is rarely the whole story for any usage-based API. The costs that actually surprise teams are the ones that only show up once you're past the included volume or need a feature that's gated behind an add-on. Using Envello's own published numbers as a concrete example of what to check, whichever provider you're evaluating:

Overage rates

Envello's Pro tier includes 50,000 to 100,000 emails per month depending on the plan variant, with overages billed at €0.80 per 1,000 emails beyond that. That rate is published on the pricing page, not something you discover on your first invoice after a traffic spike. Check whether a provider you're evaluating publishes its overage rate at all; many don't show it until you're already a customer.

Add-ons that aren't in the base tier price

Dedicated IPs are a real add-on on Envello's Scale tier (€25/month), not bundled into the base price. That's a reasonable and disclosed cost, the kind worth checking for on any provider: does the tier price include everything you'll actually need, or does reaching feature parity require stacking add-ons that change the effective price?

Questions worth asking before you commit

• What's the exact overage rate, and is it published or only visible after signup?
• Which features require an add-on rather than being included in the base tier?
• Does the retention window scale with the tier, or is long retention itself an upsell?
• What happens on a missed payment, immediate suspension or a grace period?

The volume tiers that don't map cleanly to usage

Most providers price in bands: a tier covers up to N emails, and the next tier up covers the next band at a higher base price. The trap is a team that regularly sends 55,000 emails a month landing on a 50,000-email tier and paying overage every single month instead of the next tier up, which might be cheaper overall once the overage rate is factored in. Run the actual math on your typical month, not your lowest month, before picking a tier: overage rates are usually priced as a convenience premium, not a bulk discount.

The opposite trap is picking a tier two sizes too large "to be safe" and paying for headroom that never gets used. A published, granular pricing calculator that lets you plug in your actual monthly volume and see the real total, tier price plus expected overage, is worth more than a static pricing table for this exact reason.

Support tier gating

Response-time SLAs and priority support queues are commonly gated by tier, which is a reasonable business model, but it's worth knowing upfront rather than discovering it during an incident. If your production sending depends on a fast answer to a deliverability question, check whether your intended tier includes priority support or whether that's itself a higher-tier feature. A cheap base tier with a 5-business-day support response isn't necessarily cheaper once you count an outage's cost against the support tier you'd actually need to resolve it quickly.

Migration and export costs

A cost that rarely appears on any pricing page: what it costs, in time and in dollars, to leave. Some providers charge for data export, gate historical log access behind a support ticket once you've cancelled, or simply don't offer a documented export path at all. Before committing to a provider, check whether you can export your own send history and suppression list on your own schedule, not just while you're an active paying customer. That's not a line item on the pricing page, but it's a real cost if the answer turns out to be no.