Keep every client apart, metered apart, delivered as yours.
Your clients want an agent and they want you to run it, which means one build per client unless something keeps them apart for you. Each client gets a workspace inside your organization: their connections, their knowledge, their limits, their own line on the month.
There is no Levain login for a client to find.
Keep one client's data from reaching another.
Connections, knowledge and memory live in that client's workspace, and an agent can only read the one it runs in.
Build it once, bill it many times.
Write it with the SDK, or by describing it to Claude Code, then publish it to every client from your registry.
Hand a client the keys and walk away.
A client's agents, records and data stay in their workspace, whole and exportable.
Open a workspace for a new client, not a rebuild.
From your first client to your fiftieth, the same four steps.
Build the agent once.
In Python with the SDK, or by describing it to Claude Code. Publish it as a version in your registry.
Give each client a workspace.
One call, or one click in the console. Sandbox, knowledge, memory and limits come with it.
Hand over the client's tools.
Their CRM, their helpdesk, their data. The credentials stay in that client's workspace, and the model never sees them.
Publish.
Every client workspace that adopted the agent follows the new version. Read what each client used; suspend the ones that leave.
The calls themselves, with every field. Read the docs
Instead of
a white-label kit for chat widgets, and a separate tool for everything that isn't a chat widget.
Worked example
Run one definition, keep a record per client.
A support agent runs for every client on your roster. In each client's workspace it reads that client's helpdesk, drafts the reply, and waits for an approval before it sends: one definition, different connections, a record that belongs to one client only.
This is a worked example, not a customer story.
Questions agencies ask first.
Do my clients see Levain?
Not for agents delivered through your product or API: workspaces are headless, so there is no Levain login for a client to find and nothing to remove. In Slack the agent shows the Levain app.
What does a client cost me?
Credits are pooled at your organization and every workspace reports its month-to-date usage. You see and cap what each client spends.
Can I bill my clients through Levain?
Not yet. Usage is reported per client, so you read what each one used and bill them yourself; billing rails are on the roadmap.
What happens when a client leaves?
Suspend the workspace with one call. Their data stays readable to you; deletion is on request today.
Open your first client's workspace today.
A free organization comes with a workspace to build in. Add your first client when the agent is ready.