Reassign an instance to a different license
If you've created a new license — under a different email, or after switching plans — and your instance is still connected to the old one, a platform admin can move it across with no downtime and no reconfiguration on your end.
When you might need this:
- You created a new license under a different email address
- Your old license expired and you purchased a new one
- You're consolidating multiple licenses
What happens during reassignment:
- The admin moves your instance to the new license in the kuploy.app dashboard
- On the next sync — within an hour by default, or immediately if you click Retry Sync on
/admin— your instance detects the change and receives the new license key - It begins using the new license's limits and features
- No restart and no
.envchange are needed on your side
If your instance has LICENSE_KEY hardcoded in its .env, the sync still works correctly — the hub recognises the instance itself and responds with the right license data. Update the .env anyway, so the file doesn't disagree with reality.
If your instance is stuck on an expired or wrong license, contact your platform administrator or reach out to support@kuploy.app to request a reassignment.
Viewing Assignment History
You can see the full reassignment history for any license:
- Sign in to kuploy.app
- Go to Licenses
- Click on a license to view its detail page
- The Assignment History section shows all past reassignments, including timestamps and which license the instance moved from/to
This is useful for auditing when an instance was moved between licenses and tracking changes over time.