Once, per company. The repository, and every version after it.

Any host that runs containers plus PostgreSQL 18+. The included compose file boots Postgres, migrations, the app and the worker in one command. Bare-metal works too: Node 20.9+, two processes (next start and the worker), one database. No Redis, no message broker, and the Anthropic key for AI features is optional.

The first question for any self-hosted tool. The sane setup: run Vigil on a small VPS outside the infrastructure it watches, so it never shares fate with what it monitors. For the meta-level, point any free external ping at your Vigil instance. You can also run probe agents on machines you already own and require several to agree before an incident opens, which is multi-vantage confirmation without a vendor in the middle. What Vigil deliberately does not have is a probe network operated for you: if you need checks from ten regions with no ops of your own, a hosted service is the right tool, and the comparison pages say so.

Yes. Per monitor you save one recovery action: a signed POST to an endpoint you control, a restart hook or a runbook trigger. A 76-line example receiver ships in the repo. Before firing, the worker re-probes to confirm the failure is still real; after firing, it probes again. Success is observed, never assumed. Attempts are bounded per incident, capped per day against restart loops, and every attempt lands on the incident timeline with its outcome. Optionally it holds email and webhook alerts while it works: a verified recovery pages nobody, a failed or overdue one pages immediately. All of it is off until you turn it on.

No. Vigil imports from fifteen monitoring systems, among them Better Stack, Pingdom, UptimeRobot, StatusCake, Datadog Synthetics, Checkly, New Relic Synthetics, Grafana Cloud Synthetic Monitoring and an Uptime Kuma database file. Previewing is a real import that was rolled back rather than an estimate. What does not come across gets a line with the rule that was applied: credentials are not copied out of your old account, and a browser journey or a k6 script is refused rather than approximated.

Pay by card on Whop, a hosted checkout where Whop is the merchant of record, so a real company handles the payment and issues the receipt. Enter your GitHub username at checkout and the private-repo invite fires within seconds, with nobody in the loop. Questions before or after? A real person, Maria, answers.

Private access to the full repository: application source, worker, test suites, Docker and CI setup, seed and screenshot tooling, this landing page, and all documentation. Plus every version published afterwards, at no further charge.

One license per company: unlimited production deployments for your own business and full private modification rights. Agencies and MSPs: serving any number of clients, their monitors, their branded status pages, from your own installation is covered, and clients access it as end users with no extra licenses. Only when a client receives their own deployment or copy does it become one license per client, and one is included. Not allowed: reselling the source or republishing it as a template or boilerplate.

No, nothing, ever. $149 once, per company. Every version published after you buy is included, there is no renewal, no maintenance fee and no license key that expires. Until July 2026 this page offered an optional $99 a year for continued updates. It was removed: $99 against a $149 purchase is a two-thirds maintenance rate, which is a subscription wearing a perpetual license's clothes.

No. Everything runs on your infrastructure against your Postgres. The only optional external call is the Anthropic API for AI postmortems, billed on your own key and disabled by default.

The codebase is layered for exactly this: domain logic lives in src/modules, UI in src/app and src/components, and both are thin over a documented service contract. The upgrade guide describes a rebase-friendly workflow, and database changes always ship as ordered SQL migrations.

Partly, and this answer was wrong until July 2026. Vigil Core is free software under Apache-2.0, with all 40 of Core's check types, incidents, status pages, four team roles, the audit page and the observation ledger. For a while it really was far behind, because Core was copied out by hand and nothing built one edition from the other. That is fixed. Both editions are 1.29.0, cut from the same commit by a script that runs in a required build job.

Yes. Strongest first: click through the interactive demo, which is the real app on seeded data, with no login and read-only. What you see is exactly the product you receive. The full license is readable in advance too, so nothing is hidden until after purchase.