MTA-Hub — an AI control panel for PowerMTA, MailerQ and your whole SMTP infrastructure
Design, connect, warm up and monitor MTA clusters from a single panel. MTA-Hub brings together servers, IPs, domains, vMTAs, queues, configurations and Prometheus metrics — while AI audit tells you what to do next.
server-01· PowerMTA · prod-euHEALTHYserver-03· PowerMTA · warmup-aWARMUPserver-11· MailerQ · prod-usRISKInfrastructure grows — and manual management turns into chaos
One or two SMTP servers can still live "in your head". But once PowerMTA and MailerQ nodes grow into dozens, along with hundreds of IPs and domains, — without a central panel you lose both visibility and control.
Scattered servers
IPs, domains and vMTAs are spread across panels, spreadsheets and admins' heads. There is no single registry — nobody knows exactly what runs where.
Configs drift apart
PMTA and MailerQ settings are duplicated by hand and inevitably drift between nodes. Which server runs which version is anyone's guess.
Queues swell unnoticed
While you watch one server, a queue grows on another. The problem surfaces after the fact — when delivery has already dropped.
Failure source unclear
4xx/5xx pour in, and without consolidated metrics and logs you can't tell: is it the config, IP reputation, content, or node overload.
Edits straight in files
Changes go over SSH into live configs — no validation, no review. One typo costs hours of downtime.
No rollback, no analysis
No version history, no audit log, no AI hints. Every incident is investigated from scratch and from memory.
Important to understand: Protosender, Mumara and Interspire are great at sending campaigns — but deep infrastructure management underneath them is not their job. That takes a dedicated command center.
MTA-Hub turns scattered servers into a managed system
One pipeline: from the goal and an AI plan — to monitoring, audit and optimization. All in one panel, with history and the right to make mistakes.
Without MTA-Hub
- Configs edited by hand over SSH — each server has its own
- Queues and errors live in different windows and panels
- Warm-up by eye, with no risk control
- A dangerous change can't be rolled back — versions aren't stored
- Incidents get caught after the fact, when delivery has already dropped
With MTA-Hub
- Configs via templates, diff and validation — one standard across all nodes
- Queues, errors and metrics — in one panel across all servers
- Gradual warmup with segments and risk monitoring
- One-click rollback + a full audit log of changes
- AI Core signals early — before the incident becomes visible
From goal to optimization — AI Core plans the infrastructure on the way in and audits how it runs on the way out.
Eight modules — full infrastructure control
From an AI plan and a server registry to safe configurations, warm-up and exporting ready pools into your sending platform.
AI Infrastructure Planner
You pick the goal, volumes, list source and MTA type — AI Core generates an infrastructure plan and a diagram.
- Goal and expected volumes
- Sending model and MTA type
- Ready plan + diagram
Server & MTA Inventory
A central registry of the whole infrastructure — nothing lives "in spreadsheets and heads".
- Servers, IPs, domains, vMTAs
- MTA type, provider, location
- Role, status, warmup/production
Prometheus Monitoring
PowerMTA metrics via the native exporter — consolidated across all nodes at once.
- Traffic and queues
- SMTP connections and errors
- Latency and first-attempt
Queue & Error Control
Queues and errors under constant watch — problem nodes are visible immediately.
- Queue size and dynamics
- 4xx / 5xx / transient
- Delays and problem nodes
Configuration Management
PMTA and MailerQ configurations — as code: with review, history and the right to roll back.
- Templates and a directive library
- Diff + validation before deploy
- Rollback and audit log
Warmup Manager
Controlled rollout of infrastructure into production — without burning fresh IPs.
- Active segments
- Gradual sending and limits
- Risk monitoring → production
API Export
Ready production pools go straight into your sending platform.
- Export to Protosender
- Mumara / Interspire
- Strategy ↔ infrastructure
AI Infrastructure Audit
AI Core regularly reviews the whole picture and tells you what to fix first.
- Metrics, queues, errors
- Configuration changes
- Risk patterns + recommendations
Prometheus shows what's happening. MTA-Hub explains what to do next
PowerMTA exposes metrics in Prometheus format. MTA-Hub collects them from every node, joins them with logs, webhooks and campaign data — and turns it all into one observable picture with AI conclusions.
| Node | MTA | Pool | Queue | 4xx | 5xx | Latency | Status |
|---|---|---|---|---|---|---|---|
server-01 | PowerMTA | prod-eu | 12.4K | 1.2% | 0.3% | 820ms | HEALTHY |
server-03 | PowerMTA | warmup-a | 48.2K | 4.8% | 0.9% | 1.9s | WARMUP |
server-07 | MailerQ | prod-us | 9.1K | 2.1% | 0.4% | 640ms | HEALTHY |
server-11 | PowerMTA | prod-eu | 62.7K | 7.3% | 2.1% | 3.4s | RISK |
server-14 | SMTP | prod-asia | 5.8K | 1.0% | 0.2% | 510ms | HEALTHY |
AI Metrics Auditor: on server-11 the 4xx growth coincided with a rise in outbound connections. I recommend slowing down the prod-eu pool and reviewing the latest configuration changes.
traffic_recipients_total — traffic volume per node in real time.
current_queue_size — queue size in recipients and bytes: node load at a glance.
smtp_errors_total — 4xx/5xx signal delivery and reputation problems before the complaints arrive.
request_duration_seconds — whether the MTA node is overloaded right now.
first_attempt_seconds — how fast the first attempt goes out after inject.
The combined metrics roll up into an AI Score — an overall verdict on the node's state.
Not a copywriter — an infrastructure analyst
AI Core in MTA-Hub doesn't write emails. It plans, warms up, reviews configs and investigates incidents — like a seasoned deliverability engineer who watches every metric at once and never sleeps.
Turns your goal and volumes into an infrastructure plan and diagram.
Picks the pace and segments for gradual warm-up.
Explains directives and risks, recommends safe values.
Correlates metrics and events during delivery incidents.
Regularly cross-checks metrics and queues — catches anomalies.
Scores the risk of going to production and of config changes.
Prepares documentation for the infrastructure and decisions.
Concrete, safe steps for every finding.
The queue on server-03 has been growing for the last 45 minutes.
The 4xx growth coincided with a rise in outbound connections.
Moving to production is premature: the bounce rate is above the acceptable level.
I recommend slowing down the pool and reviewing the latest configuration changes.
The server-07 configuration differs from the production-pool-v2 template.
PMTA and MailerQ configs — safe, like code
Templates, a directive library with explanations, AI recommendations, diff before apply, validation, safe deploy and rollback. The core principle: no dangerous change is ever applied blindly.
From the library — each explained with its purpose and risks.
AI shows what makes the directive dangerous and which parameters are critical.
Values apply at the server / vMTA / domain / pool level.
Before/after changes are fully visible before anything is applied.
Syntax check and safe apply, recorded in the audit log.
Revert to any past version — in one click.
Infrastructure goes live gradually and under control
Active segments, controlled pace, monitoring of errors and reputation risks — and only then production mode. No "cranked it to full — burned it in a day".
Active in the last month
Hot segments from your sending platform — for the early warm-up stages: fast feedback, minimal bounces, reputation grows from day one.
Active 1–3 months
Warm segments for scaling the volume: we verify the reputation holds on bigger traffic before fully switching to production.
Reputation-aware sending — honestly: MTA-Hub doesn't "guarantee the inbox" — nobody can. It does something else: keeps pace, errors, queues and risks under constant control so your reputation grows instead of burning out.
The infrastructure layer between sending and MTA clusters
MTA-Hub sits at the center of the ecosystem: sending platforms above, MTA nodes below, observability, CRM and AI Core alongside. All data and commands flow through one hub.
← scroll the scheme horizontally →
- SMTP/MTA pool export
- Strategy ↔ infrastructure
- Warmup segments
- Revenue attribution via KendaliCRM
- SMTP pool export
- Status synchronization
- Sending infrastructure mapping
- SMTP export
- Pool grouping
- Sending node management
- Sales attribution
- Customer journeys
- Revenue reports
- Prometheus metrics
- Configuration management
- Queues, domains, vMTA
- Operational commands
- API integration
- Queue monitoring
- Server statuses
- Operational control
- Metrics scraping
- Dashboards
- Alerts
- Infrastructure planning
- Audit and recommendations
- Risk scoring
An infrastructure back office for six kinds of teams
From owners of their own email service to in-house email teams — wherever there are more MTA nodes than one head can hold.
Owners of Protosender-based services
Behind a commercial email service sits infrastructure that needs managing every day.
Central MTA control, warmup, monitoring and export of ready pools straight into Protosender.
Email agencies
Many clients means many domains, IPs and SMTP sources scattered across projects.
A single registry of the whole infrastructure and per-client monitoring from one panel.
Deliverability specialists
It's hard to quickly see why delivery dropped: plenty of data, all in different places.
Queue metrics, errors, latency and AI audit — all diagnostics on one screen.
PMTA / MailerQ integrators
Hand-edited configs across dozens of servers, no versioning, no change control.
Config templates, diff, validation and rollback — infrastructure managed as code.
Micro-ESP teams
Running your own email service demands constant infrastructure work, and the team is small.
MTA-Hub takes over the routine and becomes the service's infrastructure back office.
In-house email teams
Transactional and marketing flows demand visibility, roles and access control.
Monitoring, alerts, role-based operations and AI analysis across the company's whole infrastructure.
MTA-Hub is being built right now — and that's your chance
We are building MTA-Hub right now: the platform you saw above is getting ready to launch. Sales haven't started yet — which means early subscribers have the advantage.
🎁 Before sales open, subscribers of our Telegram channel will get a special price on MTA-Hub. The release announcement and module deep-dives land there too. Subscribe now so you don't miss the discount.