Skip to content
BUNDLE · BUSINESS LAUNCH

Launch your own Email Service Provider.
Bare-metal, multi-tenant, customer-ready in 2 weeks.

For operators launching a customer-facing email sending business: agencies productising deliverability, white-label ESPs, niche industry-vertical platforms, regional players building alternatives to the global SaaS incumbents. The ESP Starter Kit delivers a dedicated bare-metal server with PowerMTA, configured MailWizz multi-tenant front-end, five warmed dedicated IPs, full authentication and monitoring stack, ready before your first customer onboards.

€1,499 one-time setup plus €499/month ongoing infrastructure covers: server, PowerMTA license, MailWizz EMS license, IP warmup, DNS authentication, monitoring, and two hours of expert onboarding to walk your operations team through the configuration. Customer onboarding, customer support, commercial decisions, and pricing are yours; we handle the infrastructure foundation that takes months to assemble correctly DIY.

setup fee €1,499 one-time
monthly €499 / month
launch time ~14 days
customer capacity 20-40 typical
why own ESP vs reselling SaaS

The economics of running your own.

Reselling SaaS (white-label SendGrid, Mailgun, Postmark) produces approximately 30-40% gross margin after wholesale costs. The customer pays you €0.50 per thousand emails; you pay SendGrid €0.30 per thousand wholesale; €0.20 margin. Operations are minimal (no infrastructure to manage), the deliverability is whatever the upstream provider delivers, differentiation is brand and customer service. The model works at high volume; at low volume the margins don't cover customer acquisition.

Operating your own ESP changes the economics. Hardware, licences, and infrastructure cost ~€500-700/month at the starter kit scale, supporting 20-40 active customers with combined volumes of 1-5 million emails monthly. Customer revenue at €30-150/month per account translates to €600-6,000/month at 20 customers; gross margin sits at 70-85% at this scale. Operations are real (you manage deliverability, you handle abuse, you respond to deliverability issues), so the higher margin reflects higher operational responsibility.

The right choice depends on whether deliverability differentiation is part of your value proposition. If you're competing with SendGrid on price and ease-of-use, reselling their stack and adding billing UI works. If you're competing on deliverability quality (vertical-specific reputation, IP rotation flexibility, customer-customisable warmup, regional jurisdiction), you need infrastructure control that resale can't provide. The Starter Kit is built for the second case.

Starting from scratch (DIY assembling: dedicated server, PowerMTA license, MailWizz license, IPs, warmup, monitoring, configuration) costs approximately €4,500-6,500 setup plus €600-800/month before you have anything customer-facing. About 60-90 days of engineer time to assemble correctly. The starter kit compresses both: €1,499 + €499/mo, ready in two weeks plus the standard 30-day warmup. Most operators value the time-to-launch over the cost differential.

capacity planning

Customer capacity and breakeven calculator.

Adjust customer count and volume per customer. The calculator shows fleet utilisation across your 5 IPs, monthly revenue at typical pricing, and breakeven point where revenue covers infrastructure cost. Numbers reflect typical SaaS-ESP economics at this hardware scale.

20 active customers

Comfortable range: 20-40 customers. Architecture scales to ~80 before second server needed. Most ESPs reach 20 customers within 12 months at moderate marketing investment.

30K per customer/month

SaaS ESP customers typically send 10-100K monthly. Vertical-specific ESPs (e-commerce, agency-resold) average higher; transactional ESPs lower. 30K is sensible default.

€79 per customer/month

Typical SaaS ESP pricing: €30 starter tier, €79 standard, €199 pro, €499 enterprise. Average customer at €79/month reflects typical mix.

fleet metrics

Volume and utilisation

Total monthly volume 600K
Daily volume average 20K
Per-IP daily average 4K
Hardware utilisation ~3%
Headroom before second server ~30× current
revenue economics

Revenue and margin

Monthly revenue €1,580
Monthly infrastructure cost €499
Monthly gross margin €1,081
Margin % 68%
Annualised gross profit €12,972
honest considerations

Beyond the math

  • Customer acquisition cost. Calculator shows operating margin only. CAC at €100-500 per customer depending on channel; payback at €79/month is 1.3-6.3 months. Plan budget for marketing.
  • Operational time. Each customer adds support, abuse, deliverability questions. Budget 1-3 hours/customer/month for operations beyond automated workflow.
  • Churn reality. SaaS ESPs see 3-7% monthly churn typical. Net new customer growth needs to exceed churn for fleet to grow.
  • Bad-customer risk. One customer sending unsolicited bulk damages reputation across shared IPs. Vetting and AUP enforcement are operational burdens.

