Can A Consultant Build n8n Workflows For Clients Without A Paid License?
Usually yes. n8n's Sustainable Use License explicitly permits consulting and automation services: a consultant can build, run and maintain workflows for clients and charge for that work, on their own instance or on the client's server. The line is access. Once clients can open the editor or build their own workflows, you need a commercial license.
What does the free license allow?
n8n's license FAQ lists these as permitted:
- Building and running client workflows on your own instance, as long as clients only receive the outputs.
- Serving many clients from one instance. n8n says the deciding factor is client access, not client count or revenue.
- Installing and maintaining n8n on a client's own server, provided you do not also host it for them.
- Charging for workflow building, setup, maintenance, training and consultancy. The fee is for the service, never for access to n8n.
When do I need a paid license?
- Clients can log in to your n8n instance or change workflow logic.
- Your product lets customers build or configure their own automations on n8n, even through your own interface.
- You host n8n as a service, white-label it, or use features that ask for a license key.
n8n's support guidance sends anything in between to license@n8n.io before launch.
What do I do about it this week?
- Write down who can reach each n8n instance you run, client by client.
- Remove any client logins to the editor, or price an Enterprise license for that setup.
- Check that your invoices bill for the service, not for n8n access.
- Email license@n8n.io about anything that still feels grey, and keep the reply.
What should I avoid?
- Do not give a client "just a quick look" at the editor. That one login changes the licensing position.
- Do not rely on forum answers for licensing. They contradict each other, and only n8n's own pages and replies count.
Related questions
Does it matter how many clients share one instance?
No. n8n says there is no limit on clients per instance. Only client access changes the answer.
Keep reading
- Why did my n8n workflow stop without an error? covers the production side once client workflows are running.
We build and run client n8n setups inside these rules as part of workflow automation and system integration work.