Medusa Panel › Server › Manage Servers › License
Every server runs its own licence, and a licence is machine-bound: one key activates one machine. You grow by adding machines, one key at a time, so capacity and cost scale together.
Get your licence key
Your key is in your client area, alongside the Medusa service you ordered. Each server (node) needs its own key.
Activate a server
Open Medusa Panel › Server › Manage Servers, open the server you want to license, and go to License. Enter the key from your client area and activate. The server’s License Type and License Status then show in the Manage Servers list.
Once a key is bound, the engine checks its licence state in the background. A change in billing — suspend, resume or terminate — reaches the engine within a few minutes, so it takes effect on its own.
How a key binds
- A key binds to the machine on its first activation.
- The master and each worker node run their own key — see Master and slave nodes and Adding nodes.
- To move a key to new hardware, reset its binding, then activate on the new machine.
One key, one machine. A key already bound elsewhere will not activate a second host. Reset the binding on the old machine first, or use a separate key per node.
An unlicensed server is skipped by the CDN and load balancing — keep every node licensed so it stays in the delivery pool. See Load balancing and metrics.
Related
- Adding nodes — attach more machines to a cluster.
- Master and slave nodes — how the cluster is organised.
- Load balancing and metrics — why a licence keeps a node in delivery.