Independence
You set the service rules, allowed topics and how you work with clients — not someone else’s moderation team.
Your own email service
Info · your own email service
Your own email service build it from ready-made software or order it turnkey
A service where your clients send email through your platform — on your servers and under your brand. A platform with clients and pricing plans runs the campaigns; MTA-Hub runs the infrastructure underneath: nodes, IP addresses, domains, warm-up and reputation monitoring.
- Your servers and your data
- Clients under your brand
- IP pools for client groups
- Warm-up for every new IP address
Your clients
accountsplans and quotastheir own campaigns
send through your platform
Service platform
Mumara ESPProtosenderMailWizz
sends through the Hub’s sending points
MTA-Hub · your fleet
PowerMTA and MailerQ nodesdomainswarm-up
01 / Why
Why your own service, not someone else’s
Someone else’s email service decides for you: which topics are allowed, how much a subscriber costs, and when to block your account. Your own service works by your rules.
Your data stays with you
Your service’s clients, their subscribers and their emails live on your servers and don’t go anywhere.
Your own economics
You pay for servers and licenses, not for every subscriber. You set your clients' prices yourself.
Your own brand
Clients work in accounts on your domain and see your service, not someone else’s.
02 / What it’s made of
Four layers of an email service
All the software is ready-made and installs on your servers. You don’t need to write your own service from scratch: you need to put the layers together correctly and connect them.
1. A platform with clients and plans
Mumara ESP — client accounts, a support portal and client signup through WHMCS. Protosender — pricing plans, quotas and payment gateways. MailWizz — clients and plans with a rich API.
Platform comparison2. An MTA on your nodes
PowerMTA — the standard for email platforms and the most you can get from one server. MailerQ — queues and changes on the fly, if you’ll have your own code around delivery.
PowerMTA vs MailerQ3. MTA-Hub — the infrastructure
MTA installation, configurations, domains and DNS, proxies, warm-up, monitoring and stats — plus export of ready sending points to the service platform.
About MTA-Hub4. An AI layer — optional
Six AI Core tools in MailCore platforms: offer analysis, emails and series, spam checks — things your clients will value in their accounts.
MailCore System03 / How to build it
Six steps to your first client
Order matters: first the sizing and a warmed-up infrastructure, then clients. Running a cold IP address at full power is the fastest way to ruin your reputation on day one.
- 01
Sizing
A Specification for the total volume of your future clients: how many nodes, IP addresses and domains you need at launch.
- 02
Platform
Install the service platform, set up your domain and brand, plans and client permissions.
- 03
Servers and MTA
The Hub installs PowerMTA or MailerQ on the nodes and builds their configuration.
- 04
Domains and warm-up
Sending domains with DKIM signatures and reverse DNS (PTR), and IP warm-up to working volume.
- 05
Sending points
The Hub hands the platform IP addresses and pools with a warm-up limit; the platform assigns them to clients.
- 06
Monitoring
Bounces, complaints and reputation for every sending point, plus policies that react on their own.
04 / Think about it in advance
An email service is more than sending
Your own service brings tasks you don’t have when sending to your own list: other people’s lists, other people’s emails and a shared reputation. Here’s what to decide before your first client.
Separating clients
Separate IP addresses and pools for different client groups, so one client with a bad list doesn’t ruin the reputation for everyone else. The Hub exports both single IP addresses and pools — the platform assigns them to clients.
Complaints and unsubscribes
Complaints and unsubscribes are visible for every sending point over the last 24 hours, and a shared suppression list stops emails to people who have already unsubscribed.
Warming up new IP addresses
Every new IP address and domain goes through warm-up, and the warm-up limit goes to the platform along with the sending point — a client never gets a cold IP address at full power.
Reputation under watch
Bounces by category, recipient domain and vMTA, plus blacklist checks for IP addresses and domains — you see whose traffic dropped and why.
Service rules
You decide what your clients may send and where their lists may come from. The platform gives you permissions and limits by group — set them up before your first client.
Data and access
Everything is on your servers: the Hub doesn’t take contacts or emails, login is protected with two-factor authentication, and the log shows who did what.
05 / Two paths
Build it yourself or order it turnkey
The software is the same. The difference is who installs and connects the layers: your team or us.
Build it yourself
If you have a sysadmin on your team:
- platform and MTA licenses — from MailCore System;
- MTA-Hub license — on the Pricing page;
- fleet sizing — with the Hub’s Specifications module;
- MTA installation, domains and warm-up — from the Hub panel.
Turnkey
If you need a ready service:
- sizing and a cost estimate — before work begins;
- servers, the service platform, the Hub and the MTA;
- domains, DKIM signatures, warm-up and sending points;
- handover of access and team training.
06 / Questions
Questions about your own email service
Didn’t find your answer? Email site@mta-hub.com or message us on Telegram.
Which platform should I use for the service?
Mumara ESP — if you need client accounts, a separate support portal and client signup through WHMCS. Protosender — if pricing plans, quotas and payment gateways matter. MailWizz — clients and plans with a rich API. Details are in the platform comparison.
How many servers do I need?
It depends on your clients' total volume and how many IP groups you want to keep apart. The Hub’s Specification calculates this from your answers — with a formula behind every number.
How do I stop one client from ruining the reputation for everyone else?
Split clients across IP addresses and pools. The Hub exports both single IP addresses and pools to the platform, and the platform assigns them to clients. Bounces, complaints and blacklists are visible for every sending point — you see right away whose traffic dropped.
Can I give clients dedicated IP addresses?
Yes. A single IP address goes to the platform as its own sending point — with a warm-up limit if it’s still warming up — and the platform assigns it to the client.
Do I need AI?
Not necessarily. The Hub works without AI. The AI layer in MailCore platforms is extra value for your clients: emails, series and spam checks right in their account.
How much does a launch cost?
It adds up from licenses — the platform, the MTA and the Hub — plus server rental. The Hub license is on the Pricing page; the platform and MTA come from MailCore System. If you order it turnkey, we’ll prepare a cost estimate for the work after a brief.
07 / Next step
Launch your own email service
Start by sizing the fleet for your future clients — or describe your task, and we’ll build the service turnkey.
What you’ll need
- 01A service platformMumara ESP, Protosender or MailWizz.
- 02ServersFor the platform, the Hub panel and the sending nodes.
- 03LicensesFor the platform, the MTA and the Hub — in your name.
- 04DomainsFor your service’s client accounts and for sending.
- 05Service rulesWhat your clients are allowed to send.