Fleet Management

Fleet Management monitors heavy machinery for several customer organisations out of one deployment. The interesting problem is not the charts, it is the authorisation.

Authorisation below the UI

Every request takes the same path: middleware gate, Zod parse, session lookup, a centralised policy, then a tenant-scoped repository transaction. Machine and group access-control lists constrain the query, so a user who guesses an identifier gets nothing back rather than an empty screen rendered over data they were never entitled to fetch.

Administration that cannot lock you out

Administrators create members, set their role and status, and grant access to individual machines or machine groups. Three rules are enforced in one policy module rather than scattered through handlers: nobody may administer their own account, nobody may assign a role carrying permissions they do not themselves hold, and the last active administrator can be neither demoted nor deactivated. A new member starts with no machine grants, and the panel says so plainly rather than letting an administrator wonder why the fleet looks empty.

Operational limits stated in words

Each tenant sets warning and critical limits per telemetry metric, bounded by the range the ingestion contract accepts. The machine view then states the resulting classification in words with a non-colour mark, because a reading that matters should not depend on the reader distinguishing amber from red.

Dashboards people actually build

Users add widgets from a five-kind catalogue, configure them, reorder and resize them, and save the layout. Every drag action has a button and keyboard equivalent, because a platform used in a workshop with gloves on cannot depend on precise pointer work. Charts are bounded for large series, reduced-motion aware, and always paired with a summary and a table so the information exists outside the picture.

Try it

Sign in at fleet.altixcode.com with [email protected] and the password demo. The account is a read-only Viewer in its own tenant: it can open every machine, its telemetry, events and maintenance, but it holds no write permission and cannot change its own password, so the demonstration stays intact for the next visitor.

Running in production

It deploys from its own repository to a self-hosted Coolify instance as a multi-stage Docker image that applies committed migrations before accepting traffic, runs as an unprivileged user, and answers a database-aware readiness probe. It holds a dedicated least-privilege PostgreSQL role rather than a shared superuser, takes nightly backups, and prunes telemetry on a retention schedule. Two hundred unit tests and eight browser journeys run against a real database, including the full member lifecycle: create, grant, sign in scoped to one machine, change password, deactivate.