CodeHerderSearch⌘KRequest access →

Run CodeHerder on your own server

Enterprise runs the whole platform on your own server and your own PostgreSQL database. This page lists what reaches CodeHerder and what stays with you.

One server binary and an empty PostgreSQL database

Self-hosting replaces the hosted service with your own deployment. You get the same platform and the same workflow. Only the address changes.

You start one server binary and point it at an empty PostgreSQL database. The server applies every pending schema migration before it accepts a request. PostgreSQL is the only database a self-hosted server supports.

Self-hosting needs the self_host entitlement. The Enterprise plan includes it, and the release download needs it.

The server also needs two outside services. Mail goes through Amazon SES, because the server has no SMTP transport. Sign-in uses your Cognito user pool or your OIDC issuer. See the full list of outbound destinations.

What reaches CodeHerder, and what stays with you

Your data stays in your own stores. Two kinds of request go to the CodeHerder release host: release downloads and update fetches.

Which parts of a self-hosted CodeHerder deployment reach CodeHerder's servers, and which stay with you.
ItemReaches CodeHerder?
Source code and git historyNo. It lives in your repository and on your devices.
Task state and stage transitionsNo. It lives in your own database.
Agent messages and workspace eventsNo. They live in your own database.
Cost and spend dataNo. It lives in your own database.
The audit trailNo. It lives in your own database.
Provider API keysNo. They stay on your devices.
The signed release downloadYes. You request it with your workspace token on install and on each upgrade.
Device and CLI updatesYes. Devices and the ch CLI fetch updates from the CodeHerder release host. It sees your IP address and user agent.
The licence checkNo. The server checks it offline, against a key inside the binary.
Telemetry and update checksNo. The server sends none.

The release download is a signed manifest and a checksummed build. Check the signature and the checksum before you run the binary. An update fetch carries no other data than your IP address and user agent.

You can turn the fetch off. Set CH_AUTO_UPDATE=0 and CH_DS_AUTO_UPDATE=0. Or point CH_CLI_MANIFEST_URL at your own mirror. The ch installer script host is called once, at install. The server also pulls a model price list from models.dev. It sends no customer data. Set CH_COST_PRICING_SYNC=0 to turn it off. Read where self-hosted data lives for every flow that leaves your AWS account.

Your agents still call a model provider. Claude Code and Codex send prompt content derived from your source to their provider on every turn. That request uses your provider key, which stays on your device. CodeHerder never sees the prompt or the key.

Your own deployment has its own operator area

A self-hosted deployment ships its own console. You install no separate admin binary.

  • One console

    The instance-operator area shows cost pricing and database metrics. It also shows slow queries and spawn latency. You can set instance branding there.

  • Humans only

    Only a human account can reach the operator area. The server refuses an agent credential, whatever role it holds.

  • Verified email

    Your operator allowlist names an email address. Sign in as that address once. The deployment admits the operator only after the address is verified.

  • Your own name on it

    Change the mark and the scene image in the same console. You can rename the instance too.

CodeHerder staff have no access to your install. Read what the operator may do and who approves changes.

How to upgrade, and what a lapsed licence does

An upgrade has five steps. A lapsed licence does not stop the server.

  1. 1. Back up the database

    Take a backup first. You need it if you must roll back.

  2. 2. Read the manifest

    Get the new version and the build for your platform. Read the migration notice. It says if a migration may lock a table.

  3. 3. Check the signature

    Verify the manifest signature first. Then check the SHA-256 sum of the build.

  4. 4. Swap the binary

    Stop the server. Start the new binary with the same four encryption keys and the same database.

  5. 5. Wait for migrations

    The server migrates itself. While health reports migrating, wait. Do not stop it.

Read the full download and upgrade guide. It also covers how to roll back a failed upgrade.

When the licence expires

The server writes a warning to its log at 30, 14, 7 and 1 days before expiry. After expiry, the licence keeps its edition for a 30-day grace window. Then the server drops to the community edition. It does this while it runs, with no restart.

What stays

  • Sign-in and multi-factor authentication
  • Roles and audit logging
  • Instance operator access, so you can renew

What stops

  • SAML single sign-on and SCIM
  • New API keys and webhooks
  • Release downloads
  • Licence limits. Each workspace uses its own plan limits.

Keep one operator who signs in without SAML. That operator can still renew after a lapse. Read how expiry and renewal work.

Self-host if you have an operator for it

Self-host

You have a platform owner who runs PostgreSQL day to day. That person reads the server log and plans upgrade windows. They become your instance operator, the account that reaches the deployment's own console.

Stay hosted

You have no one in that role yet. The hosted service runs the same platform and the same workflow. You patch no database and upgrade no binary.

Read who owns what on your install and how to size the deployment before you decide.

Read the operator docs

These guides are public. Your platform owner can read them before you buy.

  • Self-hosted deployment

    Download, verify, run, and upgrade a self-hosted CodeHerder server on your own PostgreSQL database, and confirm which build is live, on the Enterprise plan.

  • Self-host responsibilities and acceptance

    Who owns, runs and is told about credentials, devices, identity, backups and contacts on your install. Includes the launch record to sign.

  • Sizing a self-hosted deployment

    Start-up sizes for the app host, PostgreSQL, and device fleet of a self-hosted server, where each number comes from, and the signals that tell you to grow.

  • Self-hosted infrastructure

    Record the infrastructure you run beside a self-hosted server, list every outbound destination the server can reach, and grant its AWS roles least privilege.

  • Self-hosted data residency

    Where self-hosted data lives, every flow that leaves your AWS account, the vendor endpoints the install still calls, and the outbound channels.

  • Self-hosted backup and recovery

    Escrow the four at-rest keys, back up and copy the database and attachments, watch the recoverable point, rehearse a restore, and promote it safely.

  • Self-hosted licence expiry and renewal

    How your server warns before the licence expires, what stops after it lapses, what stays enforced, and how to renew without losing administrator access.

  • Self-hosted operator access and changes

    CodeHerder staff have no access to your install. See what the operator may do, who approves changes, and the joiner, mover and leaver steps.

Self-hosting ships on Enterprise

Pricing is custom and depends on your deployment. Tell us what you run. We will set up the self_host entitlement on your workspace. Ready to bring your team on board? See the two-week rollout plan.

Try it on one repository for two weeks.

File a task. An agent builds it. A person reads every request. You see the cost of each task.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close