All articles
OperationsOctober 2, 20267 min read

Backups, offline updates, and replacing an AI Box

What the encrypted backup contains, how signed USB updates are checked, and what to plan before restoring data to a replacement appliance.

Written for: IT administrators, records managers, appliance owners

Plan for recovery before you need it. AI Box supports encrypted removable-media backups and signed offline software update bundles, but those solve different problems: a backup protects application data; an update package installs a release.

What the encrypted backup contains

The current backup process uses SQLite's backup API to make a consistent database snapshot, then encrypts the archive with AES-GCM using a passphrase-derived key. The database contains application records such as document metadata, extracted passages, embeddings, user and appliance state, and activity data.

  • The backup is not a copy of the original uploaded document files; retain those in your approved document system.
  • It does not include model weights. Keep track of the model required by your deployment and how it can be reinstalled or transferred lawfully.
  • Protect the backup passphrase separately. Without it, the archive cannot be restored.
  • Inspect a backup and test restoration as part of a planned recovery exercise; store removable media securely.

How offline updates work

  1. A release package is accompanied by a signed update manifest containing version and integrity information.
  2. Copy both files to supported USB media, scan the drive from the appliance's Updates screen, and install the verified package.
  3. The appliance checks the Ed25519 signature and package checksum locally before installation.
  4. After installation, follow the release-specific restart and health-check instructions.
Before replacing the appliance

A database restore does not by itself confirm that a licence can move to different hardware, that the old model is available, or that embedding settings match. Confirm those items with support, keep original files, and validate a test restore before retiring the old unit.

A recovery checklist

  • Create and inspect an encrypted backup on removable media.
  • Store the passphrase and source documents separately from the appliance.
  • Record the installed release, configured inference model, embedding model, and network settings without recording secrets in an unsecured document.
  • Test recovery on a controlled replacement or staging unit before making it the production system.

Further reading

Try it on a document of your own

Ask a sample document a question and see the answer with the exact page it came from — then configure the box your team needs.

Keep reading