Hosting Providers
On a shared server, one customer’s sending decides delivery for everyone on that IP. By inspecting each customer separately, MXGate protects your server’s IP reputation: the problematic one stops while everyone else’s mail keeps flowing.
- Setup
- Once at server level; domains recognised automatically
- Isolation
- Separate inspection per account and per domain
- Customer portal
- Per-domain access to their own records
- Branding
- White-label presentation available
- Scale
- Starter 2 servers · Business and above unlimited
On the hosting side, email always bleeds from the same four places
“My mail isn’t going out” tickets
A large share of your support team’s time goes to tickets that are really delivery problems. Finding the reason means digging into server logs every time.
IP reputation dropping and blocklists
One compromised account is enough to drag down the server’s IP reputation. Getting off a blocklist takes days, and every customer on that server is affected meanwhile.
The neighbour effect
The customer who causes the problem and the customer who pays for it are not the same person. This is the hardest thing to explain, and it usually ends in a justified complaint.
Quiet churn
A customer whose mail keeps landing in spam does not complain; they quietly move to another provider. By the time you notice, you can no longer ask why.
One gateway, separate inspection per customer
The connection is made once at server level and the domains on that server are recognised automatically. You do not define customers one by one, yet each appears as a separate record with its own quota and reports.
Who sees what, and who can do what?
In a multi-tenant setup the critical question is separation of access. Opening their own records to the customer is the fastest way to cut your support load.
| Capability | You (hosting admin) | Your customer (domain owner) |
|---|---|---|
| Traffic visibility | All servers and domains | Their own domain only |
| Quarantine | View and release for any domain | Release their own messages |
| Delivery and rejection logs | All of them, with reasons | Their own records, with reasons |
| Quota settings | Change per account and per domain | View only |
| Allow and block lists | Server-wide rules | Rules for their own domain |
| Branding | Interface and notifications carry your brand | They see your brand |
The capabilities opened to customers are set per domain, and you can choose to open none at all.
Clean traffic passes, the problem traffic does not
A plan that follows your server count
The number of domains is not capped; plans differ by server count and monthly volume.
Questions from hosting providers
Do I have to define each of my customers separately?
No. The connection is made once at server level and domains are recognised automatically. In the panel each domain appears separately with its own records, quota and reports; you do not define them one by one.
If one customer sends spam, are the others affected?
No. Sending is evaluated per account and per domain; the problematic one is stopped while the others keep flowing. This removes the shared risk that comes from using a single IP on a shared server.
Can my customers see their own records?
Yes. A per-domain customer portal can be provided: the customer sees only their own traffic, quarantine and delivery records. This lets customers resolve a large share of the “my mail did not arrive” tickets themselves.
How many servers can I connect?
The Starter plan covers two servers; Business and Enterprise allow unlimited servers. Setup does not repeat as you grow — each new server is added with the same configuration.
Can I offer it under my own brand?
Yes. The customer-facing interface and notifications can carry your own brand. You can position the service as a feature inside your own plans or sell it as a separate tier.