One install, every client, one license
Monitoring is a service you sell.
One self-hosted install, a branded status page per client, and a report at the end of the month with your studio's name on it. It turns "is my site up?" from a panic email into a line item on your invoice.
One price, once. Whatever you charge is yours.
Your clients already expect you to notice when their site is down. Whether that expectation has a line on the invoice is your decision, not a feature. What Vigil gives you is the thing that makes the line defensible: an isolated workspace per client, a status page in their name, and a monthly report with the numbers and the method printed on it.
A worked example. Substitute your own two numbers; the only fixed figure is the license.
Your server, your prices, your brand on every client page. Vigil takes no share and adds no per-client or per-monitor fee, so the second row is the whole software cost at any number of clients.
Eight things, stated plainly.
Everything below is in the commercial edition today, running on your own server. There is no agency tier, no add-on and nothing that arrives later.
A report you can defend line by line.
Pick a month, press generate. Your logo, your color, the client’s name, and the numbers underneath, uptime, downtime, incidents, what was acknowledged and when, what the recovery runtime tried and whether it worked.
The methodology is printed on the document. So are the gaps: time nothing observed is reported as unmeasured and left out of the percentage, rather than quietly counted as good. A client who reads the small print finds the same answer as one who reads the headline.
PDF is your browser’s Print dialog. There is no rendering service to pay for, and the styling travels inside the file, so it looks the same after it has been emailed twice.
Read the whole thing, a real report from the demo instanceMost monitoring is built for one operator, not one agency.
None of these are bad tools. They are shaped for a different job, and the difference shows up in the same place every time: what happens when the second client arrives.
Shaped for one account
The free plans are real, and if you are watching your own handful of things they are often enough. What they are not shaped for is the structure of agency work: a separate audience per client, logins for your team, and something to send at the end of the month. Read the current limits on the vendor's own pricing page. They move, and we would rather you check them there than trust a number we typed.
Priced per page
Hosted status-page products are generally priced per page, per month, which is fine for one page and becomes a recurring line per client at agency scale. Prices change, so compare them yourself. Vigil's shape is the claim we will make: one install publishes every client's page, and adding the next client does not change the bill.
One admin account
Genuinely good, free, and the thing most agencies are already running. It has a single admin account, so everyone who can see one client can see all of them, and there is no read-only login to hand a client. Vigil ships four roles and a workspace per client, and imports your existing setup. The full comparison is pinned to a specific Kuma release with the method written down.
Hosted tools bring probes in many regions and somebody else on call. You bring one server, and own everything on it.
One command, on a server you already have.
Vigil is two processes and a Postgres, shipped as a Docker Compose file. You bring the machine (any $5 VPS is enough), run docker compose up -d, and the migrations apply themselves. The quick start is the whole procedure, and it is about ten minutes.
Nobody needs access to your server, and no part of this waits on a person. That is deliberate: your clients' monitoring should not depend on somebody else's calendar, including ours.
Vigil $149Asked by agency owners, answered plainly.
No, not for the normal agency setup. One $149 license covers your installation with unlimited tenants: every client gets their own organization, monitors and branded status page on your install, and they access it as end users. You only need an additional license when a client receives their own separate deployment or a copy of the source, and the first such delivery is included, so it's one license per client after that. Full terms in the License, readable before you pay.
Status pages are branded per tenant, the client's name, served from your domain. The one Vigil mark is a small "Powered by Vigil" line in the page footer; you own the source, so it's a single line to remove if you want the page fully unbranded (the customization guide points to it). You can put your logo on the sign-in screen too. Monitoring becomes your product, priced by you.
No service. The report is a page your own install renders, and PDF is your browser’s Print dialog. The document is laid out for A4 and Letter and carries its styling inside the file, so it survives being saved and emailed. Pick a month, press generate, send it.
Saved reports are frozen: renaming a monitor, resolving an incident late or letting retention prune old checks does not move a report you already sent, and the database refuses to update the row at all. Each one carries a sha256 of its own contents. Read a real one. It is a saved copy of what the demo instance generated, gaps, caveats and all.
We do not know, and anyone who quotes you a range has not seen your market or your clients. It is your price. What we can tell you is the only number on our side of it: $149 once, per company, with no cut of what you bill and no per-client or per-monitor fee. Whatever the number is, the monthly report is what makes it a line a client reads rather than queries.
Yes, since 1.9.0 (this page used to say "on the roadmap"; it shipped). Visitors to a public status page can subscribe by email (double opt-in, one-click unsubscribe) and get a message when an incident opens, posts a public update or resolves. Internal notes and quietly self-healed incidents never reach subscribers. Your team keeps its own alerts by email and any of the 25 native provider types, Slack to PagerDuty to ntfy.
Then this is probably the wrong tool today, and we would rather say so than sell you a weekend you did not want. Vigil is self-hosted: you supply the machine and you keep it running. It is deliberately low-touch: two processes and one Postgres, started by one compose file. It is not no-touch, and there is no managed version to buy instead. If nobody on your side will own a server, this is the wrong purchase.
You do. It is your server; that is what owning it means. The stack is deliberately boring: two processes and one Postgres, shipped as docker compose, with 4706 tests and an upgrade guide. Put it on a small VPS outside your client infrastructure so the monitor never shares fate with what it monitors. Every future version is included in the license.
Your clients, on your server, with your name on the report.
The license is the license: $149 once, per company, unlimited clients on your own install. A migration is a separate job, quoted after we have looked at what you are moving.