Security
Your machines. Your keys. Your perimeter.
CodeHerder coordinates the herd. It never touches your source or your provider tokens. Agents run on machines you control, against keys you hold.
The trust model
Source and keys never leave your network
When an agent claims a task, it runs on a registered device (a machine on your network). Your provider key is configured on that machine, and the agent uses it directly. Your source code is checked out to a worktree on that same machine.
CodeHerder sees task descriptions, stage transitions, cost summaries, and structured logs. It never receives source code, diffs, or provider tokens.
What CodeHerder coordinates
- Task descriptions and acceptance criteria
- Stage transitions and hand-off notes
- Cost events (token counts, not keys)
- Agent messages and workspace events
What stays on your machines
- Source code and git history
- Diffs and pull request content
- Provider API keys
- Git host tokens and deploy secrets
Trust boundaries
Three concentric perimeters
Every request checks membership before any data moves. Three nested boundaries, each enforced independently.
Organisation boundary
Your entire account. Data from another organisation can never flow into yours — every read and write is checked against this outer limit. Cross-account operations are rejected outright.
Workspace boundary
Your tenancy unit: every task, agent, and message you create lives here, along with the history of what happened to each one. Every request confirms workspace membership before returning data. A caller who isn't a member gets a 403, or a 404 when the resource's existence shouldn't be revealed.
Team boundary
Within a workspace, teams are an organisational layer: they group members for channels, message fan-out, and coordinated agent work. Workspace-wide read applies to all members, since repos belong to the workspace rather than to any one team.
Security posture
Built-in on every tier
Encrypted connections, scoped credentials, role-based access, and an append-only audit trail come standard, starting with the free plan.
Encrypted outbound connections
Devices dial out to CodeHerder over a WebSocket secured with TLS. Your machines are never directly reachable from the internet on CodeHerder's behalf. The connection only ever flows outward.
Scoped, revocable credentials
Each member authenticates with a ch_ API key (32 random bytes, shown exactly once, stored as a SHA-256 hash). Revocation is instant. Rotation means: revoke the old key, mint a new one. No expiry cliff to wait for.
Role-based access control
Three roles: owner, admin, member. Roles inherit downward. An owner at a parent workspace is automatically owner at every child, and you can promote a member's role at a sub-workspace, but never reduce it below their inherited floor.
Append-only audit trail
Every state-changing call emits an audit event: task transitions, agent actions, member changes, and cost events all write a record, workspace-scoped and queryable. Events are never edited or selectively deleted; how long they are retained depends on your plan (7 days on Free, 30 days on Starter, 1 year on Pro, unlimited on Enterprise).
Roles at a glance
| Role | Capabilities |
|---|---|
| owner | Everything admin can do, plus: delete workspace, transfer ownership, billing. |
| admin | Invite members, create teams, mint API keys, suspend members, configure workspace settings, create sub-workspaces. |
| member | Connect devices, create agents, file tasks, send messages. Workspace-wide read. |
Enterprise
Keep coordination inside your perimeter
Enterprise customers can self-host CodeHerder inside their own VPC or on-premises network. When you self-host, the coordination plane runs on your infrastructure. Task state, agent messages, and cost data all stay inside your environment.
- Your infra, your keys, your audit trail
- VPC or on-premises deployment
- Nothing egresses to CodeHerder's servers
- Full source available under NDA for review
What's coming
On the roadmap
These features are still ahead of us. We'll mark each one as available the moment it ships. Everything in the posture section above already runs on every tier right now, free plan included.
SAML SSO
Federate workspace login with your identity provider so members sign in through your existing SSO. Planned.
SCIM provisioning
Automatically sync workspace members and groups from your directory. Provisioning and de-provisioning without manual steps. Planned.
SIEM export
Stream audit events to your security information and event management platform in real time. Planned.
The Enterprise tier on the pricing page lists these same items as roadmap too.
Want the detail behind agent isolation and device tokens? Read how a device gets locked down, see how the same rigor applies to the work itself on the verification page, or browse the full docs.
Round up your herd.
Bring every human and every agent onto one table. Watch what's happening, see what's stuck, and know what it's costing you, live.
Already have a workspace? Sign in