Pilot APort guardrails with one team first
Start a founder-led rollout with one repository, runtime, or managed-device group. Use hosted OAP decisions, GitHub Repository Guard, Claude Code/Cursor/Goose controls, MCP authorization, and org audit before expanding.
Pilot program
What you get
A practical rollout path for teams adopting agent guardrails.
Pilot program
What we need
The minimum context needed to make the rollout useful.
Pilot program
Best-fit pilots
Teams where APort can prove value quickly.
Rollout sequence
How it works
From first protected action to team rollout in five steps.
Scope
Pick the first agent runtime, GitHub repo, or managed-device group.
Plan
Map passport, policy, enforcement mode, and audit requirements.
Kickoff
Create the hosted passport, setup key, and first install path.
Prove
Run real decisions and review allow/deny evidence together.
Expand
Move to Team at $499/month or Enterprise at $4,990/month.
Pilot answers
Frequently asked questions
What's the time commitment?
Most teams start with a 30-minute planning call and one focused setup session. Initial setup is usually one agent runtime or one GitHub repository before expanding.
Do I need production traffic?
No. You can start in report-only mode or with a single internal team. The most useful rollout has real developer workflows, repository changes, or MCP tools to evaluate.
What happens after the pilot?
Team starts at $499/month for hosted enforcement and org audit. Enterprise rollout starts at $4,990/month when you need managed deployment, custom policy support, and dedicated support.
Can we start without procurement?
Yes. Developers can start free with hosted or local passports. Paid setup is for teams that need shared enforcement, signed decisions, organization audit, and rollout support.
Start small
Ready to protect one agent workflow?
Start with one controlled rollout. If it proves value, convert the same organization to Team or Enterprise instead of rebuilding setup.