> ## Documentation Index > Fetch the complete documentation index at: https://docs.corbits.dev/llms.txt > Use this file to discover all available pages before exploring further. # The Corbits Platform > Corbits is a platform for deploying secure, auditable agents with organizational guardrails — run, govern, and audit agents your whole organization can trust. ## Ship agents your organization can trust Corbits is a platform for **deploying secure, auditable agents with organizational guardrails**. You get the run, audit, and manage layer that turns a promising agent into something you can put in front of real work: control over what agents can do, an audit trail of what they did, and observability into how they're behaving right now. This is the part of the agent stack most teams are missing. Building an agent is the easy 20%. Running it safely — with the right permissions, a record you can hand to security, and the ability to shut it down when it goes wrong — is the other 80%. Corbits owns that 80%. It is not a general agentic toolkit; it's the control plane you run agents *on*. That serves two readers at once: * **Builders and developers** who want to ship capable agents without hand-rolling permissions, secrets handling, and audit logging for every deployment. * **Enterprise evaluators** — a head of AI, plus the compliance and security teams standing behind them — who need to know an agent can be granted exactly what it needs, nothing more, and that every action is accountable. **Control and audit** is the whole point. ## The platform in one view Corbits is layered. Apps sit on top; a control plane governs them; an agent runtime does the work. Finished products people use every day — **Intercode** and **Workbench**. They're built on the Corbits platform, which means the same guardrails and audit trail apply to them too. The layer that runs, governs, and audits agents. This is where organizational guardrails live: what an agent is allowed to touch, which credentials it can use, and a record of everything it does. The execution engine underneath, **powered by Interchange**. It runs the agents; the control plane decides what they're permitted to do while they run. We build on this stack ourselves. Intercode and Workbench are first-party apps running on the same platform we offer you — the guardrails and audit trail described here are the ones our own products depend on. ## The apps Two flagship apps show what the platform makes possible. A coding-agent CLI. Bring agentic coding into your workflow with the platform's guardrails and audit trail already wired in. A go-to-market workspace where agents do real GTM work — governed, observable, and accountable by default. ## Guardrails: control what agents can do The heart of the platform is how it governs agents. Corbits separates **Credentials** — the secrets and identities an agent can act with — from **Grants** — the specific, scoped permissions that say what it's allowed to do. Grants are **fail-closed**: if nothing explicitly permits an action, it's denied by default. That's what lets an organization hand an agent real capability without handing it the keys to everything. How organizational guardrails work — scoped grants, credential separation, and default-deny. Start here if you're evaluating for security or compliance. ## Where to go next Credentials, grants, and default-deny — the control model. The coding-agent CLI, built on the platform. The governed go-to-market workspace.