GitHub Marketplace installable by any user before listing
Turn on installation for any user or organization before marketplace work begins so the listing, insights, and review flow are attached to a product people can actually install.
Why this can grow a startup
A lot of marketplace work starts as copywriting, then dies because the app is still configured like a private experiment. GitHub hides the Marketplace section unless the app can be installed by any user or organization. That means installability is not a later compliance step. It is part of whether the listing can even become a real acquisition surface. Teams that switch this on early can test the full path sooner and avoid polishing a route that is still blocked at the gate.
Company example
GitHub's draft-listing flow says the Marketplace section only appears if the app was registered to allow installation by any user or organization, and the Insights page follows the same rule.
Source and metric
Source: GitHub Docs: Drafting a listing for your app
GitHub only shows the Marketplace section when the app is installable by any user or organization.
Source discovered: May 29, 2026
When to use it
Use this when Marketplaces, Product, Onboarding is relevant to setup, developer tools, distribution and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read GitHub Docs: Drafting a listing for your app and identify what is directly supported.
- Choose one channel context: Marketplaces, Product, Onboarding.
- Define the test around GitHub only shows the Marketplace section when the app is installable by any user or organization..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.