OEMLet your customers build workflows inside your product.

OEM lets you embed the n8n workflow editor inside your product so your end customers can build and edit their own workflows from your UI. You get the n8n canvas, 500+ integrations, and the execution engine as a foundation you ship as part of your product. n8n branding remains visible in the editor.

It's a separate offering from our Enterprise plan, with its own commercial terms, dedicated sales team, and platinum support.

Two different things.

Backend use case is when you use n8n as an internal engine to power features in your product. Your end customers never see n8n. They trigger workflows through your UI and consume the output. This runs on a regular Enterprise license.
OEM is when you expose the n8n canvas itself to your end customers, embedded in your product, so they can build and edit workflows. n8n branding is visible in the editor. This requires the OEM offering.

Quick test: if your end users only trigger and consume workflows you built, you want backend. If your end users create and edit their own workflows, you want OEM.

No. n8n branding stays visible in the editor. You can embed the canvas inside your product and your end customers can build workflows there, but they will see it as n8n, not as a fully rebranded experience.

If full white-labeling is a hard requirement for your product, OEM isn't the right fit.

With OEM, your end customers can create, edit, run, and manage their own workflows from inside your product. They get the full canvas, the node library, and the execution engine. The editor stays branded as n8n, so your end customers will see and recognize it as n8n.

If you only want them to trigger workflows you've pre-built (without editing), that's a backend use case, not OEM.

OEM runs on execution-based pricing. You commit to a yearly volume of executions across all your end customers, and you're billed against that commit.

Every workflow run counts as one execution, whether triggered by your system, by an end customer, or on a schedule. Executions are pooled across all your end customers under a single contract, so you don't have to track per-tenant usage for billing.

Yes. You can build custom nodes for integrations or actions specific to your product, and ship them as part of your OEM deployment. Custom nodes run alongside the standard n8n node library and are available to your end customers in the canvas.