Issue licenses, track installations, and react to abuse from one fast, private command center.
01
Instant controlSuspend or reset in seconds
02
Installation awareKnow exactly where keys are used
03
Edge securedPowered by Cloudflare Workers
Secure admin access
Crown
WELCOME BACK
Enter the command center
Authenticate to manage products, customers, and license activity.
API operational12-hour secure session
CROWN /LICENSES
License command center
--:--
---
LIVE LICENSE INTELLIGENCE
Your software, under control.
Monitor usage, catch risky keys, and handle customer changes before they become support tickets.
0%License health
Live assessment
Loading your license health…
⌁
ALL TIME
0licenses
Total issued across every product
✓
0% HEALTHY
0active
Currently valid and operational
Ⅱ
REVIEW
0suspended
Temporarily blocked from validation
◎
0% CAPACITY
0installs
Servers currently bound to a key
♙
REGISTERED
0accounts
Customers registered in the portal
SMART QUEUE
Needs attention
0
DISTRIBUTION
Product activity
CUSTOMERS
License directory
Search and manage every issued key from one place.
0 results
⌕/
Customer
Product
License key
Usage
Last heartbeat
Status
Actions
◇
No licenses found
Create your first license or loosen the current filters.
PRODUCT CATALOG
One license namespace per plugin.
Keep every Minecraft plugin organized with its own code, key prefix, and usage overview.
YOUR SOFTWARE
Products
0
DEVELOPER DOCUMENTATION
Integrate Crown licensing into any Minecraft plugin.
A production-focused reference for Java 8, Spigot, Paper, and Maven projects. Developers only need the public validation endpoint and their product code.
PUBLIC VALIDATION ENDPOINThttps://licenses.vaeloriamc.net/api/v1/licenses/validate
01
OVERVIEW
What developers need
The developer does not need your Cloudflare account, database ID, admin password, or dashboard access. Give them only the endpoint and the exact product code created in the Products page.
✦
Example product code
VOYAGE must exactly match the code in this dashboard.
✓
Persistent installation IDGenerate once and save it in the plugin folder.
✓
Asynchronous requestNever block the Minecraft main thread.
✓
Fail safelyDisable only the plugin when definitely invalid.
✓
Verify the full responseCheck product and installation ID, not only valid=true.
02
HTTP REQUEST
POST validation payload
Send JSON over HTTPS with a five-second connection and read timeout.
Do not register important listeners or tasks first
Move normal startup into a method such as startPluginFeatures() and call it only after validation succeeds.
07
SECURITY
Rules developers must follow
01
Never include admin credentialsThe plugin receives only the public endpoint and product code.
02
Never disable TLS checksDo not trust all certificates or bypass hostname verification.
03
Never delete customer dataAn invalid license should only disable the licensed plugin safely.
04
Do not collect private server dataNo player IP lists, files, tokens, passwords, or hardware fingerprints.
05
Remember the current limitationUnsigned JSON can still be patched by a determined attacker. Signed responses are the next upgrade.
PRIVATE BUILD PROTECTION
Protect a compiled Minecraft plugin.
Upload a Bukkit, Spigot, or Paper JAR. The private Java service validates the archive, encrypts eligible strings, renames your plugin-owned bytecode, and returns a protected build package.
Checking service…The service must be deployed separately.