Hyperscaler tenant
The vendor holds the boundary.
Permissions, curated knowledge, and the session live where the model vendor already sits. Switching clients forks the operating layer.
Sovereignty
Untied from the tool.Keep the work.
Agent 365 keeps the record in Microsoft
Permissions, curated knowledge, policies, and sessions stay in your tenant. Neutral. In your tenant.
GitHub
- Read repository Allowed
- Open pull request Approved
- Force-push main Blocked
Jira
- Read issue Allowed
- Create issue Approved
- Delete project Blocked
Linear
- List issues Allowed
- Update status Approved
- Archive team Blocked
Slack
- Read channel Allowed
- Post message Approved
- Invite guest Blocked
tool
Resolve.ai
team
Platform eng
team
On-call
tool
Analyst
user
Maya Chen
tool
SRE bot
team
Security
user
Jordan Lee
tool
Docs agent
Clients connect through Telara
Architecture
Vendor-neutral. Tenant-resident.
The client and the workstream can change. Permissions, curated knowledge, policies, and sessions stay in your tenant — not Agent 365's record, and not a hyperscaler's trust boundary. Onyx indexes; it is not this operating layer.
Not tied to the tool
Workstream and client can change
Claude Code, Cursor, Copilot, local models — same path. Switch clients without forking anything.
MCP
A2A
API
Portable operating layer
Permissions, knowledge, policies, sessions
What you granted, curated, and decided travels with the tenant — not with a vendor.
Permissions
Knowledge
Policies
Sessions
Tenant-resident
Isolated tenant today, customer cloud next
Scope, policy, knowledge, and session stay in your isolated tenant. Customer-cloud deployment is on the roadmap.
Tenant isolation
Customer cloud (roadmap)
Where the runtime sits
A vendor-owned control plane cannot be the neutral record.
Your tenant
The customer holds the runtime.
The same permissions, knowledge, policies, and sessions, whichever client or workstream you bring. Neutral. In your tenant.
Control
Keep the choice. Keep the authority.
Switching a client or a workstream does not create a second copy of permissions, curated knowledge, or sessions.
One permission path
Effective scope is evaluated on every tool call, whichever client asked.
One curated knowledge
What the organisation has curated stays in the tenant — past the client, the model, and the vendor.
One session record
The next client starts from the same record, not a forked chat.
In your IDE via MCP.
Claude Code and Cursor enter the same control path. Permissions, curated knowledge, and the session stay in your tenant.
Same permissions from any connected client
Curated knowledge is not trapped in that vendor
Policies and sessions land in your tenant
# Add to claude_desktop_config.json
{
"mcpServers": {
"telara": {
"url": "api.telara.dev/v1/mcp",
"auth": "your-api-key"
}
}
}