Keep yours. The Hub connects to Protosender, Interspire, Mumara and MailWizz and hands them sending points — no need to move.
Integrations
Protosender — if you need automation and AI tools. Interspire — if simplicity matters more.
Platform comparison
Mumara — hundreds of threads and everything built in. Or Protosender with rotation of emails and SMTP servers for each mailbox provider.
Platform comparison
Your MTA. The Hub manages PowerMTA 6 and MailerQ 5.16 and connects nodes that are already running.
About MTA-Hub
PowerMTA — the standard for email platforms. MailerQ — if you’ll have your own code and a cluster around delivery.
PowerMTA vs MailerQ
Specification → MTA installation → domains and DNS → warm-up → sending point export to your platform.
Specifications Warm-up
Bounces by category and domain, breakdowns by mailbox provider, DNS record and DKIM signature checks, and warm-up that slows down when bounces rise.
Bounces Mailbox providers DNS
A node registry, configuration checks across the whole fleet, monitoring, policies and shared operations for PowerMTA and MailerQ.
Nodes Configurations Monitoring
On your own, with the Hub. The license is on the Pricing page; a good place to start is sizing your fleet.
Pricing Specifications
Turnkey. We build it, warm it up and hand it over with training. Cost estimate before work begins.
Send a request
Start with sizing — it doesn’t commit you to anything — and decide from the estimate: on your own or turnkey.
Specifications Turnkey
Start with the cause: bounces by category show where the problem is — in the list, in the email, or in the sending IP address. New IP addresses and warm-up don’t always help.
At this volume, the fleet is sized in advance: a Specification shows how many nodes, IP addresses and domains you need and what they’ll cost.
You can start with one or two nodes. New IP addresses and domains need warm-up at any volume.