Skip to content
DesclesDesign partners

Manage, govern and equip your agents

One platform for
your team’s agents.

Give every agent a virtual key, the right permissions and a budget. Share company context and distill repeated work into reviewed workflows. All on your infrastructure.

Explore the platform Explore the edge on GitHub

Works with Claude Code, Codex, Hermes and your own agents.

One agent, set up for the jobIllustrative example

Customer support

Owned by the support team

Active
Virtual key
•••• •••• 7c2aIts own identity. Provider secrets stay on the edge.
Governance
Refunds require approvalTool access: CRM, support and billing
Daily budget
$8.40 / $25 used
Org context
Customer, billing and support factsFiltered to this agent’s clearance
Workflows
Refund triage ReviewedDistilled from agent runs

Try revoking this agent’s key.

Fictional agent and usage. Simplified presentation; no live credentials.

The team’s agent platform

From their first key
to your next shared workflow.

Issue keys, define policy and budgets, and give agents context and reviewed procedures through the same edge.

Virtual keys & delegation

Issue a key per agent. Delegate access from admins to members to their agents, set expiry and revoke mediated access. Company provider and tool secrets stay on the edge.

Governance & approvals

Define which tools each agent can use, hold selected actions for a person’s approval and keep a record of policy decisions and who approved them.

Budget control

Set daily dollar or token caps per agent. The edge checks budgets on each request and blocks the next call once the cap is reached.

Organization context

Sync CRM, billing, support and code into cited facts. Share them across agents according to source labels and each agent’s clearance.

Workflow distillation

Find repeated procedures in agent runs. A person reviews the draft, then publishes it as a skill agents can follow or a workflow that runs the steps without a model.

Organization context · measured result

69–76% fewer tokens.
The same correct answers.

In one test, an agent answered from organization context instead of querying CRM, billing and support separately. Both approaches answered all 10 questions correctly.

Read the method and evidence
Tokens per question Lower is better
Account historyDirect tool callsDescles context
6 months7,5022,29169% fewer
24 months10,5762,56476% fewer

deepseek-flash · 10 accounts · synthetic data · current-fact questions. This measures one model and workload. Adding context alongside full tool access used more tokens; savings came from using context in place of those lookups.

Get started

Try the edge.
Or bring us a team workflow.

Standalone · free

Run the open-source edge.

Start with virtual keys, model and MCP routing, per-agent budgets, policy, approvals and local records. You supply the infrastructure and provider keys.

Run the edge
go install github.com/chiatzenw-cur/descles/cmd/descles@latest
descles edge init --dir acme-edge --providers anthropic
descles edge up --dir acme-edge

Elastic License 2.0. descles.internal stands for your edge’s address. Agents use Descles keys; your provider bills model usage separately.

Follow the setup guide

Team · design partner pilots

Manage agents across your team.

Add team identities, delegated access, shared policy, organization context and workflow distillation. We’ll help set up one real workflow on your infrastructure and measure the results.

Start your design-partner application.

Checking your session. You can also open sign-up directly.

Open sign-up →Sign in →

Setup docs · Self-host · Get help

No card. Nothing to connect before we talk. Prefer email? Write to the founder.

A few practical questions

Before you connect.

Built by Chiatzen Wang.
About Descles outreach@descles.com

What is available today?

The standalone edge is free and open source under Elastic License 2.0: virtual keys, model and MCP routing, budgets, tool policy, approvals and records. The Team control plane adds team identities and delegation, organization context and reviewed skills and workflows. It is the paid product, available through design-partner pilots. All run in your network. Read the current limits.

Does company data leave our network?

Descles does not receive your deployment’s prompts, credentials, context or usage metadata. Model calls go to the provider you configure; tool calls go to the systems you connect. The Team product checks an offline signed license and does not call home. Clerk and Vercel process account and site data on descles.com. Read the data flows.

Which actions can Descles actually control?

Model and MCP tool calls mediated by the edge are covered. Claude Code and Hermes hooks also check shell and file actions before they run; Codex has no equivalent hook. Direct upstream access and actions outside the gateway are outside this boundary. Shell rules are guardrails, not a sandbox. See integration limits.

How are skills different from context?

Context gives agents facts about your company. A skill gives them a reviewed procedure to follow. Descles mines repeated procedures from agent runs, and a person reviews them before use. A separate 10-ticket illustration used 76% fewer tokens with a skill; it is a demo on one model, not a general benchmark. Watch the example and read the results.