Monitor. Investigate. Act.
Open-source fleet operations: observe and control your baremetal servers, VMs, and containers from one place — and talk to your fleet through AI chat.
Monitor. Investigate. Act.
Open-source fleet operations: observe and control your baremetal servers, VMs, and containers from one place — and talk to your fleet through AI chat.
One platform that both watches and acts. Monitoring shows you what's happening; the control plane lets you do something about it — through a gated command catalog, with an AI chat grounded in live telemetry as the primary interface. Named after the Roman night watch that did both.
Mixed fleets — a few baremetal boxes, VMs on top, containers on top of those — without stitching together one tool for graphs, another for inventory, and SSH for everything else.
Many clients, one platform: every client is a tenant with its own fleet, users, and AI account, strictly isolated from the others.
"Which host is running out of disk?" beats building another dashboard. Questions first, dashboards second.
Every node, live status, automatic host↔guest topology.
CPU, memory, disk, network per host and container.
Questions answered from live telemetry, inventory, topology.
Gated command catalog, only where an approved control agent runs.
Search any file across every host in seconds.
Token → pending → approve; telemetry first, control on trust.
What each tenant costs in storage — file index, event log, file store — plus fleet counts, snapshotted with history. A system report covers the whole deployment.
Agents render thumbnails for millions of images in place and stream only the thumbnails — browse a NAS full of photos without pulling a single original.
Publish a signed release; agents pull it, verify the signature, and swap themselves across the fleet — no SSH, no orchestration.
A real tail -f on any log — or any container — on any host, streamed
to the browser. Mix several sources into one pane, files and containers across
servers, each in its own color with a legend; filterable, one click to save a
capture. No SSH.
Every docker/podman container in the fleet: running counts per server, CPU and memory per container, live logs, restart/stop/start from the browser. The host agent reads cgroups and the runtime socket — nothing gets installed inside containers.
Threshold rules per host, per label group, or fleet-wide — with severity levels; critical alerts are built to ring through Do Not Disturb.
Tag servers freely — prod, nas, role:db — then filter, search, and scope alert rules by label. A group of servers is one chip away.
Admins and users per tenant — and per-user host hiding: a hidden server vanishes from lists, file search, thumbnails, even the AI's answers. Your private NAS in a shared fleet stays yours.
Link a phone by scanning a QR — no password on the device. The fleet, charts, AI chat, live log tail, and photo browsing in your pocket, with the same per-user permissions as the web.
Not mockups — real numbers from the 27-host fleet Vigiles runs itself on.
Two static Go agents per host — telemetry (metrics, FS inventory, in-place thumbnails) and control (gated commands, installed only where allowed), both signed and self-upgrading. FastAPI services behind one mount, PostgreSQL per service, Redis Streams ingest, OpenSearch file index. Multitenant by construction.
Apache-2.0, built in the open. Phase 1 — enrollment, telemetry, fleet topology, AI chat with read tools, file-system inventory — is delivered. Phase 2 is landing: gated action commands, self-upgrading agents, in-place image thumbnails, and per-tenant usage & cost reporting are already in. If you run a fleet and want to watch it and act on it from one place — or want to help build that — welcome.