AgentOrg for AI automation agencies
You built the client's automation, it works, and now they want you to run it — which is the moment the licence you have been relying on stops covering you.
Building automation for a client and operating it for them are different things, and most self-hosted tools only license the first. AgentOrg's terms permit the second: you run the work on a client's behalf, you bill them for it, and there is no infrastructure of yours for it to run on.
You
Can you resell n8n to clients?
Most agencies hit this after the build, not before it.
Can you resell n8n to clients?
Partly, and the line falls in an awkward place for agencies. n8n's Sustainable Use License lets you build workflows for a client as a consultant, but it does not let you run n8n for them — hosting it and charging for access, or white-labelling it, each require a paid licence from n8n.
The permitted case is narrow and specific. n8n's documentation lists “providing consulting services related to n8n, for example building workflows, custom features closely connect to n8n, or code that gets executed by n8n” as allowed. It lists “white-labeling n8n and offering it to your customers for money” and “hosting n8n and charging people money to access it” as not.
AgentOrg's terms permit the case that sits between those two. You may operate the service on a client's behalf and charge them for that work, with no separate licence and no negotiation. What they do not permit is white-labelling it or giving clients their own logins.
Sourcesn8n Sustainable Use Licensen8n Help Center: which license do I need?n8n Embed
Which n8n licence does your agency need?
It depends on which of three things you are actually doing. Only the first is free, and it is the one least agencies stop at.
| n8n licence required | |
|---|---|
| Help a client set up their own n8n instance | None |
| Run client workflows on your own instance | Enterprise |
| Embed or white-label n8n in your product | Embed |
The middle row is where most agencies operate. n8n's Help Center is explicit about it: “If you intend to host and manage your clients' workflows and credentials within your own internal n8n instance, an Enterprise license would be required.” Neither Enterprise nor Embed pricing is published — both require a direct commercial agreement with n8n, so the cost of that row is whatever they quote you.
Self-hosting, n8n's paid tiers, and AgentOrg
The comparison that matters for client work is not feature count. It is what you are licensed to do, who runs the thing at 3am, and what it costs before you have a client on it.
| Self-hosted n8n | n8n Enterprise or Embed | AgentOrg | |
|---|---|---|---|
| Licensed to run it for clients | No — consulting only. Hosting it for clients needs a paid licence. | Yes, under the licence you negotiate. | Yes, under the standard terms. No separate agreement. |
| Who runs the infrastructure | You. Server, upgrades, backups, uptime. | n8n, on their cloud. | AgentOrg. Nothing to host. |
| Published price | Free software, plus your hosting and your time. | Not published. Direct commercial agreement. | $49 or $99 a month, listed publicly. |
| Cost to try it on one client | A server and a weekend. | A sales conversation before you can start. | $49, the same day. |
| Approval before an action lands | Build it yourself into each workflow. | Build it yourself into each workflow. | Built in. Every irreversible action waits for a person. |
| Who fixes it when it breaks at 3am | You. | n8n, to the terms of your agreement. | AgentOrg. There is no instance of yours to fail. |
What it costs to run five clients
Plans are metered in credits, not seats or agents. There is no cap on how many agents you create, so an agency runs one agent — or a set of them — per client inside a single account.
- Pro is $49 a month for 10,000 credits. Team is $99 for 50,000.
- A credit is consumed per tool call an agent makes, and a single task usually makes several — the agent finds the right tool, reads how to use it, then acts.
- Across the 35 tasks we have measured, a task cost a median of 4 credits and a mean of 6.9, with a range of 1 to 21. A simple lookup lands at 1–4 credits; a multi-step job that searches for tools and then runs several of them lands at 10–20.
- At the mean, Team's 50,000 credits is roughly 7,200 tasks a month. Split across five clients that is about 1,400 tasks each, at $19.80 per client per month.
- If a client has a heavy month, top-ups are $1 per 1,000 credits — an overrun is priced rather than blocked, and it does not force a plan change.
Those figures come from 35 real tasks in our own account, not from a benchmark. Treat the range as the honest part and the average as indicative: your mix of simple lookups and multi-step jobs will move it. The mechanism — a credit per tool call, several tool calls per task — is what to plan around.
What agencies actually hand over
Three jobs that come up on almost every retainer, each running on an integration you can read about in full.
Run a client's support inbox
An agent reads what came in overnight, drafts the replies that are routine, and leaves them for you to release before the client's customers see anything.
Keep a client's CRM honest
An agent finds records that have gone stale, matches contacts to the right company, and proposes the corrections rather than applying them.
Report to a client without rebuilding it monthly
An agent pulls the numbers from the client's own tools and assembles the report, so a retainer's reporting hour stops being an hour.
What AgentOrg does not do for agencies
Worth knowing before you put a client on it, rather than after. None of the following is on a roadmap promise — it is how the product works today.
- No white-label. Your clients see AgentOrg. There is no custom branding, no custom domain, and no way to present it as your own product.
- Clients get no login. You operate the account; they do not sign in. A client who needs their own workspace and their own users needs their own AgentOrg account, billed separately.
- No data isolation between clients inside one account. Agents in your organisation can reach every tool connected to it. If one client's data cannot sit alongside another's, give that client their own account.
- Credits are pooled, not ring-fenced. A heavy month for one client draws down the same balance as everyone else's.
- Approvals are account-wide. Anyone with approver rights in your account can approve an action on any client's work. There is no per-client approver scope.
AI automation agencies questions, answered
What people ask before putting an AI agent to work — answered straight.
Yes. AgentOrg's terms permit you to operate the service on a client's behalf and to charge that client for the work. This is set out in the “Use on behalf of clients” section of the Terms of Service, so it is a standing permission rather than something you negotiate per engagement.
Ready to automate client work?
Connect your tools, put an agent to work, and approve what matters. Free to start.