SunLicense v1 and SunLicense Cloud
Two different products are called SunLicense. They're made by the same team, but they don't share accounts, license keys or code. This page explains which one you have and what changes for you.
Which one do I have?
| SunLicense v1 | SunLicense Cloud | |
|---|---|---|
| What it is | A license server you download and run yourself | A hosted service we run for you |
| How you pay | Once, $14.99 (Gumroad or BuiltByBit) | Monthly or yearly, with a Free plan (plans) |
| Where it runs | Your own server (one .jar, one command), or our v1 Managed Hosting | Our servers. Nothing to install |
| Dashboard | Your own address, dark theme | app.sunlicense.com, light theme |
| Docs | docs.sunlicense.hapangama.com | This site |
| Status | Still sold and still updated | Open beta |
SunLicense v1 looks like this:

SunLicense Cloud looks like this:

I own v1. Do I have to buy anything?
No. v1 is not being replaced: it keeps working and keeps getting updates, and you don't need Cloud to use it.
Cloud is a separate product, not an update to v1. Your v1 products and licenses don't appear in Cloud by themselves, but if you want to move, we move them for you with the same license keys (see Moving from v1 to Cloud). If you want to try Cloud first, the Free plan costs nothing.
Offers for v1 customers
| You have | You get on Cloud | How to claim |
|---|---|---|
| v1, self-hosted | 3 months of the Lite plan for free, after the beta ends | Open a ticket in the SunDevs Discord with your v1 purchase receipt (or license key) and your Cloud organization's name |
| v1 Managed Hosting subscription | Lite for as long as your subscription stays active, at the same price | Open a ticket in the SunDevs Discord. We switch your existing subscription over, so there's nothing to cancel |
Moving from v1 to Cloud
We copy your v1 data into your Cloud organization. Your buyers keep their license keys, and plugins you already shipped keep working.
What moves: your products, customers (with their email, Discord account and BuiltByBit or Spigot account), licenses with the same keys, status and expiry dates, the machines each license is already used on, your IP and HWID blacklists, and the API tokens your plugins send.
What doesn't move: the license request history, v1's admin accounts, your customers' v1 passwords (they sign in to the customer portal with an emailed link instead), and your Discord bot and email settings, which you set up again in Cloud. License notes are kept on the customer they belong to.
How:
- Create your Cloud organization at app.sunlicense.com.
- In the dashboard, open Tasks → Start a task → Import from SunLicense V1 (open it; see Imports and tasks). Self-hosted: add v1's
data/sunlicense.mv.dbfile (stop v1 for a moment while you copy it) or a backup from v1's Backups page. Managed Hosting: no file needed, we already have your data. You can also open a ticket in the SunDevs Discord instead. - We check what will move first, then import it and email you. You can keep using v1 until you switch; we can import again later, and only what's new is added.
- Your plugins: if they call an address we host for you, we point it at Cloud and nothing changes for your buyers. If they call your own domain, either point that domain at us (we tell you how) or ship an update that uses
https://api.sunlicense.comas the server address. On that address v1's/api/v2/validateand/api/v3/validatework as before with the token your plugins already send; plugins that call/api/v1/validatewithout a token need one of those two (or one of our SDKs).
How v1 rules carry over: a v1 license limited to some number of HWIDs (or IPs, if it only limits IPs) gets that many machines in Cloud; a deactivated license is suspended, a deleted one revoked, and an expired one keeps its expiry date. IP blacklists match the address the request really comes from.
Which one should I use?
- v1 if you want to run everything on your own server and pay once.
- Cloud if you don't want to run a server, or want what it adds: offline licenses, official SDKs, store integrations, teams and roles and the CLI.
Can I self-host Cloud?
Not today. Cloud runs as several services with message brokers and databases, built for millions of license checks a month, so it's much harder to run than v1's single file. If you want SunLicense on your own server, v1 is the one to use.
For large teams and organizations that need Cloud on their own infrastructure, we may offer an Enterprise plan with self-hosting. Email [email protected] to talk about it.
Still not sure?
Ask in the SunDevs Discord.
