Selling Minecraft plugins has never been more viable as a side income or full-time business. The ecosystem across SpigotMC, Polymart, and BuiltByBit is thriving, and server owners are willing to pay for quality software that makes their servers stand out.
But with more plugins for sale comes a more pressing question: how do you make sure people running your plugin actually paid for it?
That’s what plugin licensing solves.
What is plugin licensing?
At its core, plugin licensing is a system that verifies whether a server running your plugin has a valid, paid license before allowing it to function.
When a server starts your plugin, it sends a request to a licensing server. That request includes a license key the customer received when they purchased. The licensing server checks:
- Is this key valid and active?
- Has it expired?
- Is it being used on too many servers at once?
- Is this server’s IP allowed to use this key?
If all checks pass, the plugin loads normally. If not, it refuses to start or disables premium features.
Why licensing matters more in 2026
The Minecraft development community has grown significantly — and so has the tooling available to bad actors:
- Decompilers like Recaf are free, well-maintained, and beginner-friendly
- Cracked plugins spread through Telegram channels and Discord servers with thousands of members
- AI coding assistants make it trivial to modify bytecode or strip license checks from a decompiled JAR
If you’re not protecting your plugins, there’s a real chance a large portion of your active users aren’t paying customers.
The main approaches to licensing
Roll your own
Building your own licensing backend is valid if you enjoy infrastructure work — but it means owning uptime, security, key management, and maintenance forever. It’s a non-trivial ongoing commitment.
Obfuscation only
Obfuscating your JAR with tools like Allatori or Zelix makes your code harder to read after decompilation. Think of it as a speed bump: determined attackers get through it, they just take a bit longer.
Dedicated licensing platform
A platform like MC License provides the full stack: validation infrastructure, a dashboard, analytics, expiration control, IP restrictions, and a Discord bot for customer self-service. You add a small SDK to your plugin and the rest is handled for you.
What to look for in a licensing platform
Cryptographic signatures — Validation responses should be RSA-signed. A plain true/false response can be replayed; a cryptographically signed response cannot.
Reliable uptime — Your customers’ servers depend on this at startup. Look for platforms with strong reliability and offline-tolerant SDKs.
Analytics — Knowing which licenses are active and on how many servers helps you spot abuse patterns quickly.
Customer self-service — A Discord bot or customer portal means less manual license management for you.
Sensible pricing — Your licensing costs should scale with your success, not undercut your margins from day one.
Getting started with MC License
MC License was built by the team behind LearnSpigot — we know the Minecraft development space from the inside, having helped more than 15,000 developers learn the craft.
Getting set up takes about 15 minutes:
- Create a free account at mclicense.org
- Import your plugin from your marketplace of choice
- Add the MC License SDK to your plugin (full docs at docs.mclicense.org)
- Generate licenses for your customers — manually, or automatically via marketplace webhooks
The Basic plan starts at $4.99/month and covers up to 3 plugins. The Professional plan at $7.99/month gives you unlimited plugins and licenses — ideal for developers with a larger catalogue or multiple marketplaces.
Have questions? Join us on Discord.