Business · Post 6 of 6
Keep the models. Own the workspace.
Claude for Teams and Enterprise put agents on every desk. The workspace around them, where the artifacts live, which tools agents can call and what gets recorded, should be yours. Pucks, KilterDesktop and managed MCP on rails make it yours.
The models are extraordinary, and a hosted team workspace is the fastest way to put them in front of everyone. Then the work piles up. Plans, reviews, dashboards and decision pages: agents make dozens a week. Connectors reach into the CRM, the ticket queue and the file share. Somebody in risk asks three questions. Where does all of that live? What may an agent do with a connector? Can we prove what it did?
We found out the hard way. Building Paddington with agents, our own artifacts lived in whichever account had made them. Switching accounts meant losing sight of them, so we swept five accounts' worth of pages into a hub we control. That hub is now a product.
Pucks: enterprise versioned artifacts
A puck is an artifact your company owns. Any page an agent makes, from a plan to a design review to a live dashboard, ships with one command, puck ship, and becomes:
- Versioned and immutable. Each version is an image in your own registry. A new version never overwrites an old one; the link to the latest stays stable and every version keeps its own.
- Filed. Folders by project and kind, tags, thumbnails, search, in Puck Hub.
- Provenanced. Which account or agent made it, from which conversation's artifact, and who it was shared with.
- Sovereign. Puck Hub runs on Kilter, in your region or on your cluster. Change chat vendors and the work stays.
KilterDesktop: the agentic desktop, on rails
KilterDesktop is the desktop your people work in with agents: conversations, files, artifacts and the apps their department runs on Kilter, in one place. The difference is underneath. Every consequential action an agent takes for a user goes through Airbender ARC first: enforced on the six-rung ladder from annotate to isolate, and recorded as evidence an auditor can replay. Users get the speed of a consumer AI app. The company gets enterprise-grade controls that hold even when an agent is wrong.
Managed MCP on rails
MCP is how agents reach real systems, and today most connectors run with one person's token and no policy in between. On Kilter, MCP servers are managed services:
- Deployed from the catalog beside the systems they front, in your region, declared in
kilter.yamllike any other service. - Acting as someone. Every call carries the user's or the agent's identity from one identity plane, so every action is attributed.
- Decided before they run. Tool calls pass Airbender ARC rails: allowlists, budgets, approval gates for the actions that need a person, and a block when something looks like injection.
- Recorded. Each call and each decision lands in the evidence ledger.
| A hosted team workspace | Sovereign, on Kilter | |
|---|---|---|
| Artifacts | In the account that made them | Pucks: versioned, filed, in your registry |
| Connectors | Per-user tokens, configured per user | Managed MCP servers, one identity plane |
| Agent actions | Allowed or not, per connector | Decided per call by rails, six rungs |
| Record | The vendor's audit log | Hash-chained evidence you can replay |
| Location | The vendor's regions | Your region, your cluster or ours |
| Models | The vendor's | Any approved model through one gateway, Claude included |
Keep the models
This is not a case against the models. Use the best ones, Claude included, through a gateway you control. Own everything around them: the artifacts, the tools, the rails and the record. That is the part your company will still need when the next model arrives.
Keep the models. Own the workspace.
Next step