System & Updates
The owner-only System & Updates screen: your current Owlat version, container health, LLM spend, and the in-app one-click updater with history.
System & Updates lives under Settings > System & Updates (/dashboard/settings/system) and is visible only to the deployment owner. It is the operational dashboard for a self-hosted Owlat: what version you're running, whether the containers are healthy, what AI is costing you, and a one-click path to the latest release.
Current version
The top card shows the version this deployment is running. On a development build it shows dev.
Container health
A live table of every service container (web, Convex backend, MTA, ClamAV, and so on) with its run state and image tag. Use Refresh to re-poll. This is the quickest way to spot a container that has stopped or is restarting.
LLM spend
A breakdown of your AI cost over the last 7 days, with the total at the top and a per-feature split (drafting, classification, knowledge extraction, the assistant, and so on) showing dollars spent and number of calls. Every priced LLM call across the deployment is recorded here, so this is the single place to see what your AI features are actually costing.
Checking for and applying updates
The Available updates card compares your version against the latest GitHub release.
- Check now polls GitHub for the newest published release.
- Update now appears when a newer version is available. It downloads the pinned Docker Compose template for the target version, pulls the new images, redeploys the Convex backend functions, and recreates the containers. The web app may restart mid-update; the page reloads itself when the new version is live.
Release notes for the available version are shown inline so you can review what's changing before you apply it.
Data volumes persist across a normal update, but a release with breaking schema changes may migrate or reset data. Read the release notes first, and take a backup before you click Update now. If an update fails, the screen links to the recovery steps — see Maintenance & Updates.
Update history
A log of past updates — which version you moved from and to, when it started, how long it took, and whether it succeeded.
The command-line equivalent
Everything here has a CLI counterpart for operators who prefer the shell: owlat upgrade on the host runs the same update flow non-interactively. See Maintenance & Updates for the full self-hosting update and recovery runbook.