Start with the Marketplace
A JetBrains plugin has an option most plugin platforms lack: the store sells it, delivers the license and keeps the books. The Marketplace documentation says the commission on each plugin purchase is 15%, that the rate can change with one month’s notice and can never exceed 25%, and that “JetBrains takes care of processing any taxes related to the sale”. VAT or withholding tax is added on top of your list price, not taken from it.
Paid plugins declare a <product-descriptor> in plugin.xml with a product code, a release-date and a release-version. JetBrains says the release date is “one of the most crucial parameters, as the subscription model depends on it”, and that perpetual fallback licenses and licensing terms are calculated from it. The license check itself runs through JetBrains’s licensing and its account system, so you do not write a validation server.
That is a lot of work done for 15%. If you want to sell a plugin to people who already hold a JetBrains account, this is the path of least effort, and it is the one most buyers expect.
When to sell it yourself
The Developer Agreement defines Externally Paid Plugins as plugins “for which the fees are not processed through JetBrains Marketplace but are instead paid directly to You”. It also says that the sale of such plugins “must occur outside of JetBrains Marketplace and is the responsibility of the Developer”. When you upload a plugin you choose between Free, Paid and, if that option is available to you, Externally Paid. Confirm the option for your plugin before you build around it.
Reasons to sell outside the Marketplace:
- One license across products. Your plugin is one of several: a VS Code extension, a CLI, a web app. A Clavem key works in all of them.
- Your own pricing and terms. Team prices, annual invoices, educational discounts, a lifetime option, upgrade pricing.
- The customer relationship. You get the buyer’s email and can contact them.
- No commission. You pay Stripe’s processing fee and Clavem’s flat plan instead.
Reasons to stay in the Marketplace: tax handled for you, perpetual-fallback logic you do not have to write, discovery inside the IDE, and no payment operations at all.
What the fee difference looks like
Take a plugin priced at 50 USD and 20 sales a month.
| JetBrains Marketplace | Stripe plus Clavem | |
|---|---|---|
| Fee per sale | 15% = 7.50 USD | 2.9% + 0.30 USD = 1.75 USD (Stripe, US cards) |
| 20 sales | 150 USD | 35 USD to Stripe |
| Platform fee | Included in the commission | 0 USD on Clavem’s Free plan up to 50 active licenses, then 29 USD a month on Indie |
| Tax handling | JetBrains | You, through Stripe |
At 20 sales, Stripe plus Clavem’s Indie plan costs about 64 USD against 150 USD, but you take on VAT and sales tax. The Marketplace fee is paying for that work as well as for the store. Run your own numbers in the Stripe fee calculator.
What is specific to the IDE
A plugin runs inside the IDE’s JVM, with the same rights as the IDE. Three platform pieces help with licensing:
- Network. Make the call with the IDE’s HTTP utilities or
java.net.http; the License API needs nothing special. Do not block the UI thread: run it in a background task. - Storage. Keep the key and token in the IDE’s
PasswordSafe, not in a settings XML that users share. - A stable id. The IDE has a permanent installation id,
PermanentInstallationID. Hash it and send it asfingerprint, so reinstalling the plugin returns the same seat.
IDEs also run on machines with proxy settings. Respect the IDE’s proxy configuration, and fall back to the stored token if the call fails.
Recommended setup for a self-sold plugin
| Setting | Suggested value | Why |
|---|---|---|
| License type | Subscription with a perpetual fallback, or perpetual with paid major versions | The Marketplace’s own model is a subscription with fallback, which JetBrains users know |
| Device limit | 3 | A work machine, a home machine and a remote machine |
| Trial | 14 to 30 days | Time to try the plugin on a real project |
| Updates | Marketplace listing as Externally Paid, if available to you | The Marketplace delivers updates; Clavem decides whether features run |
Clavem’s validity options are perpetual, a fixed number of days, or following the Stripe subscription. A perpetual fallback after a year is not built in; sell the subscription and a separate perpetual price, each mapped to its own product, if you want both.
Doing this with Clavem
Create a product, connect Stripe, map the prices. After payment, the buyer gets a key and an order page. The plugin calls activate once and validate in a background task at startup. See the JetBrains plugin guide, plus the Kotlin and Java guides for code.
Guides to follow
- License key validation for JetBrains plugins
- Offline license verification for JetBrains plugins
- Device activation in Kotlin
Questions
Can I sell a JetBrains plugin outside the Marketplace?
The JetBrains Marketplace Developer Agreement defines Externally Paid Plugins, whose fees are paid directly to you, and says their sale must happen outside the Marketplace and is your responsibility. The option may not be available to every plugin, so check the upload options and the agreement.
What does JetBrains charge to sell a plugin?
JetBrains Marketplace's help pages state a 15% commission on each plugin purchase, which can change with one month's notice and never exceeds 25% under the Developer Agreement. Taxes are calculated on top of the price you set.