Require authorization before sensitive changes proceed.
Hold sensitive GitHub pull requests and configured deployment steps until their authorization requirements are satisfied.
Required checks enforce authorization on the repositories you configure.
Start now
For teams that want the first protected repo and signer online without a sales cycle.
For testing Permission Protocol on one repo
For teams ready to protect real deploys
Evaluation to enterprise
Validate one approval workflow, then agree any broader rollout separately.
Validate one GitHub approval workflow
Validate and roll out one agreed workflow
For organizations standardizing human authorization for AI actions
You're not paying for API calls or approvals.
You're paying for control over actions that cannot be undone:
Permission Protocol ensures:
→ Held actions require an authorized signer; policy clearance is recorded separately
→ Signed receipts record who authorized what
→ Configured checks enforce authorization before an action proceeds