Vexor keeps an eye on your servers, containers, network and services. Add a host and it scans for the obvious things; deploy an agent from the browser when you want deeper checks. Logs, SLA reports and certificate expiry are built in — and it runs on your own hardware, so your data stays with you.
No sign-up. Open the live demo and sign in with demo / demo — read-only, resets every hour. Or self-host in three commands on Rocky 10, or one Docker image anywhere.
The things it's actually good at today.
Push the NSClient++ (Windows) or NRPE (Linux) agent to a host from the UI — and bundle a few extra packages with it if you need to. Windows hosts are installed remotely over SMB with an admin credential, including Windows 11 24H2 and Server 2025.
Type an address and Vexor probes for ping, SSH, RDP, FTP, HTTP and other common services, so you start with a sensible baseline instead of a blank page.
If a host already has an agent, Vexor notices and offers the deeper checks — CPU, memory, disk, services — as boxes you tick.
Reports built from the monitoring you're already doing — uptime per host and service, no exporting to a spreadsheet.
Point a lightweight shipper at your files and Windows event channels, then search, live-tail and alert on log lines — with anomaly detection when something spikes.
Track TLS/SSL certificate expiry across your hosts and services, so a forgotten renewal never takes a site down again.
Roll up the checks behind an application into a single business-service health, and add synthetic probes that walk a user journey the way a customer would.
Authentication goes through Keycloak / OIDC, so you can plug in your existing LDAP or Active Directory rather than a separate user list.
SQL Server gets a deep dive of its own — point-in-time snapshots, per-database drill-down and an A/B comparison of two moments. Proxmox, VMware and XCP-ng are read-only checks, network devices get config backup with diffs.
Agentless over SSH with a least-privilege account. CPU per processor and per process, memory and pool, paging and lock manager, disk errors and shadow sets, queues, intrusion attempts, process quotas, licences, VSI updates and certificate expiry — and it cleans up after its own SSH sessions on a busy host.
Summarise an incident timeline or a noisy stretch of logs in plain English. Run Ollama locally so nothing leaves your network, or bring your own OpenAI, Claude, Gemini or Azure key if you'd rather.
Choose which NSClient++ build gets deployed — fetch a stable release from upstream, upload your own MSI, or stay on the bundled one. Previous versions stay in the registry, so a bad build is one click to roll back.
Every check with performance data gets a graph on a real time axis, with readable units. If a host stopped answering, the gap is shaded and labelled with how long it lasted instead of hidden behind a straight line.
Host credentials, notification tokens, cloud keys and webhook secrets are encrypted in the database and kept out of logs and API responses. Every bundled component — sign-in, log pipeline, libraries — gets security updates through plain dnf update.
Give Vexor a read-only ServiceAccount token and it reads the cluster's own API. Nothing is installed in the cluster, nothing is changed in it, and no workload runs there on Vexor's behalf.
The kind of visibility big platforms sell for a small fortune — self-hosted, and simple enough to run on your own.
Vexor is updated often. The highlights of the last few months:
Notification tokens, channel settings, cloud keys and webhook secrets are encrypted in the database, and tokens no longer appear in logs.
Every feature is available, with no host limit and nothing that expires.
Remote agent install over SMB works on Windows 11 24H2 and Windows Server 2025.
Disk errors, shadow sets, pool memory, intrusion attempts, process quotas, resource waits, system resources, account expiry and certificates — plus per-processor and per-process CPU alerts.
A real time axis, readable units, and periods without data shaded instead of bridged by a straight line.
Generate, reveal and rotate the log ingest token in Vexor itself, with a list of the machines that will need the new one.
The whole flow, start to finish.
An IP or hostname is the entire form.
It probes common services and suggests a baseline of checks to turn on.
Roll out an agent for deeper checks, then follow health, graphs and SLAs.
Real screenshots from a live install, with the new role-based navigation. Click to enlarge.
Two ways to run it. Pick a tab, copy, paste. No license key, no sign-up — every feature is included.
On a fresh Rocky Linux 10 (or RHEL 10-compatible) server, run as root:
# 1 — add the Vexor repo (also pulls in EPEL, CRB and the GPG keys)
dnf install -y https://repo.vexormon.com/vexor-release-latest-el$(rpm -E %rhel).rpm
# 2 — install the full server (api, ui, naemon, keycloak, db, graphs…)
dnf install -y vexor-server
# 3 — first-run setup (databases, passwords, services, firewall)
vexor-setupThat's it — three commands, no manual repo or dependency wrangling. Supported on x86_64 Rocky / AlmaLinux / RHEL / Oracle Linux 10. Full notes & minimal install →
Prefer Docker, or running on Ubuntu/Debian? The all-in-one image runs the same stack:
# clone and start
git clone https://github.com/sayonarase/vexor-docker
cd vexor-docker
cp .env.example .env # set VEXOR_PUBLIC_URL to how you'll reach it
docker compose up -d
# grab the initial admin credentials (written on first boot)
docker compose exec vexor cat /etc/vexor/.initial-adminThen open https://<host>/. Image: ghcr.io/sayonarase/vexor:latest. Compose file & caveats →
Vexor is a one-person project in active development. It needs no license: every feature, no host limit, nothing that expires. If you run servers and try it, I'd like to hear how it goes — bug reports and rough edges included.
Email me / ask a questionTry the live demo in your browser, or self-host it and point it at a real server. Either way, I'd genuinely like to hear what you think.
Demo login demo / demo · read-only · resets hourly · no sign-up