Calculator simplifies. Real ESP economics depend on customer mix (transactional vs marketing), churn dynamics, operational efficiency, and reputation incidents. Most starter-kit ESPs break even on infrastructure alone at 7-10 customers, profit comfortably past 20 customers, and decide between adding server vs raising prices around 50 customers. Office hours included for go-to-market and pricing strategy questions.

DIY assembly cost

What this would cost separately.

Click each component. The DIY path runs ~€4,500-6,500 setup plus ~€600-800/month before customer-facing readiness, and requires 60-90 days of engineer time to assemble correctly. Bundle is €1,499 + €499/mo, ready in 2-week setup + 30-day warmup.

component detail

Bare-metal server Iron-E5

AMD EPYC 7402P (24 cores / 48 threads, 2.8 GHz base / 3.35 GHz turbo), 128 GB DDR4 ECC, 2× 960 GB NVMe in software RAID-1, 50 TB bandwidth on 1 Gbps. Sized to handle 2-5 million daily sends comfortably across 5 warmed IPs with monitoring overhead and headroom for scaling.

DIY equivalent: similar bare-metal from established providers (OVH Iron range, Hetzner AX series, Latitude.sh) runs €250-400/month. Setup fees often €0; provisioning takes 24-72 hours.

DIY assembly total ~€6,000 setup + ~€700/month
Bundle price €1,499 setup + €499/month
Savings ~€4,500 setup + ~€200/month
Time saved (DIY engineer time) 60-90 days launch acceleration
vs alternatives

Starter Kit vs SaaS resale vs DIY MailWizz.

Three honest paths to launching a customer-facing email business. Each has different cost structure, control level, margin profile, and operational responsibility. The right choice depends on whether infrastructure control is part of your value proposition.

  us
ESP Starter Kit
SaaS resale
(SendGrid white-label)
DIY MailWizz hosting
(self-managed)
SendGrid as ESP
(direct customer use)
Setup cost €1,499 one-time €0 (or partner fee) €4,500-6,500 DIY assembly €0 (signup only)
Monthly infrastructure €499/mo (fixed) Wholesale per-email cost ~€600-800/mo (DIY equivalent) Per-volume tier
Per-email cost at 1M/month ~€0.0005 (€499 / 1M) ~€0.30/k wholesale (€300/M) ~€0.0007 (€700 / 1M) ~€1.50/k retail (€1,500/M)
Time to launch ~6 weeks (incl. 30-day warmup) ~1-2 weeks (signup + branding) ~12 weeks DIY assembly 1 day (signup)
IP control Full (5 dedicated IPs) None (shared upstream) Full (you provision) Limited (assigned by SendGrid)
Customer panel branding Full white-label MailWizz Partner-program branding Full white-label MailWizz SendGrid-branded
Per-customer IP rotation Yes (you decide policy) No (upstream policy) Yes (you implement) Limited (SendGrid policy)
Compliance / jurisdiction control Full (your jurisdiction choice) Upstream-determined Full (your choice) US-jurisdictional
Typical gross margin 70-85% at 20+ customers 30-40% 70-85% at scale 0% (you're the customer)
Customer capacity 20-80 customers (single server) Unlimited (upstream-bounded) 20-80 customers (single server) Yourself only
Path to scale Add server (€499/mo each) Higher partner tier Add server Higher SendGrid tier
Deliverability responsibility You (with our office hours) Upstream (out of your control) You (no support) SendGrid
Abuse handling You (with our backup) Upstream policies apply You alone SendGrid
Customer support You You + upstream escalation You alone SendGrid (limited)
Best for Infrastructure-differentiated ESPs Brand + UX differentiation Operators with engineering depth End users, not ESPs

SendGrid resale and ESP Starter Kit are not the same business model. Resale optimises for low operational burden at lower margin; Starter Kit optimises for higher margin and infrastructure control at higher operational burden. The DIY path matches Starter Kit economics but trades €4,500 cash for 12 weeks of engineer time. Most operators value the time compression unless engineering depth is already deep.

honest fit assessment

Who launches with this kit, who shouldn't.

good fit
  • Agencies productising deliverability. You've been running deliverability work as service offering; productising into self-service ESP unlocks scale beyond hourly billing. Kit gives infrastructure foundation; you bring methodology and customer relationships.
  • Vertical-specific ESPs. Industry-niche email platforms (real estate, legal, healthcare-compliant, e-commerce) where vertical knowledge differentiates against horizontal SendGrid. Infrastructure control matters for compliance; you bring vertical expertise.
  • Regional ESPs. Building alternatives to US-jurisdictional incumbents (LATAM, EU sovereign, Asia regional). Jurisdiction selection, regional language support, regional payment methods all benefit from infrastructure control.
  • White-label resellers wanting margin upgrade. You've been reselling at 30-40% margin; ready to take operational responsibility for 70-85% margin. Customer base is established; switch from upstream to your own infrastructure.
  • Operations with at least one anchor customer ready to onboard. Don't launch with empty platform; one anchor (existing customer transitioning, founder's company, partner agency) validates economics from day one.
  • Operators with technical staff capable of PowerMTA + MailWizz day-to-day. Bundle accelerates launch but doesn't replace ops. Need at least one staff member comfortable with Linux, MTA configuration, customer support escalation.
