One engineer proving one governed workflow
FOUNDER PREVIEW- Codex or Claude Code runtime
- One signed session profile
- Local allow, deny, and approval rules
- Session history and remote stop
PRIVATE PREVIEW PRICING
Our intended subscription boundary is the infrastructure a team governs: a cloud account, cloud project, or cluster. Final public prices are still being validated with design partners.
SUBSCRIPTION SHAPE
No public price is invented before the brokered-credential and provider-verification gates are ready. Preview terms are agreed in writing.
THE BILLING BOUNDARY
A scope can represent an AWS account, GCP project, Azure subscription, or Kubernetes cluster when that provider boundary is released. Named sessions, engineers, policies, and retained receipts live inside it.
STRAIGHT ANSWERS
Not in the current runtime. Attach mode uses the identity already present on the engineer's machine. Brokered short-lived credentials are a separate release gate.
No. It launches and governs the agent you already use through its supported native hook boundary.
No. An engineer who can use the original local credential can operate outside the governed launcher. The console labels that truth. Brokered identity is the stronger boundary.
Founder staging is open for supervised evaluation. Contact us to define one workflow and one governed boundary.
NO PRICING THEATRE