Company logoOpen Ticket AI

Updates

Update an Open Ticket AI install to a new release.

Updates

Use the operations CLI in the install directory to upgrade Open Ticket AI safely. Updates always create a backup first and roll back automatically if post-update checks fail.

Online update

# From any directory once install put `otai` on PATH:
otai update              # latest version allowed by the license
# or:
otai update 0.2.0

Air-gap update

Copy the new extracted release tree to the server, then:

otai update --from-dir /path/to/otai-0.2.0

No download API call is made in this mode.

What otai update does

  1. Tags the currently running images with the old software version (for rollback).
  2. Runs otai backup and stores an archive under backups/.
  3. Downloads or uses --from-dir to get the new release.
  4. Loads image tars, replaces compose files and CLI helpers, updates version fields in .env, and refreshes the PATH wrapper.
  5. Starts the stack (docker compose up -d).
  6. Runs otai verify (Studio + Runtime health).
  7. On failure: restores the pre-update backup (compose, .env, both SQLite databases) and starts the previous version again.

Verify

otai verify
otai version

verify checks that Studio API and Runtime containers are running and that their /health endpoints respond. Full unit tests run in Open Ticket AI CI; customer hosts only run this smoke check.

Tips

  • Prefer pinned versions in production (otai update 0.2.0) over latest.
  • Do not run docker image prune during or immediately after an update — old tags are kept so rollback can reuse them.
  • Ticket-system databases are not upgraded by otai update. Apply any new connector packages from the release’s ticket-system-packages/ folder according to your ticket system’s package procedure.
  • Keep a recent backup off-host before large upgrades (see Backups).