poor fit
  • Solo operator with no anchor customers. Launching ESP without committed customers means months of CAC-funded sales before first revenue. Start with Cold Bundle (€499 + €349/mo) for personal outreach; revisit ESP launch once customer base validates.
  • You don't plan to have technical operations staff. Bundle requires PowerMTA + MailWizz operational competence. If you can't allocate even part-time technical operator, managed SMTP relay (€199-499/mo, we handle ops) fits better than launching your own ESP.
  • You expect us to handle your customer support. We support you (the operator); we don't support your end customers. Customer support is an operational responsibility you're taking on by launching ESP. If that's a deal-breaker, rethink the model.
  • You want to resell our infrastructure under our brand. Different commercial structure (white-label reseller program, separate negotiation), not the Starter Kit. Contact for that path; not what this product covers.
  • Your projected volumes are below 50K monthly. ESP economics require some scale; below 50K monthly, infrastructure cost dominates revenue. Better to use SaaS ESP yourself until scale justifies the launch.
  • You expect to compete on lowest price. Starter Kit isn't cheapest path. SendGrid resale undercuts you on price; you need differentiation other than price (deliverability, vertical, region, support). If only price matters in your market, resale model fits better.
scope of bundle

What's in the €1,499 + €499.

01

Dedicated server Iron-E5

Bare-metal AMD EPYC 7402P (24 cores / 48 threads, 2.8 GHz base / 3.35 GHz turbo), 128 GB DDR4 ECC RAM, 2× 960 GB NVMe SSD in software RAID-1 mirror, 50 TB bandwidth on 1 Gbps. Hosted in your jurisdiction of choice (BG, RO, MD, PA, HK, SG, UA).

Sized for 2-5 million daily sends across 5 IPs with monitoring overhead and headroom for fleet growth. Not CPU-bound at this scale; the bottleneck becomes IP reputation before hardware. Configuration scales to second server when active customers exceed ~80.

02

PowerMTA license + production setup

Genuine PowerMTA license (perpetual, locked to the server) plus our reference configuration: per-domain pickup directories, virtual MTA pools mapped to the 5 IPs, queue-management policies tuned for bulk + transactional split, recipient-domain throttling tables for the major receivers, FBL processing, bounce categorisation.

Configuration is reproducible. We provide the full config files; not a black box. You can audit, modify, take with you. Same configuration we use on our infrastructure for other clients. Supports 5-IP rotation patterns, per-tenant isolation, customer-level rate limiting.

03

MailWizz EMS + customer-facing panel

MailWizz Email Marketing Studio (commercial license included), configured for multi-tenant customer use. Customer accounts can manage their own lists, campaigns, sending domains, reports, transactional templates. Underlying delivery configuration controlled by you; customers see only customer-facing features.

Customer panel branded to your style (colours, logo, domain) or kept as plain MailWizz default. Your call. Branding configurable post-launch; we walk through branding setup in onboarding hours if you want help.

04

5 dedicated IPs warmed and ready

