The Comal agent platform
Build company-owned agents on a shared, governed foundation.
Comedor maintains Comal. Your company forks it, runs it on infrastructure you control — a laptop, a VPS, or your cloud — and owns every agent, tool, permission, run, and trace.
One agent, many doors
An agent is a job, not an endpoint.
You build the job once and put it where the work already happens — and you can hand the building itself to the coding agent your engineers already use.
The same agent is reachable from a Slack channel your team tags, a signed webhook your product calls, and a nightly schedule — each door named in its configuration, each pausable on its own. You build the job once and put it where the work already happens.
Open Claude Code or Codex inside your own fork and say what you want. An AGENTS.md at the fork root routes it to the matching runbook — standing the fork up, or interviewing you to author an agent — using your fork's own teams, routes, tools, and approvers rather than invented ones. It stops for every decision it must not invent, and opens no pull request without your say-so.
Less infrastructure, not less governance
From a laptop to a fleet
Every profile deploys the same harness with every rule intact — what varies is how much you run.
profile: solo runs the harness as three services — Postgres, the gateway, and the agent runner — on a laptop or a ~$20/month VPS. Same deploy, same rules: writes wait for approval, budgets are hard stops, and no model change ships without passing your evals.
A fork with no domain, no TLS, and no identity provider can still reach a real agent run: declare a preview identity and comal login mints a loudly-marked local session. It previews the governance mechanics, never identity — non-production, and refused on any deployed fork.
Runtime, gateway, and stores run in your network on every profile. The hosted side is a metadata-only control plane: anything that ever leaves your fork is schema-published operational metadata — never prompts, completions, tool arguments, or retrieval content — and Comedor sits in no request path.
See the platform before you fork.
The registry, eval cards, guides, and release notes sit behind sign-in. Requesting access files a request a Comedor firm user reviews; it needs no fork and creates no account.