Skip to main content
Databunker Pro stores its license key in the database (the config table, under the licensekey key). You can replace it at any time on a running instance — there is no need to restart the service or redeploy.
This page covers applying a key. For what a license controls — record caps, what counts as a record, how many licenses a deployment needs, and what happens at the cap or at expiry — see Licensing and limits.
A new license is typically applied when you:
  • Move from Trial mode to a paid license.
  • Renew a license that is about to expire.
  • Increase the maximum number of records (maxrecords) your plan allows.
Only the main tenant administrator (root token, tenant id 1) can set the license key. The new key is validated before it is saved — an invalid or expired key is rejected and the existing license stays in place.

​
Before you start

To complete this guide, you’ll need:
  • A running Databunker Pro instance.
  • The root access token of the main tenant. See Generate admin credentials.
  • A valid license key. Request or renew one in the Databunker Portal, then fetch it from there once it is approved.

​
Update via the API

Send the new key to the SystemSetLicenseKey endpoint. All Databunker Pro API calls use POST /v2/<Method> and authenticate with the X-Bunker-Token header.
A successful response looks like this:
If the key is invalid or expired, the call returns an error and the current license is left unchanged:
You can pre-load a license at first start with the DATABUNKER_LICENSEKEY environment variable. This is only used during the initial setup; once a key is stored in the database, update it using the API call above.