Can you run an AI agency on n8n? The license and limits

n8n's license lets you build and run workflows for clients on your own instance, but not host it for them or white-label it. Here is what n8n covers, what it leaves out, and when a white-label stack fits.

Lumina7 min read
Thin amber lines branching from a small node into a rounded rectangular frame on a dark charcoal background

You can run an AI agency on n8n, and plenty of agencies do. n8n's own license FAQ says building, running and maintaining workflows on your own instance on behalf of clients is permitted, and that you can charge for the setup and upkeep. What n8n does not give you is the sales layer: a demo a prospect can call, a branded portal, and a way to hand a client something that carries your name. That gap is where the "n8n or a white-label stack" question really lives.

Use n8n for the back-office plumbing it is good at, and watch the license line on hosting. If your pitch is "try the AI receptionist yourself, then sign," n8n alone will not carry the sale.

What does the n8n license let an agency do?

This is the part most agency owners skim, so read it once properly. n8n ships under the Sustainable Use License. The license text says you may use the software "only for your own internal business purposes or for non-commercial or personal use," and that you may distribute it to others only free of charge for non-commercial purposes.

The license FAQ turns that into plain rules for people like us:

  • Allowed: building, running and maintaining workflows on your own n8n instance on behalf of clients.
  • Allowed: charging customers for workflow creation, setup and maintenance.
  • Allowed: installing n8n on a client's own server, as long as you do not also offer hosting.
  • Not allowed: hosting n8n as a service and letting your clients build workflows.
  • Not allowed: white-labeling n8n by removing the branding and offering it as is.

For anything that ships n8n to customers inside a paid product, the FAQ points you to a commercial conversation with n8n's sales team. So the safe pattern is simple. The workflows run on your instance, your client never logs into n8n, and they pay you for the outcome, not for access to the tool. Agencies that bolt a client login onto a shared n8n instance are the ones who should stop and email n8n before they scale.

We are not lawyers, and licenses change. Check the current text before you build a business model on it.

What does n8n cost once clients are on it?

Self-hosting the community edition costs you a server and your time. On n8n's hosted side, the pricing page lists Starter at 20 euros a month billed annually for 2,500 executions, and Pro at 50 euros a month billed annually for 10,000. Business is 667 euros a month billed annually, 40,000 executions, and self-hosted only.

Workflows and users are unlimited on those plans, so the meter is executions, not seats. A client with a lead-routing workflow that fires on every form fill and every missed call will not burn through 10,000 executions in a month. A busy one running a text-back sequence for every inbound call might. Count your executions per client before you promise a flat price.

n8n is cheap. The tool bill is the smallest line in your costs, the same way the per-minute voice rate is. We made that argument for voice in build vs buy for the AI voice stack, and it holds here too.

What n8n does not give you

n8n is a workflow engine. It connects systems and moves data between them, and it does that very well. Here is what you still have to build or buy on top of it before you can sell a local service business anything:

A demo the prospect can touch. A Loom of your own workflow is a recording. A plumber who can call the receptionist, ask about pricing and hear it answer in plumbing language is a different conversation. You can rebuild that in n8n plus a voice provider, but you are now maintaining a public-facing app.

A place for the client to look. After they sign, they want to see status, assets and next steps under your name. n8n has no client portal. People fake it with a shared doc or a Notion page, and it works until the third client.

Branding on every surface. The n8n editor is not something you hand to a client, and under the license you should not be offering it as a branded product anyway.

Intake and handoff. Hours, services, price bands, calendar, who gets the leads. You collect it by email or you build a form, and then you map it by hand into the workflow.

Industry knowledge. A dental office and a roofing company need different language, different objections and different booking rules. Writing that for each trade is real work.

That list is what Lumina Sales packages: a live demo site, a client portal, a fulfillment platform and onboarding help, all under your logo for $49 a month, with builds you order priced at wholesale on a 30-minute call. The platform page lists what each part does.

When n8n is the better pick

Lumina Sales is not a workflow builder, and we are not trying to talk you out of n8n.

If your clients are operations teams who want data moved between a CRM, an accounting tool and a spreadsheet, n8n is the right tool and our stack is the wrong one. That work is invisible plumbing. Nobody needs a demo site for it, and the value is in the integrations you wire.

If you are a developer who enjoys building and you have one or two clients, assembling your own stack is fine. You will learn a lot, and the upkeep stays small at that size.

If you sell mostly through referrals and relationships, you may not need a demo at all.

The stack starts to earn its place when you are selling the same kind of system, an AI receptionist or chatbot, to many local businesses, and the thing that limits you is how fast you can show it and deliver it. The math on what you keep per client is in our margin breakdown.

Can you use both?

Yes, and a lot of agencies should. Use the white-label stack for the front of the sale and the standard fulfillment, then use your own n8n instance for the custom automations a particular client asks for on top. One split that works: the receptionist, chatbot and portal come from the stack, while the odd job of syncing bookings into a client's weird legacy software lives in n8n. If you are also weighing a bigger all-in-one, we compared that in GoHighLevel versus a white-label AI stack.

FAQ

Is n8n free for agencies?

The community edition is free to self-host, but it is licensed for internal business use. Building and running workflows for clients on your own instance is permitted by the FAQ. Hosting n8n so your clients can build their own workflows is not, so read the current license before you design the offer.

Can I white-label n8n and resell it?

The license FAQ says no. It lists white-labeling n8n by removing the branding and offering it as is among the things you cannot do. If you want to ship n8n inside a paid product, n8n points you to its sales team for a commercial license.

Does Lumina Sales replace n8n?

No. Lumina Sales is the demo, portal, fulfillment and onboarding layer for selling AI systems to local businesses. It does not replace a general workflow engine, and you can run both side by side.

Will my client see Lumina branding?

Not on a published demo. The page carries your logo, colors, subdomain and booking link. The one thing always visible is the sandbox notice saying the AI is a demo and bookings in it are simulated.

What is the cheapest way to start?

If you already know n8n, start by selling one narrow workflow to one client from your own instance. If you want to sell AI receptionists to many local businesses, the cheaper route is usually a stack that includes the demo and portal, because those are the pieces that take the longest to build.

Next step

Count what you would have to build before your next demo call: the demo, the portal, the intake form, the branding. If that list is longer than your week, start a workspace, put one prospect's business name into the demo, and send them the link. Keep n8n for the workflows only you can write.