Six services. Each one solves a different sending problem.
SMTP Relay if your application already speaks SMTP. Email API if your engineers want delivery logic in product code with proper webhooks and idempotency. PowerMTA when sustained throughput pushes the simpler MTAs past their limits. Dedicated Email Servers for teams that bring their own MTA onto bare metal. Cold Email Infrastructure for outbound work — the kind that read Spamhaus's June 2025 position and decided to keep doing this work properly. Managed Deliverability for the human-expertise layer wrapped around any of the above. Every entry plan ships with dedicated IPs in the box. The pricing is on the page — no $30/IP/month surprise after signup.
One platform with six knobs is not the same as six products that actually do the work
Email infrastructure isn't a single problem. Sending password resets out of a SaaS application doesn't look anything like sending a marketing campaign to a million addresses; running PowerMTA with stream isolation doesn't look anything like running Postfix on a single bare-metal box; cold outreach in 2026 — after Spamhaus's June 2025 position, after Gmail rolled out RETVec, after the 2024 Yahoo enforcement — is a different operation entirely from warmed transactional sending. Most platforms try to fold all of that into one product with feature flags. The result is the chronic mismatch where teams end up paying for things they don't need and going without things they do. Our catalogue is six separate products because that's what the problem space actually looks like. Combine them when the sending is complex enough to justify it.
What follows is the catalogue, with starting prices in plain view. Every entry plan ships dedicated IPs in the box. EU operation, default. The decision-aid table further down maps situations to recommended services, and the pricing comparison shows the full plan range across all six lines side-by-side.
The six product lines, with starting price
SMTP Relay Service
The application already speaks SMTP and you don't want to rewrite it. We slot in behind it as a managed relay with ten dedicated IPs from day one. Works for the boring real-world cases nobody redesigns — billing systems, ERP platforms, helpdesk tools, off-the-shelf SaaS, custom backends with three years of accreted SMTP code.
Email API
Same dedicated-IP foundation as the relay, but accessed as a REST API your engineers actually want to use. Idempotency keys for retry safety. Typed webhooks signed with HMAC-SHA256 (no more guessing whether the payload is real). SDKs for Python, Node.js, PHP, Ruby, Go, Java, C#. The shape SaaS products and event-driven workflows want when delivery logic belongs in product code.
Managed PowerMTA Servers
Commercial PowerMTA, single-tenant, with the license, the dedicated hardware, the configuration and the monitoring all rolled into one bill. Virtual MTAs for stream isolation, dedicated IP pools, per-domain throttling that actually does what the docs say. No separate Bird quote to chase, no per-server licensing math to sort out at renewal.
Dedicated Email Servers
Bare metal. Real Intel Xeon CPUs (no vCPU, no hypervisor noisy-neighbour problems). Ten to thirty dedicated IPs depending on tier. You bring the MTA — Postfix if you've been running it forever, Exim if you came up through cPanel, KumoMTA if you want the new Lua-scripted thing the ex-PowerMTA people shipped in 2024, or your own PowerMTA license if you'd rather manage that yourself.
Cold Email Infrastructure
For outbound work that read Spamhaus's June 2025 cold-email position and decided to keep doing this work, properly. Continuous active warming. Daily monitoring against Gmail's RETVec classifier and Spamhaus's blocklists. Dedicated IPs, isolated cousin domains, the whole operational kit needed to run cold email in 2026 without ending up on the wrong list. Doesn't promise inbox magic. Won't pretend the rules are what they were in 2018.
Managed Deliverability
The human-expertise layer. Someone reading Postmaster Tools and SNDS and actually doing something with the data. Blocklist remediation when listings happen. SPF, DKIM, DMARC and BIMI configured properly the first time. Monthly DMARC RUA processing turned into action items instead of XML nobody opens. Sits on top of any sending infrastructure — ours, SendGrid, Mailgun, Amazon SES, in-house Postfix, anything.
Picking the right starting service
| If your situation is... | Start here | Starting price | Then consider |
|---|---|---|---|
| Application already sends over SMTP and reliability needs to improve | SMTP Relay Service | €399/mo | Managed Deliverability |
| Building transactional sending into a SaaS product with developer-led integration | Email API | €469/mo | Managed Deliverability |
| Migrating from SendGrid (free tier eliminated May 2025) or Mailgun (rate doubled Dec 2025) | Email API or SMTP Relay | €399–€469/mo | Managed Deliverability |
| Sustained sending passes 100k+ messages per hour with stream isolation requirements | PowerMTA Servers | €899/mo | Managed Deliverability |
| Self-hosting PowerMTA but operational burden has become uncomfortable | PowerMTA Servers | €899/mo | Dedicated Servers (if you keep license) |
| Your team runs Postfix or Exim and just needs proper bare-metal hardware with clean dedicated IPs | Dedicated Email Servers | €995/mo | Managed Deliverability |
| Generic dedicated server provider (Hetzner, OVH) AUP causing friction at scale | Dedicated Email Servers | €995/mo | Managed Deliverability |
| Cold outreach program that needs to survive Spamhaus, RETVec and Gmail/Yahoo guidelines | Cold Email Infrastructure | €1,799/mo | Managed Deliverability |
| Lead-generation agency offering outbound work to client accounts | Cold Email Infrastructure | €1,799–€3,799/mo | Strategic Deliverability |
| Recovering from a Spamhaus listing or Microsoft block right now | Deliverability Audit | €1,500 one-time | Then Ongoing retainer |
| Pre-launch validation before sending program goes live | Deliverability Audit | €1,500 one-time | The right sending product based on findings |
| Multi-brand portfolio with executive visibility on deliverability | Strategic Deliverability | €3,500/mo | Sending products per brand as warranted |
Pricing for all six lines, on one page
Same shape across the catalogue. A published Starter (or audit equivalent) with dedicated IPs in the box. A mid tier when sending grows. A Scale or Enterprise tier when it grows further. A Custom plan when the operation has stopped fitting any of those. Annual prepayment knocks 10% off retainer engagements.
| Service | Starter / Audit | Mid tier | Top tier | Custom |
|---|---|---|---|---|
| SMTP Relay | €399/mo (10k/day, 10 IPs) | €749/mo (25k/day, 15 IPs) | €1,499/mo (50k/day, 20 IPs) | Quote |
| Email API | €469/mo (10k/day, 10 IPs) | €859/mo (25k/day, 15 IPs) | €1,729/mo (50k/day, 20 IPs) | Quote |
| PowerMTA Servers | €899/mo (50k/hr, 4 IPs, 5 vMTAs) | €1,499/mo (150k/hr, 8 IPs, 15 vMTAs) | €2,799/mo (500k/hr, 16 IPs, 50 vMTAs) | Quote |
| Dedicated Servers | €995/mo (Xeon E-2388G, 32GB, 10 IPs) | €1,699/mo (Xeon Gold 6326, 64GB, 20 IPs) | €2,100/mo (Xeon Gold 6338, 128GB, 30 IPs) | Quote |
| Cold Email Infrastructure | €1,799/mo (5k/day, 10 IPs) | €2,499/mo (10k/day, 20 IPs) | €3,799/mo (20k/day, 30 IPs) | Quote |
| Managed Deliverability | €1,500 one-time audit | €1,200/mo Ongoing retainer | €3,500/mo Strategic + dedicated consultant | Quote |
When one service isn't quite the answer
Most mature setups end up combining more than one. Here are the combinations we see often, with rough cost ranges so you can compare the architecture against what the in-house equivalent would cost.
SMTP Relay + Managed Deliverability
SaaS teams sending operational mail over SMTP, with an operator looking after the receiver-side reputation work alongside. Combined cost from €399 + €1,200 = €1,599/month, which is the most common entry combination by some distance.
Email API + Managed Deliverability
Product-led teams whose engineers can build the integration cleanly enough but don't have a deliverability specialist on staff. The retainer fills that gap. Combined cost from €469 + €1,200 = €1,669/month.
Dedicated Servers + Managed Deliverability
The "we'd rather run our own MTA, but we still want someone reading Postmaster Tools" combination. €995 + €1,200 = €2,195/month for a fully managed sending stack at one-server scale.
SMTP Relay + Email API together
Common in organisations that have both off-the-shelf tools (which want SMTP) and their own product code (which prefers an API). One billing account covers both. Shared IP pool is available as a Custom-plan option when reputation consolidation makes sense.
PowerMTA + Cold Email on separate cousin domains
The pattern ESPs running both client transactional traffic and outbound prospecting end up with — PowerMTA on the primary domain, Cold Email Infrastructure on isolated cousin domains so reputation doesn't bleed across. €899 + €1,799 = €2,698/month combined.
Strategic Deliverability across a multi-brand portfolio
Large organisations with multiple brands where deliverability has executive visibility. The €3,500/month Strategic engagement covers coordinated DMARC strategy across the portfolio, BIMI rollout brand by brand, comparative reputation tracking, and quarterly architecture reviews when something material has shifted in the receiver landscape.
Common questions about the catalogue
The questions we get most often before someone signs
How do I choose between SMTP Relay and Email API?
Look at the application doing the sending. If it already speaks SMTP and the integration works, SMTP Relay (€399/mo Starter) drops in behind it without requiring a rewrite — you keep your existing code and gain the dedicated-IP foundation. If the sending logic should live inside product code instead — webhooks, idempotent retries, structured request/response — then Email API (€469/mo Starter) is the right shape. They're not better-or-worse; they're answers to different questions about where the delivery code wants to live.
When does PowerMTA become worth the price difference?
The boundary is roughly 100,000 messages per hour sustained. Below that, SMTP Relay or Email API will do the job for less money and less operational complexity. PowerMTA Servers (€899/mo Standard) start to pay off in three situations: when you're past that throughput line and the simpler MTAs are choking on it; when you need explicit stream isolation through virtual MTAs because transactional and marketing reputations shouldn't share an IP pool (or per-customer reputation isolation in a multi-tenant platform); when per-domain throttling needs tuning beyond what relay defaults give you. If none of those apply yet, you're not at the PowerMTA tier yet.
What's the difference between PowerMTA Servers and Dedicated Email Servers?
The MTA, mostly, and who runs it. PowerMTA Servers (€899/mo) is the managed product — we install PowerMTA, tune it, monitor it, operate it. The commercial license is rolled into the bill. Dedicated Email Servers (€995/mo) is the bare-metal product where you bring your own MTA: Postfix, Exim, KumoMTA, or your own PowerMTA license if you'd rather manage that yourself. The first is for teams that want PowerMTA specifically and don't want to operate it; the second is for teams that have their own email expertise and want hardware with dedicated IPs without paying us to run a commercial MTA on top.
Why does Cold Email Infrastructure cost more than dedicated servers?
Because the operational density per delivered message is roughly an order of magnitude higher. Dedicated Email Servers run on reputation that you brought with you — already-warm IPs, sender history that filters trust. Cold Email Infrastructure (€1,799/mo Starter) is the opposite shape: fresh IPs, fresh cousin domains, no reputation yet, and the rules updated in 2025. That means continuous active warming, daily monitoring against Gmail's RETVec classifier and Spamhaus's blocklists, warming traffic between campaigns to keep reputation alive in low-volume periods, and triage when listings happen. The price isn't a margin difference. It's the difference in actual work.
Can I combine multiple services?
Yes — most mature setups do. The patterns we see most often: SMTP Relay for off-the-shelf operational tools alongside Email API for the product's own outbound code; Dedicated Email Servers running KumoMTA wrapped with Managed Deliverability for the receiver-side work; PowerMTA Servers and Cold Email Infrastructure on separate cousin domains so reputation doesn't bleed across; or Managed Deliverability layered on top of any of these for the human-expertise piece. The catalogue is separated because the work is different, but the products are designed to compose cleanly.
What does Managed Deliverability cover and when do I need it?
Managed Deliverability (€1,500 one-time audit / €1,200 monthly Ongoing / €3,500 monthly Strategic) is the human-expertise layer wrapped around any sending stack. We read Postmaster Tools, do something useful with what's there, remediate blocklist listings when they happen, configure SPF/DKIM/DMARC and BIMI properly, turn the monthly DMARC RUA reports into actual action items. It works on top of our infrastructure or someone else's — SendGrid, Mailgun, SES, an in-house Postfix, anything. The audit is the right entry when there's a specific problem to diagnose. The retainer is right when deliverability needs continuous attention and you don't have someone in-house with the time or the pattern recognition to do it.
Are dedicated IPs included in the entry-level plans?
Yes — and this is one of the most visible differences against the SaaS email-API providers. The SMTP Relay Starter at €399/month ships with ten dedicated IPs. The Email API Starter at €469/month ships with ten dedicated IPs. The Cold Email Starter at €1,799/month ships with ten dedicated IPs. Compare to the alternatives: Postmark charges $50 per IP per month and won't sell them at all unless you're committing to 300K monthly minimum sends; SendGrid gives dedicated IPs free but only above 100K/month on the right plan; Mailgun bundles them only at the Scale tier. Dedicated IPs as the baseline rather than as a paid add-on isn't an accident of pricing — it's the position.
Where are the servers located?
Sweden and Germany by default — both EU jurisdictions, both with the regulatory stability and peering arrangements that make this work practical. EU operation simplifies the GDPR posture for European data subjects, which matters whether the sending is transactional or outbound. US and Asia-Pacific data centres are available on Custom plans when latency or specific regulatory reasons make them worth the trade-off. The team itself is in Stockholm and has been operating production email infrastructure since 2003.
Do you offer custom plans?
Yes. Every product line has a Custom tier for the cases that don't fit a published plan: higher volume than the top tier, larger IP allocations, multi-server clusters, specialised configurations, agency engagements covering multiple teams, white-label arrangements. Custom plans are quoted from the actual scope rather than from a list. Most engagements start on a published plan and migrate to Custom only once volume or complexity has earned it — there's no benefit to overshooting the configuration on day one.
How do I get started?
Match your current sending model to one of the six product lines using the decision-aid table above; the answer is usually obvious once the operational question is clear. If a Custom configuration or a multi-service combination is the right fit, write to us with a description of what you're sending, what infrastructure you're on now, and what you'd like to change. Most quotes turn around in one to two business days. Published plans are billable directly through the Client Area; Custom plans involve a brief scoping call first so we both go in with the same understanding.