n8n Embed/OEM: Embedding n8n into your own product

n8n Embed, also known as the n8n OEM option, allows software vendors and agencies to embed the visual workflow editor of n8n directly into their own product interface, so that customers can build automations without leaving the application. Licensing is not based on seats, but on an annually committed execution volume (executions), which is pooled across all end customers and billed under a separate OEM agreement. A complete rebranding of the interface is not intended, the n8n brand remains visible in the embedded editor. As of: July 2026.

What the OEM embedding concretely delivers

According to the n8n OEM page the offering includes the visual workflow canvas for dragging, dropping and connecting steps, more than 500 pre-built integrations as well as code and AI nodes for JavaScript, Python and AI agents. In addition there are enterprise features such as role-based access control (RBAC), single sign-on, audit logging, API key scoping and credential management. For operations, n8n provides observability through execution history, real-time alerts, log streaming and usage dashboards. By default, the instance runs self-hosted in the provider's own infrastructure, not at n8n itself.

Licensing model: execution volume instead of seats

Instead of classic user licenses, n8n OEM bills based on executions. Providers commit to an annual volume of workflow executions across all their end customers and are billed against this quota. n8n does not publish a public price list for OEM, the specific terms are negotiated individually in the OEM agreement with n8n sales, the contact channel according to the documentation is license@n8n.io. Anyone who needs solid figures for their own calculation cannot avoid this direct conversation with n8n.

Technical prerequisites for the embedding

According to the n8n prerequisites for OEM deployments the infrastructure requirements are manageable: at least about 10 CPU cycles with scaling as needed, 320 MB to 2 GB of memory depending on workflow complexity, and 512 MB to 4 GB of SSD storage for the database, either SQLite or PostgreSQL. n8n recommends a dedicated database per instance, persistent volumes for containerized operation, IP allowlists, regular backups as well as a separate container setup for nightly backups. Operation is possible on any public or private cloud, n8n itself states that it is not particularly CPU-intensive.

Authentication via iframe SSO and token exchange

If end customers are to get direct access to the embedded editor, according to the documentation on token exchange n8n relies on OAuth 2.0 token exchange, an enterprise feature that is enabled via the environment variable N8N_ENV_FEAT_TOKEN_EXCHANGE and requires an instance delivered over HTTPS. The provider's own backend signs short-lived JWTs (valid for a maximum of 60 seconds) with a private key, n8n verifies them with the matching public key; RSA, EC and EdDSA methods are supported. The tokens must contain required fields such as subject, issuer, audience, timestamps and a one-time token ID, and for newly created users additionally an email address for automatic provisioning. The same mechanism can also be used to implement delegated API access, in which the backend makes calls to n8n on behalf of an end user.

OEM embedding or simple background automation

Not every integration of n8n needs an OEM agreement. According to n8n documentation, the OEM variant is specifically intended for cases in which end users are meant to see and operate the workflow editor themselves. If the automation instead runs invisibly in the background, for example via webhooks or API calls, without anyone outside the provider's own team seeing the editor, a regular n8n operation without a separate OEM agreement is sufficient. NordFlux helps assess which of the two variants is more sensible technically and economically for a specific product, more on the basics under n8n automation.

Frequently asked questions about n8n Embed/OEM

What does an n8n OEM license cost?

n8n does not state a public price list for OEM. Billing is based on an annually committed execution volume, which is individually set in the OEM agreement with n8n sales, contact is made via license@n8n.io.

Can I offer n8n completely under my own brand?

No. According to n8n documentation, the n8n brand remains visible in the embedded editor. A complete white-labeling of the interface is not intended in the OEM model, anyone who needs that as a hard requirement, for them OEM is not the right solution according to n8n.

Do I need an OEM agreement for every n8n automation running in the background?

No. If workflows run invisibly in the background and end customers are only addressed via webhooks or an API, without seeing the editor itself, a regular operation without a separate OEM agreement is sufficient according to n8n.

What technical preparation is needed for the embedding?

At least a server with a few CPU cores, 320 MB to 2 GB of memory, SQLite or PostgreSQL as the database, as well as an instance delivered over HTTPS. For direct editor access, a token exchange implementation with an asymmetric key pair is additionally needed on an enterprise license basis.