Four ways to ship agents to your customers. Where each one stops.
Building it yourself, Claude Managed Agents, an n8n embed, a white-label kit. Each is the right answer for some brief, and one of them beats us on billing today. Here are the five rows that decide it.
Five rows, and the one that decides it.
Everything here does something well. Where they diverge is whether your customer is a unit the platform understands, or a boundary you assemble and keep in step yourself.
| What is compared | Build it yourself | Claude Managed Agents | n8n embed | White-label kits | Levain |
|---|---|---|---|---|---|
| A workspace per customer |
Partly.
A namespace in each of five services, kept in step by code you own. |
No.
No boundary per customer; you build one around the agent. |
Partly.
A canvas per customer, holding the workflows they build on it. |
Partly.
An account per client, holding a chat agent and its knowledge. |
Yes.
One call opens it, holding their connections, knowledge, memory, limits and record. |
| Models |
Yes.
Any provider you like. The routing between them is yours to write. |
Partly.
Claude models. |
Partly.
Model nodes your customers wire up themselves. |
Partly.
The kit's own roster, published by each vendor. |
Yes.
Anthropic, OpenAI, Google, Meta, Mistral and others in one setting, or your own keys. |
| One API and console, scoped per customer |
No.
Five consoles, none of them scoped to one of your customers. |
Partly.
An API. No console of its own. |
Partly.
n8n's workflow editor, hosted inside your product. |
Partly.
The kit's console, around a branded chat agent. |
Yes.
One organization API and one console, plus Slack and MCP. |
| Spend read back per customer |
No.
Five invoices; attributing a run to a customer is a job you write. |
No.
One account's usage; splitting it per customer is a job you write. |
No.
Executions counted against your embed licence. |
Yes.
Client wallets and billing rails that work today: a client tops up and the kit invoices them. |
Partly.
Month-to-date spend per workspace, over the API. Billing your customer through Levain is on the roadmap. |
| Your brand, all the way to the customer |
Yes.
Yours, as long as no vendor's surface reaches your customer. |
Yes.
Yours; the runtime never faces your customer. |
Partly.
n8n's branding stays visible in the editor. |
Yes.
Yours, applied to the kit's surface. |
Yes.
Yours. Your customers never need a Levain account. |
in the product
partly, or by code you write
not this
Positions as of September 2026.
In fairness
What each one is genuinely better at.
A comparison where the other column never wins is not a comparison. Here is the brief each alternative should get.
Build it yourself
Assembling it yourself wins on control. You pick every part on its merits, replace any one of them the week it stops earning its keep, and no platform sits between you and your customers' data.
What no vendor sells is the customer as a unit: one boundary with all five inside it, opened in a call and suspended in another. That is the code still on your roadmap a year from now.
Claude Managed Agents
If Claude is the only model you intend to ship, this is the shorter path: the loop is maintained by the people who make the model, and there is no third party between you and it.
What it leaves you is the customer. One account's usage, no boundary per customer, no console.
n8n embed
Where your customers want to build the automation themselves, n8n is the right answer and nothing here replaces it. A canvas they own beats an agent they cannot change.
Levain is for the other case: you wrote the agent, you know the job better than they do, and it should arrive working.
White-label kits
For a chat-shaped brief a kit is the better tool, and its client billing rails work today: the client tops up a wallet and the kit invoices them. Ours are on the roadmap.
Most of what an agency is paid for is not a chat window. Levain runs any agent you write, on their help desk, their CRM, their data.
What the workspace holds, mechanism by mechanism. The platform
How customers are kept apart, and who touches the data. Trust
What a workspace costs and how credits pool. Pricing
Give every customer a workspace.
A free organization comes with a workspace to build in. Add your first customer when the agent is ready.