Open source
Community
$0self-managed
For teams evaluating the architecture or operating the core independently.
- Gateway and Envoy adapter
- Embedded OPA policy engine
- Core connectors and CLI
- Approvals and signed evidence
- Apache-2.0 source
Pricing
Start open. Pay for a production outcome.
The Apache-2.0 core stays inspectable and self-hostable. Paid work buys focused implementation, maintenance, and accountable operating support—not a toll on the open source.
A lower-risk first step
Readiness sprint
Map one agent action surface, its trust boundaries, and a testable control-path plan before implementation.
$2,500fixed · 10 business daysCredited toward a production pilot that starts within 30 days.
Map the control path Recommended first build
Design partner
Production pilot
From $7,500fixed scope · six weeks
Put one consequential workflow behind identity, policy, approval, narrow credentials, and signed evidence.
- Threat and action-surface workshop
- One workflow and up to three existing connectors
- Initial policy pack and simulation
- Identity, approval, and credential setup
- Deployment, failure drills, and evidence handoff
- Weekly engineering working session
After the pilot
Enterprise operations
From $18kper year · billed annually
Keep an agreed BoundRunner deployment maintained, reviewed, and supported after the pilot.
- Release and upgrade planning
- Agreed connector and policy maintenance
- Quarterly evidence and architecture review
- Security update guidance
- Two-business-day initial response objective
Scope boundaries
Final scope follows technical discovery. Net-new connectors, provider fees, third-party licenses, compliance certification, multi-region engineering, and 24/7 response are separate. Paid work uses a signed order form and invoice; there is no self-service card checkout.
Commercial FAQ
Built for a technical buying process.
- Do we have to buy support to use BoundRunner?
- No. The repository is Apache-2.0. Paid engagements cover implementation and an accountable operating relationship.
- Is the readiness sprint required?
- No. Teams with a well-defined workflow can enter the pilot directly. The sprint is for teams that need the action map and acceptance tests first.
- What changes the pilot price?
- New connector engineering, unusual provider contracts, compliance work, additional workflows, and deployment topologies beyond the tested baseline.
- How is recurring scope priced?
- By the agreed deployment, connector and policy surfaces, and response objective—not by agent seats or token volume.