Docs · Account
Billing
Flat price, no per-seat math. You pay for a band of active readers per month. Public repos are free forever at any team size, and billing problems never block a merge.
The meter: active readers
An active reader is a distinct GitHub user who was required to read at least one PR on a private repo during the billing month. The details that matter:
- A reader counts once per workspace per month, across any number of repos and PRs.
- PR authors who are not required readers do not count.
- Bot accounts never count.
- Public repos never count anyone.
The current count is on the billing page, updated as the month runs. It is informational: going over your band changes nothing in CI.
Plans
| Plan | Price | Active readers | Adds |
|---|---|---|---|
| Startup | $19/mo | Up to 3 | Full core product |
| Team | $99/mo | Up to 20 | Priority support |
| Business | $349/mo | Up to 75 | Audit log, analytics, Slack notifications |
| Enterprise | Custom | Unlimited | GHES, SSO, retention guarantees, DPA, invoicing |
Every plan includes unlimited private repos, unlimited PRs, all reading rules and overrides, the review log, email digests, and every browser extension. Annual billing takes 2 months off. Full comparison on the pricing page.
The trial
Installing the GitHub App on a private repo starts a 14-day trial: full product, any team size, no card. At the end, the billing page recommends a band from your trailing 30-day reader count. If the trial ends without a plan, checks on private repos move to neutral and stop enforcing. Nothing is lost; picking a plan resumes enforcement.
Fail open
Money problems never block code:
| Event | What happens |
|---|---|
| Trial ends, no plan | Private-repo checks turn neutral: paused, not enforced. |
| Payment fails | 14 days of grace with email reminders, then neutral. |
| Reader count over the band | CI unchanged. An amber banner on the billing page shows the count. Two consecutive months over brings a firmer nudge. |
| Subscription canceled | Enforced until the period ends, then neutral. |
Mechanics
- Payments run through Stripe Checkout.
- Plan changes happen in the Stripe customer portal, reached from the billing page. Upgrades apply immediately and prorate to the day; downgrades take effect at period end.
- Owners manage billing; members and admins can see the meter.