White-label email infrastructure your customers see as yours.

White-label email infrastructure lets you sell email sending as your own product while another operator runs the engine behind it: your customers see your brand on the dashboard, the sending domains and the support, while the mail-transfer agents, IP reputation, authentication and deliverability work stay out of sight. It is how an agency, hosting company, SaaS platform or consultant offers a credible sending service without spending two years and a deliverability hire building one. Argus Root provides that engine from infrastructure inside the European Union, and stays out of your customer relationship entirely.

Building your own gives the most control and the highest long-run margin, once you have absorbed the cost of servers, IP space, mail-transfer-agent licensing and the deliverability engineer who keeps it all reputable. Reselling a marketing SaaS is quick, but the brand stays largely theirs, dedicated IPs are uncommon, and your margin is whatever they leave on the table. White-labelling the infrastructure sits between the two on purpose: the speed of reselling with much of the control of building, your brand on everything the customer touches, and the reputation work handled by people who do it for a living.

The model fits anyone whose clients need to send email but whose own product is something else. Agencies fold a deliverable sending service into a retainer rather than pushing clients to a third-party tool that dilutes the relationship. Hosting companies and managed service providers add email sending to a catalogue that already carries domains and servers. SaaS platforms that need to send on behalf of their users get production-grade infrastructure without diverting engineers onto mail-transfer-agent tuning. Consultants give their advice somewhere to land, offering the sending setup they would otherwise only recommend.

The arrangement itself is straightforward. We provision the infrastructure and configure it under your brand, including the sending domains, the dashboard theming and the support addresses your clients will see. You set your own pricing above our wholesale rate and keep the difference, and you own the contract and the relationship with the end customer. We operate the engine, handle the deliverability work and stay invisible, surfacing to your client only as the brand you have put on the outside. When a client grows from a single dedicated IP to a clustered deployment with multiple pools, the underlying setup scales without the customer needing to know anything changed.

Because the reputation of each sender is isolated, one client's behaviour does not put another at risk, which is the failure mode of cheap shared platforms that rotate clients across the same addresses. Your customers are accounted for individually, and so is their standing with the mailbox providers.

We do not run a white-label engine as a side product; we run sending infrastructure under several brands of our own, which is the most direct evidence that we can run it under yours. The mail-transfer agents, the IP pools and the deliverability practice that would power your service already power more than one front door, and we manage them with our own tooling rather than a panel we resell. When you white-label with us, you are renting an engine that has to perform every day for businesses we own, not a demo built to win your contract.

-- one dedicated source IP + pool per white-label tenant
kumo.on('init', function()
  kumo.define_egress_source {
    name = 'tenant-acme-1', source_address = '203.0.113.41',
  }
  kumo.define_egress_pool { name = 'acme', entries = { { name = 'tenant-acme-1' } } }
end)

-- warm slowly per destination; raise the rate as reputation builds
kumo.on('get_egress_path_config', function(domain, source, site)
  return kumo.make_egress_path {
    connection_limit = 4,
    max_message_rate = '90/h',
    enable_tls       = 'Opportunistic',
  }
end)

We are equally clear about the lane we operate in. This is infrastructure for legitimate, permission-based sending: marketing to people who opted in, transactional mail, lifecycle messages. It is not a home for purchased lists, nor for sending built to evade the rules, and it runs on properly licensed software rather than a cracked mail-transfer agent. That discipline is what keeps the IP ranges reputable for every client on them, which is the same reason the 2026 market has split between cheap operators who rotate clients across shared addresses and enterprise vendors whose quote-only pricing starts in the thousands a year. We sit between the two deliberately: real infrastructure, transparent wholesale pricing, and an engineer rather than a script behind the ticket.

The infrastructure is the visible part, but the value of a white-label partner is the ongoing reputation work that keeps mail landing. A dedicated IP is worthless cold; it has to be warmed over weeks so the mailbox providers see a sender that grows the way a real business does rather than one that appears overnight at full volume and gets flagged within days. Once warm, the standing of each sender is watched against the published thresholds, with complaint trends and engagement signals read before they tip a domain into trouble.

When a problem does appear, a sudden complaint spike, a blacklist entry, an authentication misalignment introduced by a change at the client's end, the work is to diagnose and resolve it quickly rather than discover it through bounced mail and an unhappy customer. This is the part a reseller of a SaaS cannot offer and a part-time effort cannot sustain, and it is the reason a white-label arrangement is worth more than the sum of its servers. The infrastructure is what your client sees; the deliverability practice is what they are paying for. The detail of how we run that practice for direct clients sits with our email infrastructure and deliverability work, and the same discipline carries through to the senders behind your brand.

One detail catches many senders out: the spam-complaint rate the mailbox providers hold you to is measured across all of your sending rather than per platform. A business sending marketing through one tool and transactional mail through another is judged on the combined figure against the same threshold, so a problem in one stream drags down the other. Running your clients on infrastructure we watch as a whole keeps that picture in one place, with the Postmaster signals and complaint trends read against the line before either stream drifts toward it.

Because your brand sits on the outside, your customers come to you first, and the support model is built to keep you in front. You hold the customer-facing conversation; we stand behind you with the engineering, reachable as your back line rather than as a separate vendor your client ever meets. When a deliverability question needs an operator, it reaches one of ours, and the answer comes back to you to relay in your own voice and on your own brand.

Accountability divides along the same line as the work. We answer for the infrastructure, the IP reputation and the deliverability engineering; you and your client answer for consent, list quality and the content being sent. Neither side can carry the other's half, and a white-label partner who claims to own all of it is one to be wary of. The arrangement holds because each party owns the part it genuinely controls, with a clear escalation path for the moments where the two meet.