Vexor Live demo
Self-hosted · open source stack · early access

Monitoring that gets out of your way.

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.

Try the live demo Install it yourself

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.

  • Runs on your own hardware
  • Free trial through 2028
  • No sales calls, no seats
Vexor dashboard showing host and service counts, active problems and a host list

What it does

The things it's actually good at today.

Deploy agents from the browser

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.

Add a host, let it scan

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.

More checks when an agent's there

If a host already has an agent, Vexor notices and offers the deeper checks — CPU, memory, disk, services — as boxes you tick.

SLA & availability reports

Reports built from the monitoring you're already doing — uptime per host and service, no exporting to a spreadsheet.

Ship & search your logs

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.

Watch your certificates

Track TLS/SSL certificate expiry across your hosts and services, so a forgotten renewal never takes a site down again.

Business services & synthetics

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.

Sign in with what you have

Authentication goes through Keycloak / OIDC, so you can plug in your existing LDAP or Active Directory rather than a separate user list.

More than Linux and Windows

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, and there's even OpenVMS if you still run it.

Ask the AI what happened

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.

Keep your agents current

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.

Kubernetes and OpenShift, without installing anything

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.

  • Add a cluster the way you add a host. Pick Kubernetes or OpenShift in the same wizard, hand over the API address and a token, and Vexor probes the cluster and tells you what it can see before you commit to anything.
  • Twelve checks on Kubernetes, thirteen on OpenShift. Workloads below their replica count, pods crashlooping or stuck pulling an image, node pressure and drain state, PVCs stuck Pending, services whose endpoints have no ready backend — the usual shape of “the site is down but every pod looks fine”. On OpenShift it also watches cluster operators, the update status and MachineConfigPool rollouts.
  • A monitoring outage is not a service outage. If Vexor can't reach the cluster, the affected checks report UNKNOWN rather than CRITICAL — which would otherwise wrongly wipe out the measured availability of everything in the cluster at once.
  • Alerts, graphs and SLA reports, as usual. Cluster checks are ordinary Vexor services, so they flow into the same notification policies and availability reports as the rest of your estate.

Enterprise monitoring, without the enterprise

The kind of visibility big platforms sell for a small fortune — self-hosted, and simple enough to run on your own.

  • No per-host or per-metric billing. Monitor as much as your hardware can handle. One free trial license unlocks every feature.
  • Your data never leaves your network. Hosts, logs, metrics and credentials stay on your own server — nothing phones home to a SaaS.
  • Set up in an afternoon, not a quarter. No consultants, no onboarding project. Add a host, let it scan, and you're monitoring.
  • Built on proven open source. Naemon at the core, with a modern UI, API, log pipeline and SLA reporting layered on top.

How it works

The whole flow, start to finish.

  1. 1

    Add a host

    An IP or hostname is the entire form.

  2. 2

    Let Vexor scan

    It probes common services and suggests a baseline of checks to turn on.

  3. 3

    Deploy & watch

    Roll out an agent for deeper checks, then follow health, graphs and SLAs.

A look at the interface

Real screenshots from a live install, with the new role-based navigation. Click to enlarge.

Dashboard with host and service counts, active problems and a host list
Dashboard — status across your hosts at a glance.
Host list with status and details
Hosts — everything you monitor in one list.
Service checks with current state and plugin output
Services — checks, state and plugin output.
SLA report with availability bars per host
SLA report — availability per host and service.
Monitoring score grading how well each host is covered
Monitoring score — a 0–100 grade for how well each host is covered.
Host detail view with its service checks, current state and SLA summary
Host view — every check on a host, its state and its SLA.

Install

Two ways to run it. Pick a tab, copy, paste. Every install ships a free trial license — no sign-up.

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-setup

That'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-admin

Then open https://<host>/. Image: ghcr.io/sayonarase/vexor:latest. Compose file & caveats →

Vexor is a one-person project in active development. Every install gets a free trial license with the full feature set, valid until May 2028, so there's time to actually live with it. 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 question

Give it ten minutes

Try 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.

Open the live demo Install it yourself

Demo login demo / demo · read-only · resets hourly · no sign-up