Self-hosted infrastructure monitoring

See the failure.
Verify the recovery.

Vigil monitors your services, runs the recovery actions you allow, and checks that they worked. Every incident leaves a record you can inspect.

Explore the product tour Compare editions

For engineers, infrastructure teams and agencies.
Run it on your servers. Keep control of your data.

Detect a failureTrigger your actionVerify with a new probeFollow a real sample →

Inside Vigil / Monitor overviewOpen the full monitor list ↗

Vigil monitor list showing service status, uptime, response times and check intervals — Monitor overview excerpt · actual interface with seeded data, not customer results

Self-hosted Your servers and dataOpen-source Core Apache-2.0$149 Commercial Once, per company

From detection to resolution

An alert is the beginning.
A verified outcome is the goal.

Monitoring, recovery and evidence belong in the same workflow. Vigil connects them without taking control away from your team.

01 / Monitor

Know what failed.

Check endpoints, databases and services from infrastructure you control. Open an incident after the failure window you set.

Explore monitoring →

02 / Recover

Act within your limits.

Recheck the failure, send a signed trigger to your recovery endpoint, then probe again. Set attempt limits and cooldowns.

How recovery works →

03 / Record

Keep the evidence.

See the failed observation, the last success, and what changed. Recovery attempts and their outcomes stay on the incident timeline.

Inspect incident evidence →

Automatic recovery is a Commercial feature, off by default. Exhausted or failed recovery leaves the incident open for a person.

Verified recovery · real product tour

See the check
that closes the loop.

The Auth Service sample records the action, a successful verifying probe and automatic resolution. A separate example shows what happens when recovery runs out of attempts.

Follow the verified recovery →

Actual product interface · seeded Auth Service scenario, not a performance claim · Read the full timeline → · Read the verifying probe outcome →

Outcome / recovered

The new probe confirms it.

The recovery record marks the attempt as succeeded only after the target responds again. The incident then closes.

Inspect the recovery record →

Outcome / needs a person

The limit stops automation.

Checkout’s two attempts fail verification. Its incident stays open and a responder takes over the DNS repair.

Inspect the exhausted-recovery example →

Built for the infrastructure you run

Keep your tools.
Connect the work.

Monitor your stack, reach the right responder, and move from your existing system with a comparison you can inspect.

Your services: HTTP, TCP, DNS, TLS, databases, containers and more. See supported checks →
Your team: Notification channels, on-call schedules and escalation policies. Explore operations →
Your migration: Preview an import and run in shadow mode before enabling alerts or automation. Plan a migration →
Your clients: Separate workspaces, branded status pages and client reports in one Commercial install. Vigil for agencies →

Two editions. Your choice.

Start with Core.
Add the operational layer.

Open source

Vigil Core

Free Apache-2.0

Monitoring, incidents, evidence and public status pages for one organization per install.

Explore Core →

Commercial

Vigil Commercial

$149 once, per company

Verified recovery, remote probes, runbooks, on-call, objectives and multiple client organizations.

Compare editions →

Both editions run on your infrastructure. Commercial includes source access, private modifications and every future published version. Hosting is your responsibility.

Your infrastructure. Your record.

See how Vigil handles an incident.