Skip to content
Multi-tenant · MailWizz · PowerMTA · Per-tenant IPs

Hosting for ESP Resellers
infrastructure for operators running their own ESP business.

ESP reseller economics work when the infrastructure layer is operationally serious. Multi-tenant MailWizz or Acelle on PowerMTA-tuned servers, dedicated IPs assigned intelligently, FBL processing across the tenant base, and operational support that understands the reseller model rather than treating it as just another VPS workload.

Quick answer

ESP reseller hosting describes infrastructure for operators running multi-tenant email platforms as their own ESP brand. The standard stack includes MailWizz or Acelle Mail (multi-tenant platform), PowerMTA (high-volume SMTP delivery), MySQL/MariaDB database, dedicated IP pool for tenant assignment, FBL processing, and operational tooling. Infrastructure typically runs on dedicated servers rather than VPS for performance. Pricing for ESP reseller infrastructure starts around €299/month for entry setups and scales to €1,500+/month for larger resellers. The model differs from direct campaign operation because the operational complexity is significantly higher and the reseller must isolate tenants operationally.

Key facts about ESP reseller hosting

  • Reseller market dynamics: Mainstream ESP categories (general bulk email, B2C marketing, B2B outreach) have established competition. Specialty resellers focus on niches: crypto-friendly ESPs, adult-industry ESPs, regional language ESPs, vertical-specific ESPs.
  • Platform options: MailWizz ($69 commercial PHP license, multi-tenant native), Acelle Mail (open-source, similar features), Mautic (open-source, more marketing-automation focused), Sendy (simpler, single-tenant by default), custom platforms (Rails/Django/Go).
  • SMTP backend: PowerMTA dominates for high-volume reselling (commercial license, mature deliverability). Postal is open-source alternative. Postfix works at lower volumes.
  • Tenant scale economics: 5-20 tenants is small reseller. 20-100 tenants is mid-size. 100-500+ tenants is large reseller (typically multiple infrastructure clusters).
  • Per-tenant IP economics: Dedicated IP per tenant at €8/month = €8 cost per tenant per month. Shared IP pool reduces this but increases cross-tenant reputation risk.
  • Daily volume range: Small reseller 50K-500K daily messages. Mid-size 500K-5M daily. Large reseller 5M-50M+ daily.
  • Pricing models for end-customers: Per-subscriber monthly, per-message, hybrid base + overage, or volume-based tiers. Most successful resellers use simpler pricing than mainstream ESPs to differentiate.
  • Authentication infrastructure: Each tenant sending domain needs SPF, DKIM (2048-bit), DMARC. Per Google\'s bulk sender requirements, authentication compliance is non-negotiable for 5K+ daily sending.

The ESP reseller business model

The ESP reseller business is a specific niche within email infrastructure. The reseller operates their own brand, customer-facing platform, billing relationship, and support. The reseller's competitive advantage is typically one or more of: specialty market focus (crypto, adult, specific vertical), pricing positioning (cheaper than mainstream ESPs at scale), content latitude (accepting senders mainstream ESPs decline), regional positioning (better fit for specific geographic markets), or operational features (specific integrations or capabilities).

The reseller's customers are end-senders running their own email operations: small businesses, marketers, affiliate operators, agencies, content publishers. The customer relationship is similar to mainstream ESPs from the end-customer perspective: signup, plan selection, payment, sending campaigns, viewing reports. The customer typically does not see or care about the underlying infrastructure.

The reseller's relationship with infrastructure providers (like us) is wholesale. We provide the infrastructure capacity (servers, IPs, network, operational support) and the reseller provides the customer-facing operation. The economics work when the reseller's revenue per tenant exceeds the per-tenant infrastructure cost by a margin sufficient to cover operations, marketing, support, and profit.

The platform decision: MailWizz vs Acelle vs alternatives

The choice of customer-facing platform is one of the most consequential decisions for an ESP reseller. The platform shapes operational workflow, feature differentiation, and tenant experience.

