# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/jetbrains-plugin-hidden-release-before-public-launch/
- Source: [plugins.jetbrains.com](https://plugins.jetbrains.com/docs/marketplace/hidden-plugin.html?from=IJPluginTemplate)
- GrowthDex source hub: [JetBrains Marketplace Docs: Hidden release](/sources/jetbrains-marketplace-docs-hidden-release-plugins-jetbrains-com/)
- Last checked: 2026-06-06T10:04:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Operations, Launches
- Stages: jetbrains marketplace, launch ops, review readiness, developer tools


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where jetbrains plugin hidden release before public launch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Operations channel.
3. Use the evidence from plugins.jetbrains.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed 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.

## Adjacent tactics in the same lane

- [Edge Add-ons hidden listing before review push](/growth-ideas/edge-add-ons-hidden-listing-before-review-push/) - 3 shared channels, 2 shared stages
- [Atlassian Marketplace review window as launch buffer](/growth-ideas/atlassian-marketplace-review-window-as-launch-buffer/) - 3 shared channels
- [Salesforce AppExchange security review parallel with listing design](/growth-ideas/salesforce-appexchange-security-review-parallel-with-listing-design/) - 3 shared channels
- [Chrome Web Store deferred publish window after review](/growth-ideas/chrome-web-store-deferred-publish-window-after-review/) - 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The JetBrains plugin page should finish the IDE trust check](/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.