Pro for personal accounts
Pro is shithub's single-seat paid plan for personal accounts. It unlocks a small set of features beyond what Free offers, charged at $4 / month and managed entirely through the Stripe Billing Portal.
Upgrade, downgrade, and invoice management live at
/settings/billing.
What Pro unlocks
| Feature | Free | Pro |
|---|---|---|
| Public and private repositories | Included | Included |
| Required reviewers on private personal repos | Upgrade | Included |
| Multi-reviewer (>1 approvals) on private personal repos | Upgrade | Included |
| Advanced branch protection on private personal repos | Upgrade | Included |
| Pinned repositories on your profile | Up to 6 | Up to 100 |
"Advanced branch protection" covers preventing force-pushes, preventing deletion, and requiring signed commits on private personal repos. Basic protection (an empty rule, or one with none of those flags) stays on Free.
What stays on Free
- Public and private repositories — no count limits.
- Org features (Team plan) — Pro applies to your personal account. Organizations have a separate Team tier with its own feature set.
- Issues, pull requests, Actions minutes, Storage — none of these are gated by Pro today. Pro v1 is intentionally small.
Downgrading
Cancellation flows through the Stripe Billing Portal. shithub honors the scheduled cancellation: at the end of the paid period your account returns to Free.
- Existing required-reviewer rules and advanced branch protection flags stay in the database. The gate refuses to create new gated state on Free, but never deletes prior configuration.
- Profile pins above 6 stay in place — you keep what you pinned as Pro; the cap re-applies when you next edit your pins.
Payment failures
A past-due subscription enters a grace period (operator-configured; the default is 14 days). Pro features stay available during grace. After grace lapses, Pro-only features become read-only until billing is brought back into good standing.
Operator note
Each Pro feature gate has an independent operator-controlled enforce
flag in billing.enforce.*. Until an operator flips a feature on,
its gate runs in report-only mode — Free users continue to use the
feature, the would-deny is logged for the soak. This page describes
the eventual Pro behavior; deployment-specific timing depends on
your operator's per-feature rollout schedule.
View source
| 1 | # Pro for personal accounts |
| 2 | |
| 3 | Pro is shithub's single-seat paid plan for personal accounts. It |
| 4 | unlocks a small set of features beyond what Free offers, charged at |
| 5 | $4 / month and managed entirely through the Stripe Billing Portal. |
| 6 | |
| 7 | Upgrade, downgrade, and invoice management live at |
| 8 | [`/settings/billing`](../user/account.md). |
| 9 | |
| 10 | ## What Pro unlocks |
| 11 | |
| 12 | | Feature | Free | Pro | |
| 13 | |---|---|---| |
| 14 | | Public and private repositories | Included | Included | |
| 15 | | Required reviewers on private personal repos | Upgrade | Included | |
| 16 | | Multi-reviewer (>1 approvals) on private personal repos | Upgrade | Included | |
| 17 | | Advanced branch protection on private personal repos | Upgrade | Included | |
| 18 | | Pinned repositories on your profile | Up to 6 | Up to 100 | |
| 19 | |
| 20 | "Advanced branch protection" covers preventing force-pushes, |
| 21 | preventing deletion, and requiring signed commits on private personal |
| 22 | repos. Basic protection (an empty rule, or one with none of those |
| 23 | flags) stays on Free. |
| 24 | |
| 25 | ## What stays on Free |
| 26 | |
| 27 | - Public and private repositories — no count limits. |
| 28 | - Org features (Team plan) — Pro applies to your *personal* account. |
| 29 | Organizations have a separate Team tier with its own feature set. |
| 30 | - Issues, pull requests, Actions minutes, Storage — none of these are |
| 31 | gated by Pro today. Pro v1 is intentionally small. |
| 32 | |
| 33 | ## Downgrading |
| 34 | |
| 35 | Cancellation flows through the Stripe Billing Portal. shithub honors |
| 36 | the scheduled cancellation: at the end of the paid period your |
| 37 | account returns to Free. |
| 38 | |
| 39 | - Existing required-reviewer rules and advanced branch protection |
| 40 | flags stay in the database. The gate refuses to **create** new |
| 41 | gated state on Free, but never deletes prior configuration. |
| 42 | - Profile pins above 6 stay in place — you keep what you pinned as |
| 43 | Pro; the cap re-applies when you next edit your pins. |
| 44 | |
| 45 | ## Payment failures |
| 46 | |
| 47 | A past-due subscription enters a grace period (operator-configured; |
| 48 | the default is 14 days). Pro features stay available during grace. |
| 49 | After grace lapses, Pro-only features become read-only until billing |
| 50 | is brought back into good standing. |
| 51 | |
| 52 | ## Operator note |
| 53 | |
| 54 | Each Pro feature gate has an independent operator-controlled enforce |
| 55 | flag in `billing.enforce.*`. Until an operator flips a feature on, |
| 56 | its gate runs in report-only mode — Free users continue to use the |
| 57 | feature, the would-deny is logged for the soak. This page describes |
| 58 | the **eventual** Pro behavior; deployment-specific timing depends on |
| 59 | your operator's per-feature rollout schedule. |