“White-label” gets applied loosely to n8n hosting offers, and the gap between what it implies and what a given provider actually delivers is worth checking carefully before you promise it to a client.
What “white-label” should actually mean
At minimum, a genuinely white-labeled setup should let you present the product as your own, not a visibly third-party tool with your logo pasted on top. In practice, that breaks down into a few separable capabilities:
- Custom domain per client — the instance runs at
automations.clientdomain.com, not a shared provider subdomain. - Rebranded interface — the n8n editor itself (or the parts your clients ever see) carries your branding, not “n8n” visibly in the chrome.
- Rebranded client communications — status pages, billing, and support touchpoints under your name, not the underlying host’s.
- No visible attribution to the infrastructure provider anywhere a client would see it.
Most providers that advertise “white-label” deliver the first item and imply the rest. It’s worth asking specifically which of these four you’re actually getting, because they’re not the same commitment.
Custom domain is not the same as white-label
A dedicated custom domain per client — which is a genuinely useful, commonly available feature — solves the “where does this run” question but not the “whose product is this” question. If a client (or their technical staff) opens the workflow editor and it’s unmistakably n8n’s own interface, the domain alone doesn’t create the impression of a proprietary tool.
Questions worth asking a provider before you promise this to a client
- Is the editor UI itself rebrandable, or just the URL?
- Does your billing and support communication carry your name, or the host’s?
- Is this live today, or “on the roadmap”? — a fair number of hosts (including us, currently) offer real custom domains per instance while full interface white-labeling is still ahead. That’s a legitimate stage to be at; the problem is only when it’s marketed as already shipped.
Where honesty matters more than the feature itself
If you’re an agency reselling this to clients, overselling white-label capability is the kind of thing that surfaces at the worst moment — a client’s technical hire notices the editor says “n8n” somewhere, or asks why the status page points to a different company’s domain. Being precise with your own clients about what’s rebranded and what isn’t costs you nothing and avoids that conversation entirely.
Where we stand on this, plainly
Every instance we host runs on the client’s own custom domain today. Full interface-level white-label rebranding is genuinely on our roadmap, not shipped yet — we’d rather say that plainly than have an agency discover the gap from a client. If that full rebrand is the deciding factor for how you sell to your own clients, it’s worth factoring into your timeline; if per-client domains and genuine per-client isolation cover what you need today, that part is already in place. See how agency pricing and instance isolation work for the rest of the picture.