Billing and plans
GitStack runs the whole stacked-review workflow for free, including two-way GitHub sync, so your replies, merges, and closes post back to GitHub on every plan. Public repos are free on every plan. You pay for the members on your private repos. This page covers what each plan includes, how members are counted, what happens when a plan lapses, and how to cancel.
Plans at a glance#
| Free | Pro | Enterprise | |
|---|---|---|---|
| Price | $0 | $12 / member / month, or $10 / member / month billed annually ($120 / member / year) | Custom |
| Members on private repos | 3 | 10 | Unlimited |
| Members on public repos | Unlimited | Unlimited | Unlimited |
| Repos and storage | Fair use | Fair use | Custom |
| Two-way GitHub sync | Yes | Yes | Yes |
Every plan includes the full gs CLI, the review UI, live updates, automerge,
worktrees, and two-way GitHub sync: reading the GitHub mirror and posting
replies, merges, and closes back to GitHub. Paid plans differ in how many
members can work in your private repos. Repos, storage, sync operations, and
API traffic are fair use, with the ceilings listed in
Limits and fair use.
The member cap counts every distinct account with access to a namespace's private repos, including you as the owner, so Free allows you plus two other members. Public repos have no member cap, and taking part in one never counts toward the limit.
What a member is#
A member is an account with access to a namespace's private repos.
- A personal namespace starts at one member: you.
- An organization counts its distinct members. Ten people with access to its private repos is ten members.
Accounts themselves are always free. Signing up, working in public repos, and running the full workflow solo costs nothing on any plan.
Pro tops out at ten members. A team that needs an eleventh moves to Enterprise, which has no member cap.
An organization on Pro is billed for each of its members, monthly or annually. A personal namespace is a single seat on any plan, so one subscription covers it however many members reach its private repos, and the ten-member cap still applies to that access. Annual billing is two months free: $10 per member per month, charged once a year as $120 per member.
Upgrading to Pro#
Go to gitstack.sh/buy, pick the namespace (your personal handle or an org you own or admin), choose monthly or annual, and complete checkout on Stripe. The plan flips to Pro as soon as the payment confirms.
When a plan lapses or you downgrade#
If a paid plan lapses or an organization drops below what its usage needs, the
namespace becomes read-only for pushes once it is over the Free storage
limit. A
read-only namespace refuses git push (and other writes) with a message
pointing you at your options. Reads are never affected: clone, fetch, and pull
keep working.
To get a read-only namespace writable again, do any one of these:
- Upgrade the namespace back to Pro.
- Export and remove repos to get back under the Free storage limit.
- Delete repos you no longer need.
A read-only namespace never loses access to its own history. Everyone can still clone, fetch, and browse. Only pushes are paused until the namespace is back within its plan limits or upgraded.
The 14-day grace period#
If a renewal payment fails, GitStack starts a 14-day grace period. Your Pro entitlements stay fully in force during that window, so nothing changes while you update your card. If the payment is not resolved by the end of the grace period, the namespace drops to Free and the usual read-only rules apply if it is over the Free limits.
Paying the outstanding invoice at any point during grace clears it immediately and keeps you on Pro.
Canceling#
Manage or cancel a subscription from the Stripe customer portal, reachable from your billing settings. In the portal you can:
- Update your payment method.
- View invoice history.
- Cancel at the end of the current period. You keep Pro through the period you have already paid for, then the namespace moves to Free.
Your repositories are always yours#
Downgrading, lapsing, or canceling never locks you out of your code. A read-only namespace still serves every read, so you can always take a full copy:
git clone --mirror https://gitstack.sh/<namespace>/<repo>.git
Export is never gated by your plan. Your repositories remain yours and exportable on any plan, at any time.