Service dashboards: Postgres, Redis, NATS and more

The Services tab shows one card per database or service your app uses, from PostgreSQL and Redis to NATS, ClickHouse and Prometheus. Each card says whether the service is running, how big it is, when it was last backed up, and how to connect. Where ox can read the service, a Browse button opens a read-only view of its data.

What a service card shows

• Status: Running, Stopped or Failed. A failed service shows the reason on the card, and Logs opens its log.
• Version, memory, disk and connections, when the service reports them.
• Backup: when the last daily backup ran, or Off. Backups and restore covers restoring one.
• Connection: the variable your app reads, like DATABASE_URL. Its value stays hidden until you click the eye, and that click is written to your audit log, the same as on the Variables tab. The copy button copies the revealed value.
• More: backups, variables, logs, and a link to this page for that service.

Browse a service's data

The Browse button names what it opens: tables, keys, indexes, streams, collections or metrics. Every view reads only, shows a bounded page of rows, and cuts long values. Some kinds also have a query box:

A few pages can also change data, like deleting a Redis key or cancelling a Postgres query. Those stay off until you press Allow changes, which lasts 15 minutes, and every change is written to your audit log.

Why services stay private

ox binds every service to 127.0.0.1, so only your app and ox on the same server reach it. Many of these services, like Prometheus, Memcached and Chroma, have no password at all, and a public port would hand your data to anyone. ox never opens a service's port to the internet, and does not proxy a service's own admin UI. When you need one, run it as a custom service and give it a domain with its own login.

Add a service ox does not build in

Any service with a Linux binary or an apt package can run as a custom service: a [services.<name>] entry with a run command. It gets a card like any other. ox knows which service it is from its tool, packages or run, and explore = "nats" names the browser when none of those does.

[services.bus]
run      = "nats-server -js -a 127.0.0.1 -p $PORT -sd $SERVICE_DATA_DIR --auth $SERVICE_PASSWORD"
packages = ["nats-server"]
provides = { NATS_URL = "nats://${password}@${host}:${port}" }

The 50 most common services

A built-in type is a type in ox.toml; a custom service is a run entry as above. Opens is what its Browse button shows; Card means the card and its connection details only.

When a service does not start, Troubleshooting lists the messages ox prints, and Logs shows its own output.