System

Web UI → System is the box-level health page: host resource usage, AIOS service states, remote-access status, and the self-update card, pulled from GET /api/system/stats (and, for updates, GET /api/update/status).

Host

• OS — the distro’s PRETTY_NAME from /etc/os-release.
• AIOS DASHBOARD — the running dashboard binary’s version.
• HOST UPTIME — from /proc/uptime.
• LOAD (1/5/15m) — from /proc/loadavg.
• MEMORY — used/total in MB from /proc/meminfo, with a bar that turns red past 85% used.
• DISK / — used/total in GB for the root filesystem (df -BG /), same red-past-85%-used treatment.

Services

One row per AIOS systemd unit, each a green ACTIVE or red DOWN dot from systemctl is-active <unit>.service:

• aios-gateway
• aios-dashboard
• aios-dashboard-auth
• aios-bridge
• aios-bridge-auth

Remote access

The REMOTE ACCESS card on this page reports Tailscale status — it’s how a desktop or unlisted-domain install is reachable from another device without port-forwarding or public DNS. Three states:

• Not installed — Tailscale isn’t on this box; re-run the provisioner with --with-tailscale to enable it.
• Connected — green dot, shows the tailnet hostname/IP to reach this dashboard at.
• Installed, not connected — red dot, prompts you to run tailscale up.

Updates

The UPDATES card checks GET /api/update/status for a newer release:

• No releases published yet — shows the current version only.
• Up to date — green dot, current vs. latest version shown.
• Update available — pulsing dot, current → latest version, a link to release notes, and either:
  • APPLY & RESTART button (Linux only) — calls POST /api/update/apply after a confirmation dialog. This restarts aios-gateway immediately; you still have to restart the dashboard itself manually afterward (systemctl restart aios-dashboard) since it can’t safely restart itself mid-response.
  • A note to run aios update apply from a terminal, for macOS/desktop installs (source rebuild) or unsupported platforms.

Where everything lives

Path	Contents
/root/.aios	config, .env, sessions.db, harness.db, memories/, projects/, agents/
/root/.aios-control/	mothership tenant registry
/root/.aios-license-keys/	license signing key (mothership only)
/etc/systemd/system/aios-*	service units
/etc/nginx/sites-available/	gateway + project sites
/var/backups/aios/	backups

For the CLI/API-level view of the same on-disk layout — what each running binary is called and where it’s installed — see the “What a running install looks like on disk” table in Getting Started.