What does the paid pilot add to Free?
Free is software access to the GitHub gate for a setup you manage. The pilot pays for our engineers building the integration with yours on the gate you choose, agreed acceptance tests, a security review pack and the gate running live by day 30. Choose it when a reviewer, auditor or customer is about to ask who approved an agent's actions.
What happens after 30 days?
Ongoing coverage is scoped and priced for your workflows. We agree Annual terms before you continue. If you do not continue, nothing auto-renews: the gate drops to the Free plan and the receipts already issued stay verifiable.
What does the pilot require from us?
A workflow owner, an engineer for about 4 to 6 hours, named signers and a reviewer who can judge the evidence. We agree the gate, the test path and the acceptance criteria before signature. Payment is due before kickoff; the 30-day clock starts once the agreed access is available.
What if the pilot misses the acceptance criteria?
You get a full refund. The criteria are written down on day one, so there is no argument later about what counted. The refund applies when your side provided the agreed access and engineer hours. If access arrives late, the 30-day clock starts when it does.
How is Team different from the pilot and Annual?
Team is self-managed software access to the GitHub approval workflow for 3 to 10 named signers, at $100 per signer per month billed annually. You configure it, and implementation is priced separately. The pilot and Annual are paid engagements with scope and pricing agreed for your workflows: we build the gate with your engineer on the action you choose, and you get the acceptance tests, the security review pack and evidence export. Enterprise is scoped in an annual agreement. We do not meter gated actions or receipts on any plan.
Can we start with payments, GitLab or a private deployment?
The pilot runs on one of five gates: money out, agent code to prod, infra changes, PII or PHI export, or identity changes. GitHub and MCP clients are supported paths. SSO, GitLab and private deployments need a feasibility and scope review before we promise delivery or quote an engagement.
Will our auditor accept the receipts?
PP receipts provide signed decision evidence that can be verified independently. Your reviewer decides whether that evidence meets their requirement. The pilot tests that fit, and the security review pack gives you the written answers; it does not guarantee auditor acceptance or certify compliance.
Can we keep our existing approvals?
Yes. We start with the approval decision you already require and agree where the gate and receipt fit. Enforcement depends on the selected integration, required checks and bypass permissions, which we review during setup.