PlatformLicenseMulti-tenantStrengthsLimitations
MailWizz$69 commercial PHPNativeMature, widely-used, good ecosystemOlder PHP codebase, dated UI
Acelle MailOpen source / $59 license tiersNativeSimilar to MailWizz, active developmentSmaller ecosystem
MauticOpen sourceWorkaround requiredMarketing automation featuresNot native multi-tenant
Sendy$69 commercialLimited (workaround)Simple, SES-optimizedNot designed for reselling
ListmonkOpen sourceWorkaround requiredModern Go-based, fastNot built for reselling
Custom Rails/DjangoDevelopment costCustomer's designFull control, unique featuresSignificant development cost

Why MailWizz dominates reseller deployments

MailWizz has become the de facto standard for ESP reselling for several reasons. Native multi-tenant from day one. Built-in customer management, billing integration capability, and tenant-specific branding. Customer portal that tenants find familiar (similar enough to mainstream ESP UIs that learning curve is manageable). Active development with regular feature additions. Established integration ecosystem with email validation services, payment processors, and SMTP backends.

MailWizz's limitations are real but manageable: older PHP codebase that requires specific PHP versions and module configurations, UI that looks dated compared to modern SaaS UIs, occasional performance issues at very high scale that require database tuning. None of these are showstoppers for typical reseller operations.

Why Acelle is the open-source alternative

Acelle Mail provides similar multi-tenant ESP features as MailWizz with an open-source license model (with optional paid support). Active development, similar feature set, slightly different UI patterns. Resellers preferring open-source or wanting to modify the platform code use Acelle. The community is smaller than MailWizz but actively maintained.

When custom platforms make sense

Resellers operating at sufficient scale to amortize development costs build custom platforms for specific reasons: unique feature differentiation that mainstream platforms cannot support, specific integration requirements with niche tools, performance requirements that exceed what MailWizz or Acelle can handle, or strategic reasons to own the platform IP. Custom development typically requires €50K-€200K initial investment plus ongoing maintenance.

The PowerMTA decision for high-volume reselling

The SMTP backend choice matters most at scale. Below 100K daily messages, the difference between options is operationally invisible. Above 1M daily messages, the choice becomes significant.

PowerMTA strengths

PowerMTA is the industry-standard high-volume MTA. Used by most major ESPs internally (SendGrid, Mailgun, and others run PowerMTA or similar commercial MTAs at scale). The product has 25+ years of optimization for email-specific workloads: connection pooling, retry logic tuned for specific receivers, VMTA configurations for tenant isolation, sophisticated traffic shaping, queue management at massive scale. The license cost is significant but the operational benefit at high volume justifies it for serious resellers.

PowerMTA cost considerations

The PowerMTA license is the primary cost barrier. Pricing varies by scale and is negotiated with Bird (the current owner after the SparkPost acquisition history). Annual licenses typically range from several thousand to tens of thousands of dollars depending on volume tier and feature set. For resellers operating below 1M daily messages, the license cost may exceed the operational benefit over open-source alternatives.

Open-source alternatives

Postal is the most credible open-source alternative for ESP reseller use. It is designed specifically for transactional and bulk email, handles VMTA-style isolation, integrates with MailWizz and Acelle. Performance is lower than PowerMTA at extreme scale but adequate for most reseller use cases. Postfix with heavy tuning works at moderate scale; pure Postfix struggles at million-plus daily message volumes without significant operational attention.

The hybrid approach

Some resellers operate hybrid setups: PowerMTA for premium tenants where deliverability ROI justifies the license cost, Postal or Postfix for budget-tier tenants where the cost difference matters. The architecture is operationally more complex but produces better unit economics across tenant segments.

The tenant isolation architecture

Multi-tenant ESP operation requires operational isolation between tenants. Without isolation, one bad tenant's abuse damages the entire reseller's reputation. The isolation happens at several layers.

Authentication isolation

