Solutions · Enterprise

Fleet control without theater

Platform teams already own developer infrastructure. Managent is the coordination layer when AI coding agents become a fleet — not a side experiment.

Tenancy that fails closed

Agent API keys are org-scoped. Cross-tenant probes return 404, not 403. Workspace sessions are HttpOnly cookies; authorization lives on the server for every endpoint — UI role checks are never the gate. Rate limits cover anonymous and authenticated traffic. Secrets stay server-side; the marketing site never embeds portal tokens or NEXT_PUBLIC_* credentials.

That posture is deliberate: evaluators should be able to map Managent onto an existing access-control matrix without inventing a parallel threat model. Full writeup on /security.

Org keys and the ops console

managent init creates org, keys, and repo records (keys print once). Agents authenticate with Bearer keys; humans use the workspace dashboard for fleet and impact views. Operators get force-release, kill-agent, transfer, and bulk-extend from the ops console when a lease goes orphan or a runner dies mid-heartbeat.

Day-to-day agent machines wrap work with managent run — acquire, spawn, heartbeat, always release. managent status and managent watch expose the territory map so platform engineers can answer “who holds auth right now?” without grepping logs.

Enforcement you can defend

Default leases coordinate intent at the control plane. Filesystem writes are not cryptographically sealed in the default path — we say that plainly. Soft coordination plus hard gates at land time is the deliberate stack: optional managent run --runtime=hardened (Docker or bubblewrap VFS), git hooks that catch local bypasses, and managent enforce verify-pr / required GitHub checks so those bypasses cannot ship.

Semantic verification is optional and honest about limits: it surfaces contract-risk signals; it does not replace merge-tree or claim to eliminate every class of conflict. See /demo/semantic for the interactive shape.

Where it sits in the stack

Beside Git and CI — not instead of them. Agents call the control plane before edit; reviewers see territory; merge checks confirm what was claimed still merges cleanly. Laptop, CI, and cloud runners share one map. Start with the live demo, skim docs, then book a conversation when the mechanics match your fleet.