Runs where your other sites run
sysx is self-hosted. It sits on infrastructure you control, alongside whatever else is already on that server.
What it's built on
sysx is plain PHP 8 and MySQL/MariaDB. No framework, no build step, no container orchestration. It's the kind of stack that runs comfortably on a modest VPS, the same way the rest of a small ops team's infrastructure does — nothing about sysx needs more care than the servers it's watching.
| Language | PHP 8 |
|---|---|
| Database | MySQL or MariaDB |
| Build step | None |
| Orchestration | None — runs as a normal web app on a server you already have |
| Data location | Stays on your server, throughout |
How servers report in
Two ways of collecting telemetry, so every box in an estate can be covered regardless of what's already running on it.
Shell agent, pushed from cron
A small shell script run from cron. Because it runs as root, it can identify the process behind each open port, not just the fact that something is listening.
PHP endpoint, polled over HTTPS
For hosts already running a web server and which don't need a separate agent. sysx polls the endpoint and collects the same readings.
Neither mode needs a daemon or an agent framework — nothing beyond what a minimal Linux install already has.
AI features
The AI-backed features — the scheduled estate review and the chat assistant — call out to a model of your choosing. Model choice is configurable, and the routine analysis is designed to run on inexpensive models, so running costs stay low.
The deterministic monitoring checks do not depend on the AI in any way, and continue to function without it.
Want to talk through fitting sysx to your infrastructure?
Tell us how many servers you look after and who looks after them, and we'll take it from there.
Enquire about a deployment