Each tenant operates their own sending domains with their own SPF, DKIM, and DMARC records. The reseller's infrastructure does not co-mingle authentication across tenants. A tenant's bad authentication does not affect other tenants' delivery.

IP isolation

The most operationally significant isolation. Each tenant either has dedicated IPs (preferred for high-volume tenants) or shares IPs with other tenants who have similar risk profiles. Pool segmentation: high-quality engaged-list tenants on Tier 1 IPs, mid-quality tenants on Tier 2, new or higher-risk tenants on Tier 3 IPs. The pool architecture prevents one tenant's complaint rate from damaging Tier 1 IP reputation that other tenants depend on.

Sending throughput isolation

VMTA configuration in PowerMTA allows per-tenant throughput limits. The reseller can guarantee Tenant A's sending continues at full rate even when Tenant B has high bounce rates that would otherwise trigger receiver-side throttling on the shared infrastructure.

Reputation tracking isolation

Per-tenant analytics: bounce rates, complaint rates, open rates, deliverability metrics. The reseller can identify which tenants are creating reputation problems before the problems propagate across the pool. Action: alert the tenant, reduce their sending rate, move them to lower-tier IPs, or terminate the relationship.

Compliance isolation

Each tenant has their own suppression list, unsubscribe handling, and complaint processing. Tenants do not share suppression lists (one tenant's unsubscribers are not automatically suppressed for other tenants). The legal compliance posture remains tenant-specific.

How our infrastructure supports ESP resellers

Our role in the ESP reseller stack is specific. We provide the infrastructure layer with operational characteristics tuned for the reseller use case.

Dedicated servers tuned for ESP platforms

MailWizz and Acelle perform best on dedicated hardware with specific tuning: sufficient RAM for the campaign queue processor, NVMe storage for the database, dedicated CPU for the queue worker pool. Generic VPS hosting works at small scale but creates performance bottlenecks above 100K daily messages. Our dedicated servers (€99-€999/month) provide the hardware tier resellers need.

PowerMTA managed installations

For resellers who need PowerMTA, we provide managed installation packages: license acquisition, PowerMTA installation on dedicated hardware, initial configuration of VMTAs, integration with MailWizz/Acelle, ongoing maintenance. The customer pays for the PowerMTA license plus our managed installation pricing.

Clean IP pools with pre-flight validation

Our IP pool for reseller deployments is pre-validated through the 14-check pre-flight: Spamhaus SBL/XBL/PBL, SURBL, Microsoft SNDS, Google Postmaster Tools history, SpamCop, UCEPROTECT, Barracuda, Senderbase, Composite Block List, reverse DNS history, and PTR pattern analysis. IPs that fail any check are not assigned. The reseller starts with a clean foundation.

Custom rDNS per IP

Each IP is configured with reverse DNS pointing to a hostname under the tenant's domain. The PTR record matches the HELO/EHLO greeting the SMTP server sends. Receiving providers check this alignment as one of many sender legitimacy signals.

FBL processing infrastructure

We operate FBL relationships with Microsoft (SNDS feedback), Yahoo, Comcast, Cox, and other receivers. Complaint signals flow to our processing pipeline and route to the appropriate reseller account with per-tenant suppression tagging. The reseller integrates the suppression data into their platform's tenant management.

Monitoring and alerting

Pool-level reputation monitoring across Spamhaus, SNDS, Postmaster Tools v2. Alert thresholds defined per reseller. When pool reputation degrades, we contact the reseller for triage rather than letting the deliverability problem compound silently.

Operational consultation

Resellers face operational situations we have seen before: sudden complaint rate spike from a tenant, unexpected blacklist event on a specific receiver, IP warmup timing for new pool additions, tenant migration from another ESP, scaling decisions as the reseller grows. Our team has years of operational experience in the segment and provides consultation on these decisions.

The reseller economics in detail

Revenue model variations

Per-subscriber monthly: $0.10-$1 per 1000 subscribers per month. Simple to communicate, complex when tenants have variable list sizes.

Per-message: $0.0001-$0.001 per message. Aligns cost with usage but penalizes tenants with infrequent high-volume sends.

Hybrid base + overage: monthly base fee plus per-message overage above included quota. Most resellers use this model.

Volume tier: flat monthly price per volume tier. Simple, predictable for tenant, may leave revenue on the table for high-volume tenants.

Typical tenant pricing

Small B2B reseller selling cold email infrastructure: $200-$500/month per tenant for 100K-500K monthly messages.

B2C newsletter ESP: $50-$300/month per tenant for 100K subscribers with weekly sending.

Vertical specialty (crypto, adult, etc.): premium pricing due to mainstream ESP exclusion. $300-$1,500/month per tenant.

Margin analysis

Reseller revenue per tenant: $200-$1,500/month depending on segment.

Infrastructure cost per tenant: $20-$100/month (IP, share of fixed costs, support overhead).

Gross margin: 70-90%. The healthy margin compensates for marketing, support, churn, and operational risk.

Scaling efficiency

Fixed infrastructure costs (PowerMTA license, base servers, monitoring infrastructure, FBL relationships) amortize across more tenants. Adding the 50th tenant adds incremental cost (IP, support time, suppression list) but not full base infrastructure. Resellers reach efficient scale at 20-100 tenants depending on tenant size profile.

Common operational scenarios we help with

Reseller launch

New reseller standing up their first deployment. Platform installation, PowerMTA integration, initial IP pool, first 5-10 tenants. Onboarding period takes 30-60 days from infrastructure provisioning to first tenant campaigns.

Migration from another infrastructure

Existing reseller moving from another provider. The migration involves: database export from old platform, infrastructure provisioning at ASH, database import and configuration adjustment, IP warmup on new addresses (existing IP reputation does not transfer), DNS cutover with low TTL, parallel operation during validation, termination at old provider.

Scaling expansion

Reseller adding capacity for new tenants or volume growth. Additional IPs, additional dedicated servers, potentially additional jurisdiction expansion. Planning includes IP warmup timeline, DNS configuration changes, and platform-side capacity planning.

Reputation recovery

Reseller recovering from a deliverability incident (specific blacklist event, sustained complaint rate spike, IP range damage from problem tenant). Recovery involves identifying the source (which tenant, which content category, which sending pattern), remediating at the source, and coordinating IP rehabilitation across receivers.

Tenant termination

Reseller terminating a problem tenant. The process: documentation of policy violations, tenant notification per terms, data export window for the tenant, account suspension. The infrastructure layer supports the termination workflow but the reseller makes the business decision.

What we honestly recommend against

Starting at infrastructure tier

Resellers should not start with the most expensive infrastructure. Begin with entry-tier servers, build the tenant base, scale infrastructure as revenue justifies. The temptation to "build it right from the start" often produces infrastructure costs exceeding revenue for months.

PowerMTA below volume threshold

PowerMTA license costs significant money. Below 500K daily messages, the license cost typically exceeds the deliverability benefit over open-source alternatives. Start with Postal or Postfix. Migrate to PowerMTA when volume justifies it.

Over-allocating dedicated IPs

Dedicated IPs require maintained sending volume to preserve reputation. A new dedicated IP without sufficient sending becomes a stale IP with neutral or negative reputation. Start with shared IP pools for new tenants, move them to dedicated when their volume warrants.

Multi-jurisdiction at launch

New resellers do not need infrastructure in multiple jurisdictions immediately. Single jurisdiction is operationally simpler and cheaper. Expand to additional jurisdictions only when tenant base demands it (specific tenant requirements, geographic redundancy needs, regulatory diversity).

Marketing positioning that promises everything

Resellers competing on "we accept anything" race to the bottom of the market and inherit abuse problems that damage the business long-term. Specialty positioning (specific verticals, specific use cases, specific operational features) produces better unit economics than mass-market generic positioning.

Related operational reading