The complete engineering superharness for teams.
One policy, set centrally.
Developers code with palgu. Every request goes through the Palgu API, where your team sets routing, budgets and policy once. Teams that keep Claude Code or Codex can opt in to routing them through Palgu. The table below shows which controls apply to each client.
Six questions for your platform and security review.
Forward this page internally. Each answer names the mechanism your security review can check.
What do developers install or change?
One install and one sign-in: palgu login, then palgu to code. Palgu leaves Claude Code and Codex settings alone; developers who stay in Claude Code use Palgu there through the open-source Mixture of Models mod. Cursor and aider point at the OpenAI-compatible endpoint. Start with one repository; Palgu indexes it and the harness applies from the next task.
Palgu CLI · Mixture of Models mod for Claude Code · OpenAI- and Anthropic-compatible endpointWhat can developers bypass, and who approves exceptions?
Practice and model policy are set at the org level and apply per task. Exceptions are requested in-session and approved by the roles you designate; every exception is recorded in the audit ledger with who, what and why.
policy engine · allowlists · audit ledgerWhat leaves our infrastructure?
Requests to the models you allow, routed through Palgu or your self-hosted gateway. The audit log keeps a hash of each prompt, not its text. Conversation transcripts are kept under a 30-day default retention setting, encrypted on the managed service (self-hosted: depends on your key setting), and an org admin can turn them off. Your code never executes in Palgu; tests run in your CI. Sensitive repos can be pinned to local models; with a self-hosted gateway, their requests stay in your network.
hashed audit · transcript capture you control · client-side test execution · Ollama / sovereign endpointsWhat happens when Palgu or a provider is down?
Circuit breakers detect the outage. Transport failover moves the session to an alternate provider without a quality downgrade and keeps it there for the session. Over budget, requests go to a lower-cost model instead of failing, and the ledger records it.
circuit breakers · session-sticky transport failover · budget downgradeWhy this instead of agent config plus CI plus an open-source harness?
Palgu ships the code graph, task memory, review council and decision ledger as one system that uses your repository’s code graph, under central policy and audit. You do not have to wire them together or keep them in sync.
Cortex code graph · Mnemos · Council · provenanceWhat does it cost in money, latency and operations?
Self-serve plans are per seat per month, billed monthly: Starter $9, Pro $19, Team $39, Business $59; Enterprise, with a self-hosted gateway and SSO, is a contract. AI usage is billed separately at provider cost + 10% managed gateway fee from a prepaid balance (BYOK: no Palgu token markup), with routine work routed to efficient models. Routing adds a single in-band pass. Operations: a hosted service, or a gateway you run with auto-update.
plan + AI usage at provider cost + 10% managed gateway fee · one in-band routing pass · managed or self-hostedWhere requests go, and what Palgu stores.
Palgu servers never run your code. Tests run in your CI. Sensitive repositories can be pinned to local models on a self-hosted gateway, so their requests stay in your network.
Keep an existing coding client. Route its requests through Palgu.
Centrally managed. Runs where you need it.
Start with one repository. Expand by policy.
- Week 1One repository, one teamIndex the repo, connect the agents, apply your existing standards as policy.
- Week 2Turn on review and validationCouncil review with palgu review, and functional plus visual validation of changes. Watch the audit ledger.
- Week 3Set model policy and budgetsAllowlists, risk-tier routing, per-team budgets, sensitive repos on local models.
- ThenExtend policy to more teamsNew repos and teams inherit the harness. Developers keep choosing their tools.
curl -fsSL api.palgu.ai/install.sh | bash
palgu login
palgu # every request through your gateway