System
Platform status
What this deployment is, whether it is healthy, and what changed. Every panel says when its data was collected, so nothing stale can read as live.
This screen is read-only. It never restarts, deploys, migrates, backs up or restores anything — those are YELLOW/RED actions under the security model and run from a shell through ops/. Where an action would help, the exact command to run is shown instead of a button.
NOMINAL
All platform checks passing
- Readiness: ok
- Database: ok
- Configuration: ok
- Supervision: ok
- Process: ok
- Build: ok
Status collected (just now)
Auto-refreshes every 20s while this tab is visible.
Process and supervision
Service health
Up 1h 35m
PID 869234, started 2026-10-05 18:07 UTC
- Supervisor
- OKsystemd --user · paxx-webRestarts automatically on exit and starts again after a reboot.
- Restarts
- yes
- Survives reboot
- yes
- Started
- 2026-10-05 18:07 UTC
- Uptime
- 1h 35m
- Memory (RSS)
- 231 MB · heap 87 MB / 96 MB
- Event loop
- 0% utilised since start
Readiness probes
Ready · 4/4 passing| Probe | Result | Detail | Latency | Checked |
|---|---|---|---|---|
| Database reachable | PASS | Store responded to a trivial query (postgres). | 7ms | 2026-10-05 19:42 UTC |
| Schema migrations | PASS | All 11 shipped migrations are applied. | — | 2026-10-05 19:42 UTC |
| Required configuration | PASS | Every variable required to run publicly is present and structurally valid. | — | 2026-10-05 19:42 UTC |
| Seed data | PASS | The owner account exists. | — | 2026-10-05 19:42 UTC |
Probed (just now)
If you need to act
What the deployment itself thinks is true, from a shell:
ops/status.shFollow this unit's logs live:
journalctl --user -u paxx-web -n 200 -fRestart the service (YELLOW — run it yourself, from a shell):
systemctl --user restart paxx-webPersistence
Database
Reachable in 7ms
23 tables
- Driver
- PostgreSQL
- Store
- postgres://paxx@127.0.0.1:55432/paxx_dev
- Reachable
- yes7ms
- Migrations
- up to date11 applied / 11 shipped
- Tables
- 23
Operations journal
Deployment status
Succeeded
commit 796def2 · main · by dome
- Release
- /home/dome/paxx-deploy/releases/20261005T151611Z-796def2
- Commit
- 796def2 on main
- Rollback target
- none recorded — no rollback target is known
- Started
- 2026-10-05 15:16 UTC (4h ago)
- Duration
- 1m 12s
- Steps
- 12/13 ok, 1 skipped
- Actor
- dome
Steps of the latest attempt
| Step | Result | Took | Detail |
|---|---|---|---|
| key-storage | ok | 25ms | both keys come from .env.local; no key file is in play |
| create-release | ok | 133ms | /home/dome/paxx-deploy/releases/20261005T151611Z-796def2 |
| link-shared | ok | 16ms | — |
| stamp | ok | 10ms | 796def2 @ 2026-10-05T15:16:11Z |
| install | ok | 667ms | pnpm install --frozen-lockfile |
| build | ok | 1m 01s | pnpm build |
| stop | skipped | 14ms | unit not active |
| backup | ok | 128ms | — |
| migrate | ok | 4.3s | 11 newly applied |
| swap | ok | 5ms | current -> 20261005T151611Z-796def2 |
| restart | ok | 49ms | — |
| health | ok | 2.7s | ready |
| prune | ok | 16ms | 0 removed, 1 retained |
Recent deploys
| Started | State | Commit | Steps | Duration | Actor |
|---|---|---|---|---|---|
| 2026-10-05 15:16 UTC | Succeeded | 796def2 | 12/13 ok, 1 skipped | 1m 12s | dome |
| 2026-10-05 15:11 UTC | Failed | b70e532 | 7/8 ok, 1 skipped | 1m 05s | dome |
| 2026-10-05 15:09 UTC | Failed | ec7e547 | 4/4 ok | 0ms | dome |
Build identity
App version
v0.1.0 · 796def2 · main
- Version
- 0.1.0
- Commit
- 796def2
- Branch
- main
- Built
- 2026-10-05 15:16 UTC
- Release
- 20261005T151611Z-796def2
- Environment
- productionNode v24.18.0
Presence and validity only
Configuration
All required configuration present
26 optional variables not set.
Values are never read into this page — only whether each variable is set and whether it is structurally valid.
Deployment
- PAXX_PUBLIC_URL
Public base URL of this deployment. OAuth redirect URIs are built from it; without it they are guessed from the request's forwarded origin.
Set
Security
- PAXX_SECRET_KEY
Seals integration credentials at rest. Without it no Connect flow can store anything — sealing fails rather than writing plaintext.
Set - PAXX_TOKEN_ENCRYPTION_KEY
Seals Google OAuth tokens and PKCE verifiers. Without it the real Google connector is never selected and both account slots run the mock.
Set
Connector health
Integrations
18 of 18 integrations healthy.
| Integration | Health | Data | Latency |
|---|---|---|---|
| Command Center | healthy | unknown | 8ms |
| Database | healthy | unknown | 4ms |
| Worker | healthy | unknown | 12ms |
| OmniRoute | healthy | unknown | 55ms |
| Obsidian Sync | healthy | unknown | 20ms |
| Paperclip | healthy | MOCK | 42ms |
| GitHub | healthy | MOCK | 110ms |
| Google Workspace (primary) | healthy | MOCK | 180ms |
| Google Workspace (second) | healthy | MOCK | 143ms |
| ClickUp | healthy | MOCK | 95ms |
| PAXX | healthy | MOCK | 30ms |
| Obsidian | healthyin-memory fixture vault | MOCK | 2ms |
| Spotify | healthy | MOCK | 60ms |
| Weather | healthy | REAL | 34ms |
| Xentral | healthyMock fixtures — no real Xentral API is connected. | MOCK | 42ms |
| Shopify | healthyMock fixtures — no real Shopify API is connected. | MOCK | 38ms |
| PAXX P1 | healthyMock fixtures — no real PAXX P1 API is connected. | MOCK | 27ms |
| Carrier network | healthyMock fixtures — no real carrier API is connected. | MOCK | 61ms |
Health checked (just now)
Connect, disconnect and enable/disable live in Settings → Integrations. They are not duplicated here on purpose — one set of controls, one source of truth.
Latest entries
Recent log output
systemd journal · paxx-web
Read from journald.
Read (just now)
- infopaxx-webSeeded 3 default weather favorites.pid=869234
- infopaxx-webSeeded default settings for dh@gopaxx.de.pid=869234
- infopaxx-webSeeded 13 integration rows.pid=869234
- infopaxx-webSeeded owner user: dh@gopaxx.depid=869234
- infopaxx-web ✓ Ready in 416mspid=869234
- infopaxx-web ✓ Starting...pid=869234
- infopaxx-web - Network: http://127.0.0.1:3200pid=869234
- infopaxx-web - Local: http://127.0.0.1:3200pid=869234
- infopaxx-web ▲ Next.js 15.5.27pid=869234
- infoinit.scopeStarted paxx-web.service - PAXX Command Center (Next.js).pid=33115
- infoinit.scopepaxx-web.service: Consumed 3.738s CPU time, 119M memory peak.pid=33115
- infoinit.scopeStopped paxx-web.service - PAXX Command Center (Next.js).pid=33115
- infopaxx-web{"at":"2026-10-05T18:07:09.732Z","level":"info","source":"platform","message":"Database handle closed; exiting cleanly."}pid=868386
- infopaxx-web{"at":"2026-10-05T18:07:09.674Z","level":"info","source":"platform","message":"Shutdown signal received; draining.","fields":{"signal":"SIGTERM"}}pid=868386
- infoinit.scopeStopping paxx-web.service - PAXX Command Center (Next.js)...pid=33115
- infopaxx-webparams:pid=868386
- infopaxx-web[paxx:system] seed check failed; returning a degraded report instead: Failed query: select "id", "email", "name", "role", "created_at", "updated_at" from "users"pid=868386
- infopaxx-web}pid=868386
- infopaxx-web }pid=868386
- infopaxx-web routine: 'parserOpenTable'pid=868386
- infopaxx-web line: '1449',pid=868386
- infopaxx-web file: 'parse_relation.c',pid=868386
- infopaxx-web position: '71',pid=868386
- infopaxx-web code: '42P01',pid=868386
- infopaxx-web severity: 'ERROR',pid=868386
Operations journal
Backups
Last database backup 4h ago
Latest per kind
| Kind | Status | Age | Size | Checksum | Retained |
|---|---|---|---|---|---|
| Database | Succeeded | 4h ago | 120 B | sha256 recorded | 2 copies |
| Environment | Never recorded | — | — | no checksum | — |
| Operations state | Never recorded | — | — | no checksum | — |
Recorded backups
| Created | Kind | Status | Artifact | Took |
|---|---|---|---|---|
| 2026-10-05 15:17 UTC | database | succeeded | /home/dome/paxx-deploy/shared/backups/database/paxx-pglite-20261005T151715Z.tar.gz | 29ms |
| 2026-10-05 15:12 UTC | database | succeeded | /home/dome/paxx-deploy/shared/backups/database/paxx-pglite-20261005T151216Z.tar.gz | 29ms |
Restores are not offered here at all — a restore is a destructive data operation (RED) and belongs in a shell with a human in front of it. Retention is applied by the backup script, not by this page.