Five IPv4 addresses from a clean /24, each with custom rDNS aligned to sending domains you provide. All five warmed in parallel over the 30 days preceding handover, so they reach you with established Postmaster Tools ratings and SNDS scores.

You assign IPs to customer pools or use them as IP rotation under MailWizz. Standard architectures: 5 IPs split as 2 transactional + 2 marketing + 1 dedicated to largest customer. Your call; we suggest patterns in onboarding hours.

05

Custom rDNS + DKIM + SPF + DMARC + MTA-STS

Per-IP PTR records aligned to sending domain pattern. DKIM keypairs (2048-bit RSA) per tenant domain. SPF records with explicit ip4: declarations covering all 5 IPs. DMARC policies at p=none reporting initially (graduates to p=quarantine after warmup stabilises). MTA-STS policy files at canonical .well-known location. TLS-RPT records for delivery reports.

All authentication verified from independent test infrastructure before launch. If any check fails, we fix before customer onboarding begins. Standard scope covers up to 3 tenant domains at launch; additional domains added as customers onboard.

06

2 hours expert onboarding

Two hours with senior deliverability engineer. Walk through: PowerMTA configuration architecture, MailWizz administration interface, customer-onboarding flow, IP-rotation strategy, monitoring dashboard interpretation, FBL processing, bounce-categorisation logic, common customer support scenarios.

Telegram async or live call, your preference. Recording available if you want to review later or share with additional team members. Beyond included 2 hours, additional consulting at €199/hour standard rate.

07

Monitoring stack configured (ongoing)

Postmaster Tools (daily polling per tenant), SNDS (hourly, per IP), 84 RBLs every 15 minutes (per IP), FBL ingestion from major receivers, content classifier estimates weekly. Same scope as standalone Deliverability Monitoring (€49/mo per tenant) bundled into the €499 subscription.

Telegram alerts route to your operations channel. Customer-tenant alerts can route to customer-specific channels if you implement (post-launch configuration).

08

What's NOT included

Customer billing platform (you bring: Stripe, Paddle, crypto, your billing logic), customer signup flow (you build: marketing site, payment integration), customer acquisition (you market), customer support staff (you hire), abuse handling staff (you implement; AUP is yours to enforce), legal entity (you register if needed), payment processing (your responsibility).

questions before launch

Frequently asked.

Why launch your own ESP instead of reselling SaaS?

Reselling SaaS gives ~30-40% margin and zero infrastructure control. Operating your own ESP gives 60-80% margin, full control over deliverability decisions, IP rotation flexibility, jurisdiction choice, at the cost of operational responsibility.

Right answer depends on whether deliverability differentiation is part of your value proposition. If you compete with SendGrid on brand and ease-of-use, reselling their stack with billing UI works. If you compete on infrastructure quality (vertical reputation, IP rotation, regional jurisdiction), you need infrastructure control resale can't provide.

How many customers can the bundle support?

Comfortably 20-40 active customers at typical SaaS-ESP volumes (10K-100K monthly each). Architecture scales to ~80-100 customers before hardware capacity becomes constraint and second server makes sense. Bundle is sized for first 12-24 months of growth, not perpetual scaling.

Beyond ~80 customers, two paths: add second Iron-E5 server (€499/mo additional, doubles capacity) or upgrade to higher-tier server (Iron-E7 with 256 GB RAM, €699/mo). Most ESPs reach 20 customers within 12-18 months at moderate marketing investment.

Can I run this on bare-metal we already have?

Possible but adds complexity. Hardware requirements: 16+ CPU cores, 64+ GB RAM, NVMe storage, dedicated 1 Gbps network with 5+ IPs available. PowerMTA license is transferable; we can re-license for your hardware (some additional cost for license re-issuance).

Most operators find the bundled hardware sensible because jurisdiction matters (you want hosting in EU sovereign or offshore for ESP business; many existing setups are US-located which limits target market). Discuss in pre-purchase Telegram conversation.

What happens if a customer abuses the platform?

Operational responsibility on your side. You enforce AUP (Acceptable Use Policy), you handle complaints, you suspend abusers. We provide AUP template language and abuse-handling playbook in onboarding. We provide backup support in office hours for genuinely complex cases.

Repeat abuse pattern from your customers damages our shared IP reputation across the platform. We monitor for fleet-wide abuse signals; if your tenant's behaviour starts affecting other tenants, we contact you for resolution. Persistent abuse without resolution can lead to platform termination (last resort; rare).

