What is Manykind
Manykind is an agent platform built on one inversion: a customer’s data stays with the customer. Every customer holds a sovereign data vault, owned by their wallet the way a crypto wallet owns coins, and your agents and workflows work inside it.
You hold none of that data. There is nothing to import, nothing to migrate, and no store of user data of your own to secure.
Two sides and a connection
| Who owns it | What it holds | |
|---|---|---|
| Agent Service | You, the developer | Your agents and workflows, plus the cubbies, widgets, datasets, and members that belong to them. |
| Vault | Your customer: a person or an organization | Their data, their Memory Bank, their connectors to outside systems, their members. |
| Connection | Signed by the vault owner | A scoped, revocable agreement that lets one agent or workflow run on that vault’s data. |
An agent or workflow does nothing with a customer’s data until the vault owner connects it. The connection names which part of the vault it may use, and the owner can withdraw it at any time.
What you ship
- Workflows. A typed graph of steps: triggers, model calls, agents, people, cubby reads and writes, connector actions. Build one in the ROC Workflow Builder or in code. A workflow is an agent, so it publishes, deploys, and connects the same way.
- Agents. A code agent is TypeScript that reacts to events in the vault. An external agent runs on your own infrastructure and joins over A2A.
Both call models the platform serves, keep shared working state in cubbies, file what they learn into the vault’s Memory Bank, and can ship widgets as their UI.
Your own apps sit around them. A web app, a mobile app, or a server job can talk to a vault directly through the Vault SDK to onboard a customer’s data or read results back.
What makes Manykind different
- Your agent is the guest. In a conventional app a user’s data becomes yours the moment they hand it over. Here it never leaves their vault: you get access, not custody.
- Consent is already built. Every vault that connects your agent has a wallet-signed, scoped agreement on record. Revocation is a signature, not a support ticket.
- No lock-in to defend. The data lives in the customer’s vault, not in your app, so they can run your agent beside others and keep their history if they switch. Switch any agent, keep every memory.
- An open standard. Manykind is the first implementation of the Self-Sovereign Context Protocol (SSCP): you build against a specification, not one vendor’s product.
Start building
- How it fits together: the two sides, the connection, and where each part of these docs fits
- Quickstart: build and run a workflow
- Agents: workflows, code agents, and external agents, and the Agent Service that owns them
- Vaults: what your customer owns, and how your apps work with it
Using a coding agent? Point it at our llms.txt: see Build with AI.