Licence and updates
The check-in
Every 12 hours, and once when you activate, your install contacts license.nuroute.ai over
HTTPS. In return it gets a token that allows it to route for the next 5 days, plus any new
routing model or model catalog.
It sends exactly this, and nothing else:
| Sent | Example |
|---|---|
| Your licence key | nrl_… |
| A random install ID, made when NuRoute was installed | 3f1c… |
| NuRoute's version, routing-model version and catalog version | 1.0.0, f78abef327baf8cc, 9234ee8784d1243a |
| The number of API requests since the last check-in | 48213 |
| Whether each NuRoute service is up | { "auth": "up" } |
Never sent: prompts or answers, API keys or provider keys, user names or email addresses, which models or providers you use, costs, logs or IP addresses. Owners and admins can see the exact last check-in under Licence & system → What the last check-in sent.
We use the request count only to agree on your volume tier at renewal. It never limits or stops your install.
When the check-in fails
The token lasts 5 days, so a failed check-in is not an outage. The dashboard shows a banner to everyone while something needs attention:
| Banner | What it means | What to do |
|---|---|---|
| "We couldn't reach the licence server at the last check-in. API requests keep working for N days…" | The server could not reach license.nuroute.ai (firewall, proxy, DNS) | Allow outgoing HTTPS to license.nuroute.ai (see Requirements). The next check-in, at most 12 hours later, clears it. To check sooner, restart: docker compose restart auth-service |
| "This install's licence has been revoked…", "The licence server says this licence has ended…", "…belongs to another install…" or "…no longer recognises this licence key…", each with "API requests keep working for N days" | The licence server refused the licence | Contact NuRoute. Requests keep working until the current token runs out |
| "Your licence ends in N days" / "Your trial ends in N days" | Fewer than 14 days left | Contact NuRoute to renew or to move from the trial to a licence |
| "This install's licence has ended or could not be renewed, so API requests are refused" | The token ran out | See Licence & system for the reason. Once renewed, enter the new key there, or restart auth-service after a renewal of the same key |
| "Your NuRoute trial has ended, so API requests are refused" | The 14 days are over | Contact NuRoute for a licence key, then enter it under Licence & system |
| "This install is not activated, so API requests are refused" | No licence yet | Activate on the setup screen or Licence & system |
While requests are refused, the API answers 402 with a reason (licence_required,
licence_expired, trial_ended), and 503 licence_unavailable if the status cannot be checked
for a moment. The dashboard stays available so admins can fix it; nothing is deleted.
Trials
A trial lasts 14 days and includes everything. Start it on the setup screen with your work email; each company (email domain) gets one trial. To continue after it, contact sales@nuroute.ai for a licence key and enter it under Licence & system → Enter a new licence key: the install, its data and its settings stay as they are.
Renewals and new keys
Your licence runs until the end date in your contract. When the renewal is paid, NuRoute extends it on our side and your install picks it up at its next check-in; you do nothing. If we send you a new key (for a new contract, or a move from a trial), enter it under Licence & system → Enter a new licence key.
A licence key works on one install. Reinstalling or moving to a new server? Ask support@nuroute.ai to release the key, then enter it on the new install.
Routing-model and catalog updates
NuRoute's routing model (which decides which model each request needs) and its model catalog (models, prices, quality tiers) improve continuously. Your install receives the latest of both with the check-in, independent of NuRoute releases, so you do not need to upgrade for them.
Both are signed by NuRoute with a key that never leaves our build pipeline. Every NuRoute service checks the signature before using an update and keeps what it has if anything is wrong, so a tampered or damaged update is never used. Licence & system → What the last check-in sent shows which routing-model and catalog versions your install runs.
A new model in the catalog that needs a provider your NuRoute release does not support yet appears once you upgrade.