JetBrains plugin hidden release before public launch
Upload the plugin as hidden first so review, docs, media, links, and monetization can be finished before the page lands in marketplace search or external search engines.
Why this can grow a startup
A technical marketplace page should not need a public dress rehearsal. JetBrains makes a cleaner launch path available: hide the initial release, let the page go through approval, finish the listing setup, and unhide only when the install surface is ready. That keeps early reviewers and direct-link testers useful without forcing every searcher to see a half-packed page.
Company example
JetBrains lets plugin developers mark the initial upload as Hidden so the plugin stays out of Marketplace search results, IDE plugin managers, and search engines while the team sets up the page, passes approval, and prepares monetization.
Source and metric
Source: JetBrains Marketplace Docs: Hidden release
Hidden plugins stay out of Marketplace search results, IDE plugin managers, and search engines until the team explicitly unhides them.
When to use it
Use this when Marketplaces, Operations, Launches is relevant to jetbrains marketplace, launch ops, review readiness 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 JetBrains Marketplace Docs: Hidden release and identify what is directly supported.
- Choose one channel context: Marketplaces, Operations, Launches.
- Define the test around Hidden plugins stay out of Marketplace search results, IDE plugin managers, and search engines until the team explicitly unhides them..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.