Ship one agent into every account's own stack.
Every account you sell to runs a different stack, so every agent feature turns into an integration project per account. Levain gives each account its own workspace, so you write the agent once.
The agent is the part you write.
The sandbox, the credentials, the memory and the record already exist, one set per account.
Your customers never see Levain.
Workspaces are headless. Your product, your interface, your name.
One version reaches every account at once.
What you learn from one account's agent ships to all of them as a version you approve.
Add an account in four steps, not a project.
The same four whether it's your first account or your thousandth. No sandbox vendor, integrations vendor, memory API, vector store or metering spreadsheet, stitched together by the engineers who were supposed to build the feature.
Write the agent once.
Python with the SDK, or any language through the API. Publish it as a version in your registry.
Open a workspace per account.
Sandbox, knowledge, memory and limits come with it. Nothing to assemble.
Hand over the account's tools.
Their CRM, their helpdesk, their data. The credentials stay in their workspace, and the model never sees them.
Publish.
Every account that adopted the agent follows the new version. Read what each one used; suspend the ones that leave.
The calls themselves, with every field. Read the docs
Worked example
Answer what the agent did for an account, months later.
A renewal watcher inside a revenue product reads acme-corp's own HubSpot, drafts an outreach note for every deal closing this quarter, and waits for approval before it writes anything back. The record keeps the tool calls, the approval and who gave it, and what the run cost. Export it as a printable page under your name, not ours.
Frequently asked questions.
Can an account connect its own tools?
Two ways. Push the credentials an account has already authorized to its workspace through the API. Or mint a connect link through the organization API and put it behind a button in your product: the account authorizes the provider directly, with no Levain login, and the credential lands in its workspace. Either way, every tool call from then on uses that account's access.
Can I roll a new version to one account first?
Not today. Publishing a version rolls it out to every workspace that adopted the agent, and staged rollout is on the roadmap.
Do my customers need a Levain account?
No. Workspaces are headless, so your product talks to them through the API and your customers see your product.
How is one account kept apart from another?
Each account has a workspace with its own sandbox, credentials, knowledge base and memory, and an agent can only read the workspace it runs in. Every run starts in a fresh machine that belongs to that workspace.
What happens when an account leaves?
Suspend the workspace with one call. Their data stays readable to you; deletion is on request today.
Open your first account's workspace today.
A free organization comes with a workspace to build in. Add your first customer when the agent is ready.