Solutions
Minecraft Plugin Licensing for PaperMC
License protection for PaperMC and Spigot plugins with per-server HWID binding, IP limits, support-driven resets, watermarked downloads, and Discord management.
Ulises Licenses protects premium Minecraft plugins by binding each license key to the servers that run it. PaperMC plugins verify keys on enable, HWID limits stop key sharing across machines, and every download carries a per-license watermark that traces leaks.
Minecraft servers are easy to copy and hard to police, which is why premium plugins need licensing built for that reality. Ulises Licenses binds each license to the servers that run it, not just to whoever bought it.
Each purchase becomes a license key your plugin verifies on enable. HWID binding ties the key to specific machines, IP limits catch account sharing, and watermarked downloads trace leaked jars back to their source.
Per-server HWID binding
Each license allows a configurable number of machines. Server owners request resets through support when they migrate hosts.
PaperMC-first integration
Documented onEnable patterns with async verification, bounded retries, and periodic re-checks that never freeze the main thread.
Watermarked distribution
Every download is fingerprinted per license, so a leaked jar identifies exactly which license leaked it.
Marketplace compatible
Works alongside BuiltByBit and Polymart sales: buyers check out on the marketplace, you issue and enforce the license here.
Discord bot management
Create products, issue and revoke licenses, check buyer licenses, and manage IPs from Discord without opening the dashboard.
How Minecraft Plugin Licensing works
- 1
Create the product
Register your plugin in the dashboard with its HWID and IP limits.
- 2
Issue license keys
Generate a key per buyer, individually or in bulk CSV import after each sale.
- 3
Verify on enable
Ship UlisesLib inside your plugin, read the buyer's key from config, and verify before enabling features.
Minecraft Plugin Licensing questions
Does it work on Spigot and forks?
Yes. Anything running on the JVM with Bukkit API works: Spigot, Paper, Pufferfish, Purpur, and proxies where applicable.
What if a buyer changes hosts?
They open a HWID reset request from their dashboard. You approve it, the old fingerprint is cleared, and the new machine registers on next check.
Can buyers share one key across servers?
Only within the HWID and IP limits you configure. Sharing beyond that is rejected automatically.
Without Ulises vs with Ulises
| Task | Manual | With Ulises |
|---|---|---|
| Issuing licenses | Copy-paste keys over DMs | Dashboard, bulk CSV, and Discord bot |
| Verification | None, or home-grown checks | Cloud API with signed responses |
| HWID and IP limits | Manual policing | Automatic enforcement with resets |
| Updates | Re-upload and re-share files | Auto-update with checksum verification |
| Leak tracing | No trail | Per-license watermarks |
| Revocation | Push a new build and hope | One click, effective on next check |
Related solutions
Java & Kotlin Licensing
Protect any JVM application with UlisesLib: Gradle and Maven setup, license verification, HWID binding, and automatic updates for Java and Kotlin software.
BuiltByBit Integration
Sell Minecraft plugins on BuiltByBit and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.
Polymart Integration
Sell Minecraft plugins on Polymart and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.