Operate

Updates & maintenance

On a managed deployment, the assistant keeps itself current on its own: updates install in a window you can control, always after a backup, and roll back on their own if anything goes wrong. A deployment you installed on your own server behaves the same way — it was enrolled by the installer, so everything below applies to it too.

How updates arrive

This applies to a managed deployment and to one installed from your own Naxis link alike. When Naxis publishes a new version, the contact on file is emailed right away, and the deployment learns of it at its next check-in: the admin Overview announces the pending update, and Settings → Software updates shows the plan — the card appears only when an update is actually waiting, and stays silent the rest of the time. Unless someone chooses otherwise, it installs by itself on the coming Sunday at 02:00, in the deployment’s own local time.

• Update now installs it on the spot — it begins within a minute or two.
• Pick your own window and it’s kept.
• Some updates carry a deadline. A deadline can move the date earlier, never later — and once it has passed, the update installs at the first opportunity.

The one exception is a deployment deliberately run outside the update channel, with no licence link of its own: it has no card and no schedule, and follows whatever process you put around it. Everything installed the ordinary way — see Install — on your server — updates itself as described here.

What happens during an update

1. A database backup is taken. If it can’t be taken, the update doesn’t run.
2. The new version starts and must pass a health check.
3. If it’s healthy, the update is complete — usually a minute or two of downtime.
4. If it isn’t, the previous version is put back automatically. Your data is untouched.

The outcome is visible to Naxis, so a failed update is noticed without you reporting it. If you land on an error page during that window, that’s normal — wait ten minutes and open it again rather than reloading repeatedly.

Backups

A fresh database backup is taken before every update and kept on the server (the most recent few). For a self-hosted deployment on hardware you value, you may also want your own server-level backups — the assistant’s backups protect the upgrade, not the machine.

Staying licensed

The assistant checks in with Naxis periodically. As long as it can reach us, it stays licensed with room to spare. If it can’t reach us for an extended period it will warn administrators well ahead of any interruption — the usual cause is the server losing outbound internet. See Troubleshooting.

Last updated 3 Sep 2026