Branded FAQ
Is CatWrangler hosted, or do I self-host?
CatWrangler is a fully hosted service — there's nothing to install or self-host. Each customer gets their own isolated server. Your agents simply point at it and build, while credentials and the write path stay structurally out of an agent's reach.
You don't run CatWrangler; CatWrangler runs for you. It's a hosted service with one isolated server per customer, so the version control underneath stays server-side and invisible.
Hosted, isolated, nothing to install
There is no self-host option to weigh, no server to provision, no version-control engine to babysit. You connect your agents and start building. Behind the scenes, real version control runs on infrastructure dedicated to you — not shared with other customers.
- A hosted service — no install, no self-host, no pipeline to wire up.
- One isolated server per customer, so your codebase and history are yours alone.
- Real team access control: login, SSO, and per-org membership.
Why agents never hold the keys
Because the write path lives server-side, credentials stay out of an agent's reach by design. An agent can't slip past the gates — describe, isolate, validate — because it never holds the keys to do so. The structure does the enforcing, not a policy an agent could ignore.
Related questions
Is there a self-hosted or on-premises version?
No. CatWrangler is a hosted service with one isolated server per customer. There's nothing to install or operate yourself — you point your agents at it and build.
Can an agent access the underlying credentials or write directly?
No. The write path and credentials are structurally out of an agent's reach. An agent can't bypass the gates because it never holds the keys.
Keep reading
Vibe-Engineering
Many agents. One codebase. Zero collisions.
Point your agents at CatWrangler and build — the discipline runs underneath.