For platform teams
For platform teams: config as code, for every harness
You run the developer platform. Tempa gives you one place for the agents' configuration, in the workflow you already use for everything else.
How it works for you
GitOps or the web app
Keep the configuration in a Git repository with pull requests and a webhook, or edit drafts in Tempa with a diff and a preview before you publish.
Inheritance with modes
Set the baseline at the top; each level below may add to it, change it or only tighten it, as you decide per setting.
Policies as code
Guardrails are Rego policy bundles with unit tests and sample events, tested against the live config before they ship.
An MCP proxy
Developers' agents reach your internal MCP servers through Tempa, which adds the credentials and allows only the tools each team may use.
A CLI and plugins
One `tempa` CLI and a plugin per harness for Claude Code, Codex, GitHub Copilot, Gemini CLI and Antigravity; files Tempa renders stay out of your repositories' committed tree.
An admin API and MCP
Everything the web app does is in the API, and in an MCP server for your own agents, with the same role checks.