Enterprise from about 50,000 emails a month
Your own relay. Your own IP.
On the standard plans, you share a sending IP with other customers. That works well because we guard the reputation of those IPs. Above a certain volume, though, you no longer want that dependency: Enterprise gives you your own relay instance, whose reputation depends on your sending alone.
- your own sending IP
- dedicated contact
- servers in Germany
- cancel monthly
| Hostname | relay-yourcompany.mailbridge.email |
| Sending IP | your own IPv4 address ✓ exclusive |
| DKIM | your own selector, delegated via CNAME |
| Credentials | yours only |
| Location | Nuremberg or Falkenstein |
First do you even need this?
When Enterprise makes sense
There are three reasons to go for it. If none of them applies, a standard plan serves you better, and we will tell you so on the call as well.
-
More than about 50,000 emails a month
Above the largest plan size, your own instance pays for itself, and receiving servers notice the volume anyway. An IP backed by a single, steady sender is easier for receivers to assess than one shared by many small senders.
-
You do not want to share the IP
On a shared IP, the behavior of other senders affects your delivery. We monitor that and step in, but we cannot rule it out. With your own IP, the reputation depends on your sending alone. That is the real difference.
-
Separate streams for separate purposes
Sending invoices and newsletters over the same IP ties together two things that have nothing to do with each other: a promotional mailing with lots of unsubscribes then drags down the delivery of your invoices. With several instances, they run separately.
-
When it is not worth it
Below about 50,000 emails a month, your own IP usually brings less than it costs. A new IP first has to build trust, and that takes regular volume. If you send irregularly or in small amounts, you demonstrably do better on a well-maintained shared IP.
Scope what is included
Four things you do not get with the standard plans
-
One or more dedicated relay instances
Your own instance of our relay software, hosting only your credentials. It has its own hostname, its own DKIM selector and its own configuration. How many instances make sense depends on how many sending streams you want to keep apart.
-
Your own sending IP per instance
Each relay instance sends through exactly one IPv4 address. If only your credentials are on it, it is your IP: its reputation with receivers comes solely from how you send. We handle the warmup, the blocklist monitoring and the follow-up if a receiver does block you.
-
Dedicated contact, four-hour response time
A named person with a direct line and email address who knows your setup. No shared inbox, no ticket system. For requests on business days between 8 a.m. and 5 p.m. (German time), you get a qualified response within four hours. That means the first substantive reply, not the finished fix: some things cannot be solved in four hours, but you will know where things stand.
-
Guided onboarding
We set up the instance, prepare the DNS records for you to copy, double-check them, guide you through switching over your applications and manage the warmup. If you are moving from another provider, we plan the order so that no email gets stuck at any point.
Honestly the limits
What Enterprise is not
These points are here because otherwise you would find them out in day-to-day operation. If any of them is a deal breaker for you, we should know before the quote, not after.
- No automatic failover. If your instance goes down, your sending does not switch to another relay on its own. That is intentional: an automatic switch would send your email through someone else's IP with a reputation you know nothing about. During a longer outage, we move you over manually and let you know beforehand.
- No delivery guarantee. We put the technical foundations in place and monitor them. Whether an individual email lands in the inbox is decided by the receiver, based on content, sending behavior and domain reputation. Nobody who is being honest can promise that.
- No ISO 27001 certificate of our own. The data centers our servers run in are certified. We, as the provider of the service, are not, and we do not pretend to be. If your procurement requires a certificate for the service provider itself and not just for the data center, tell us before the quote. What we do instead, in concrete terms, is listed further down and can be verified.
- No 24/7 on-call support. The committed response time applies on business days from 8 a.m. to 5 p.m. (German time). Outside those hours you can still reach us, but without a commitment.
- No full volume right away. A fresh IP has no history with receivers. The warmup takes several weeks, during which the volume increases step by step. If you switch over on Monday and want to send 100,000 emails on Tuesday, you will be throttled.
- The IP does not belong to you. It is part of our infrastructure. If you cancel, it reverts to us, and the reputation you have built cannot be transferred.
Price what it is based on
Why there is no number here
On the pricing page, every amount is out in the open, and it will stay that way. For Enterprise we cannot name one, because the price depends on three factors that differ from customer to customer. What we can disclose is the math behind it.
-
Number of instances
Every dedicated relay instance costs money to run: its own machine, its own IP, its own monitoring and its own warmup. That is the base amount, and it applies per instance. One instance is the norm; you need several if you want to separate sending streams.
-
Sending volume
On top of that comes the volume-based part, following the same logic as the standard plans: the larger the volume, the lower the price per thousand emails. The tiers of the Bridge plans show the direction it continues in.
-
Level of support
Moving from another provider with many sending systems takes more work than a fresh setup with two applications. We estimate this part after the call and list it separately in the quote, so you can see what is one-time and what is monthly.
-
What stays the same
Monthly terms with no minimum contract period, no setup fee for the standard setup, the cost cap for unusual overage, and all prices excl. VAT. These terms are the same for Enterprise as for every other plan.
Process from the first call to sending
What happens after you get in touch
-
Call
A phone call of about thirty minutes. We ask about volume, sending systems, domains and what is not working today. At the end, we will also tell you if a standard plan is enough.
-
Quote
Within a few business days, with the monthly and one-time parts listed separately. It also states how long setup and warmup will take.
-
Setup
We set up the instance, you get the DNS records to copy and we double-check them. We create your credentials together, one system at a time.
-
Warmup and handover
The volume increases over several weeks. You can follow the progress in the portal, and we reach out proactively if anything stands out. After that it runs, and your contact stays the same.
From the first call to production sending usually takes two to three weeks, followed by another four to six weeks of warmup.
Verifiable operations and security
What actually applies to operations
No badges, just things you can look up in the contract, the documentation or the portal.
- Servers in Germany only, spread across the data centers in Nuremberg and Falkenstein, hosting under a data processing agreement pursuant to Art. 28 GDPR
- No data processing in third countries, not even by subprocessors
- DPA and TOM in the portal: conclude them with your company details after signing in and download them as a PDF signed by us, no paper round trip
- Data centers certified to ISO/IEC 27001:2022, operated by Hetzner Online GmbH. Nuremberg and Falkenstein are named in the certificate; MailBridge itself is not certified
- Plus an unqualified BSI C5 Type 2 attestation (the cloud security standard of Germany's Federal Office for Information Security), audited by an accounting firm under ISAE 3000
- Mail flow does not depend on the portal: if the management interface goes down, the relays keep accepting and delivering
- We store SMTP passwords only as hashes; you see them in plain text exactly once, when they are created
- Strict sender binding: a set of credentials can only send from the domains approved for it
- Every management action is logged, with the time and the person who performed it
- Operated by LOGIN SystemHaus, an IT service provider in Wiesbaden, Germany, since 1991
- Cancel monthly, Enterprise included, with no minimum term
Questions that come up before the call
Frequently asked questions about Enterprise
How long does it take to get a dedicated relay up and running?
The setup itself takes a few days. The warmup takes longer: a new IP has no history with receivers, and if you push full volume through it right away, you get throttled. That is why we increase the volume step by step over several weeks. Your sending is already running during that time, just ramping up.
What happens if my relay goes down?
There is no automatic failover to another relay. That is a deliberate decision: an automatic switch would send your email through someone else's IP with a reputation you know nothing about. During a longer outage, we move your credentials over manually and let you know beforehand. The mail flow itself does not depend on the portal: if the portal goes down, the relays keep accepting and delivering.
Can I switch back to a standard plan later?
Yes. Your credentials then move to a shared relay, and your sender domains and settings stay as they are. Because the DKIM selector changes in the process, one DNS record needs to be updated. We plan the move with you and carry it out outside your sending hours.
What happens to the IP if I cancel?
It reverts to us and goes through a warmup phase before it is assigned again. You do not take it with you: the address belongs to our infrastructure, not to your contract. The reputation you have built therefore cannot be transferred. That is true of every provider that supplies the IP.
Do I get several relays if I send for several brands?
Yes, that is the usual reason for more than one instance. Sending transactional email and newsletters over separate IPs protects the delivery of your invoices from a promotional mailing that drags down the reputation. Each instance has its own IP and its own DKIM selector.
Is MailBridge ISO 27001 certified?
No, and the distinction is important enough to spell out. What is certified are the data centers our servers run in: Hetzner Online GmbH is certified to ISO/IEC 27001:2022, the certificate states that its scope covers all hosting services and the data centers, and both Nuremberg and Falkenstein are named in the certificate annex. It was issued by SOCOTEC Certification Deutschland under number ZN-2025-35 and is valid until September 26, 2028. On top of that comes an unqualified BSI C5 Type 2 attestation, audited by WP Koehler GmbH under ISAE 3000 with an audit report dated November 17, 2025, and a classification as an operator of critical services under Section 8a of the German BSI Act (BSIG). LOGIN SystemHaus GmbH, the provider of MailBridge, does not hold an ISO 27001 certificate of its own. If you need one, tell us before the quote.
Does the cost cap apply to Enterprise too?
Yes. Just like on the standard plans, sending pauses automatically when overage is unusually high, and you release it with one click in the portal. So here, too, a bill cannot run away from you without you noticing.