Production control plane for agent teams

Connect every agent.
Improve the system.

Observe real work across local coding agents and cloud runtimes. Dharma turns trajectory evidence into evaluations, Failure Atlas findings, and signed remediation your organization can review and roll out.

Outbound-only local relay. No provider keys in the browser. Signed rollout and rollback receipts.

Live operating loop policy active
Local agents Cloud agents A2A handoffs
  1. 01
    ConnectCodex, Claude Code, Agy (preview), SDK or BYOK
  2. 02
    ObserveReduced, signed trajectory evidence
  3. 03
    EvaluateRubrics and Failure Atlas families
  4. 04
    RemediateReviewable GitHub skill changes
  5. 05
    Roll outSigned canary, receipt and rollback
100-trajectory analysis windowsGitHub provenanceTenant-isolated evidence
Trajectory observabilityOrganization-specific rubricsFailure AtlasRemediation supply chain

One control plane, three execution boundaries

Use the agents you already have, or run ours by API.

01

Local agents

Keep execution on the developer machine.

The outbound CLI relay connects workspace-qualified Codex and Claude Code sessions, plus Agy and Hermes (preview, not GA). Provider keys and full local transcripts stay on the device.

Included in trial
02

Your GCP

Use Vertex through workload identity.

Dharma orchestrates a customer-owned project through scoped federation. No service-account JSON key is downloaded or stored by Dharma.

Production launch (preview)
03

Dharma managed

Run isolated ADK agent revisions by API.

Tenant-bound runtime, traces, admission controls, usage settlement, immutable revisions, and signed remediation are operated as one managed environment.

Production launch (preview)

From signup to operational evidence

The setup sequence is built into the workspace.

Customers authorize each external boundary themselves. Dharma automates the organization shell, trial tokens, private control repository, policies, and next-step commands around those approvals.

  1. 01
    Create the company

    Sign in, name the organization, and receive a 50,000-token launch trial.

  2. 02
    Authorize the boundary

    Install the GitHub App, then choose local CLI, or a preview option: GCP WIF BYOK or managed ADK.

  3. 03
    Connect the first agent

    Run the generated CLI command or create an agent through the scoped organization API.

  4. 04
    Observe real work

    Signed reduced evidence is attached to the correct workspace, provider, bundle, and trace.

  5. 05
    Close the loop

    Evaluation findings become a reviewable remediation PR, held-out proof, signed rollout, and rollback receipt.

Start with the boundary you need

A real local trial, then one production token pool.

Local-agent evaluation loop

Connect the team before moving workloads.

  • Codex and Claude Code workspace onboarding, plus Agy and Hermes (preview, not GA)
  • Encrypted local vault and reduced evidence sync
  • Evaluation, Failure Atlas, and GitHub remediation workflow
  • Managed ADK and GCP BYOK stay upgrade-gated

No credit card required for the launch trial.

Customer-scoped authorityEvery task, trace, repository, usage event, and rollout is organization-bound.
Review before autonomyThe first remediation requires organization approval; later low-risk versions may follow the approved policy.
No cloud keys in Dharma HQCloud BYOK uses workload identity; local provider credentials remain local.