Public is free. Private is $4 a person.
You pay for people who can reach private work. You never pay for a repository, for storage, or for a server sitting idle.
A personal namespace, or an organization where every repository is public.
- Public repositories, forks, review and landing
- Clone and push with stock git over HTTPS or SSH
- Mirrors, webhooks, export
- 500 hosted CI minutes a month
- Unlimited members; nobody is charged for public work
- Self-hosted runners, unmetered
An organization that holds private repositories. One person is one seat, so a solo developer pays $4.
- Everything in Free, plus private repositories
- 2,000 hosted CI minutes a month per seat, pooled
- Teams, roles and per-repository grants
- Outside collaborators on a single repository
- Seats added the moment someone joins, prorated
- Invoices, cards and cancellation in the billing portal
Hosted CI minutes are counted per job over a rolling thirty days. Jobs on your own runners are never counted.
What each plan holds
| Feature | Free | Team · $4 / person |
|---|---|---|
| Public repositories | Unlimited | Unlimited |
| Private repositories | Not in a free plan | Unlimited |
| People | Unlimited, free | $4 each per month |
| Teams, roles, per-repository grants | Roles | Teams, roles and grants |
| Hosted CI minutes | 500 a month | 2,000 a month per seat, pooled |
| Self-hosted runners | Unmetered | Unmetered |
| Review, land queue, mirrors, webhooks | Included | Included |
| Card on file | No | Yes — taken on the subscription page |
Four steps, and only one of them costs anything
- 1
Sign up
Free, no card. Your namespace holds public repositories and 500 CI minutes.
- 2
Create an organization
Free, no card. Members, teams and public repositories, at once.
- 3
Make something private
The first private repository asks you to subscribe from Billing, at $4 for each person in the organization today. Checkout takes the card, the billing address and a promotion code; back in Billing, one click creates the repository.
- 4
Seats follow people
Adding someone is never refused; the bill rises that moment, prorated. Releasing a seat is a deliberate act in Billing, next to cancel.
What counts as a seat
Every member of the organization, plus every outside collaborator who can reach at least one private repository. Someone you added to a public repository is free. Someone who is both is one seat, never two.
When a payment fails
Everything stays readable. Creating stops: no new private repositories, no new people, and hosted CI on private work pauses until the invoice is settled. No billing state ever deletes a repository.
When you cancel
Private repositories stay readable and become read-only until you subscribe again or make them public. Public work is unaffected.
Self-hosted
The engine is open source. A deployment with no payment provider configured sells nothing: organizations and private repositories are free, and the only meter is the runner budget the operator sets.