@@ -34,6 +34,31 @@ The fairness rule is explicit: public/open-source collaboration should |
| 34 | stay generous. Paid gates focus on private collaboration, hosted cost, | 34 | stay generous. Paid gates focus on private collaboration, hosted cost, |
| 35 | advanced organization controls, and support expectations. | 35 | advanced organization controls, and support expectations. |
| 36 | | 36 | |
| | 37 | +## Pricing copy rules |
| | 38 | + |
| | 39 | +Pricing and onboarding pages must describe only features shithub can |
| | 40 | +actually deliver on the hosted service. Before changing pricing copy, |
| | 41 | +refresh the official GitHub pricing source and the Stripe Billing docs |
| | 42 | +because both are time-sensitive inputs. |
| | 43 | + |
| | 44 | +Rules for paid-org copy: |
| | 45 | + |
| | 46 | +- Do not mention Copilot, AI agents, AI code review, or AI quotas. |
| | 47 | +- Do not promise SAML, SCIM, LDAP, managed users, audit exports, data |
| | 48 | + residency, compliance attestations, contracts, or custom support |
| | 49 | + until the matching implementation sprint ships. |
| | 50 | +- Do not advertise Packages, Pages, Wikis, Projects, Actions minutes, |
| | 51 | + or storage quotas until those surfaces have enforcement and usage |
| | 52 | + accounting. |
| | 53 | +- Use upgrade language for unavailable Team features instead of hiding |
| | 54 | + existing data. Downgrades preserve configuration and make gated |
| | 55 | + settings read-only where possible. |
| | 56 | +- Keep public/open-source collaboration generous in both copy and |
| | 57 | + enforcement. Avoid copy that makes public repositories feel like a |
| | 58 | + second-class Free tier. |
| | 59 | +- Enterprise is a contact-sales stub in v1. It should collect interest |
| | 60 | + without promising contractual features. |
| | 61 | + |
| 37 | ## Entitlement matrix | 62 | ## Entitlement matrix |
| 38 | | 63 | |
| 39 | | Capability | Free | Team | Enterprise stub | | 64 | | Capability | Free | Team | Enterprise stub | |