Can I customise PowerMTA configuration?

Yes. You have full root SSH access to the server; PowerMTA configuration is yours to modify post-launch. We provide reference configuration as starting point; advanced operators often customise for vertical-specific patterns (transactional vs marketing split, customer-tier rate limiting, custom bounce categorisation).

Office hours included for configuration questions. Beyond included hours, advanced configuration consulting at €199/hour. Most ESPs run reference configuration unchanged for first 6-12 months and customise once specific patterns emerge.

Do you provide customer billing?

No. Customer billing is your responsibility: payment processor (Stripe, Paddle, crypto via BTCPay, whatever fits), pricing tiers (you decide), invoice generation (your billing platform), tax compliance (your jurisdiction). MailWizz does have basic per-customer usage tracking; you integrate with your billing system.

Many operators use Stripe for fiat customers and BTCPay for crypto-paying customers. Some use Lago or Chargebee for usage-based billing. Whatever fits your customer base; we don't lock you into specific billing platform.

How do I handle deliverability incidents?

First-line incident handling is yours: customer reports issue, you investigate (monitoring dashboards, MailWizz campaign data, customer's specific sending pattern). Most incidents (60-80%) resolve through customer-side fixes: list cleaning, content adjustment, sending pattern.

Escalate to office hours for complex incidents: RBL listings affecting your IPs, sustained inbox-rate collapse, infrastructure-side issues. Office hours included monthly; additional consulting at €199/hour. Most ESPs use 1-3 hours/month escalation in steady-state.

What if I want to scale beyond bundle capacity?

Three paths depending on growth: (1) Add second Iron-E5 server €499/mo additional (doubles capacity); (2) Upgrade to Iron-E7 server €699/mo (256 GB RAM, more cores, denser single-server scaling); (3) Multi-region deployment for jurisdiction-specific customer cohorts (custom quote).

Most ESPs scale via path (1) until ~150 customers, then evaluate (3) for jurisdiction-specific growth. Path (2) fits operations with very high per-customer volumes (TX email or large e-commerce ESPs).

How does cancellation work?

Cancel anytime via Telegram. Setup fee (€1,499) is non-refundable since the work has been done. Monthly fee prorates to cancellation date. Server, PowerMTA license, MailWizz license, IPs all transfer to you on cancellation; you can self-host going forward.

About 5-10% of starter-kit ESPs cancel within first 12 months, usually because the business case didn't pan out (insufficient customers, market validation challenges). The infrastructure remains yours; some operators self-host for personal use even after winding down customer business.

How does payment work?

Setup fee (€1,499) charged at order; first month (€499) charged at server provisioning. Subsequent months billed in advance on subscription anniversary. Payable in any of our 11 supported cryptocurrencies via self-hosted BTCPay. Pre-paid 6-month: 5% discount. Pre-paid 12-month: 10% discount.

ESP starter scope appropriate for first 12-18 months of operation

The ESP starter pack covers what operators actually need during the first 12-18 months of running an ESP-style operation. The scope reflects the operational reality rather than aspirational positioning that promises capabilities operators do not yet need.

Initial deployment covers: hosting infrastructure adequate for first 100-500 customer accounts, MailWizz or Acelle deployment with appropriate configuration, sending infrastructure with initial IP allocation sized for projected first-year volume, basic monitoring infrastructure with alerting through standard channels, customer-facing branding configuration.

Ongoing operational coverage includes: monthly check-ins for the first 6 months covering operational tuning as customer base develops, quarterly check-ins thereafter, deliverability incident response when reputation events affect the operation, infrastructure scaling guidance as customer growth approaches initial allocation limits.

ESP starter pack pricing at EUR 1,499 monthly covers the integrated scope. Operations growing beyond starter pack scope (typically when customer count exceeds 500 or aggregate volume exceeds 10M monthly) graduate to professional or enterprise tier with expanded scope matching the larger operational requirements.

Ready to launch your ESP?

Telegram order takes 30 minutes (longer than other bundles because we discuss your model, target customers, jurisdiction choice). Server provisioned within 48 hours; warmup begins on confirmed sending domains. Production-ready ~6 weeks from order. Cancel anytime, infrastructure transfers to you.

# Median Telegram response: 12 minutes during operating hours