Lovable’s monitoring and Vigilia
Lovable’s project monitoring and Vigilia
Lovable now checks your project for problems on a schedule, inside the editor. Vigilia watches your live app as visitors use it, and hands every fix back to Lovable. They overlap less than the names suggest. Here is what each does, from Lovable’s own documentation as of October 2026.
Side by side
| Lovable project monitoring | Vigilia | |
|---|---|---|
| When it looks | On a schedule: by default daily at 6:00, only if the project was edited since the last check. Weekly is an option. | All the time. A new error is explained within seconds of the first visitor hitting it. |
| What it looks at | Your project’s code, and recent errors from visitors. | Errors, failed and slow requests, dead buttons and page speed from every visitor; uptime; server errors (Pro). |
| Uptime | Not mentioned in its docs. | Checked every 5 minutes on Free, every minute on paid plans, plus key pages such as checkout. |
| What you get | Findings above the project chat, and an email to the owner for important ones. “Try to fix” asks Lovable to fix it. | A plain explanation, who it affects, and a fix prompt for Lovable, by email (Slack and Discord on paid plans), or read by Lovable directly over MCP. |
| After the fix | A finding’s status changes when you act on it. | Watches real traffic and tells you the fix held, or reopens the incident if the error comes back. |
| Where it works | Lovable projects. | Any web app: Lovable, Bolt, v0, Cursor, Claude Code, hand-written; any host. |
| Cost | Pro, Business and Enterprise workspaces; each completed run uses credits. In beta. | One app free with 10 AI diagnoses a month; errors it already knows are explained for free. |
When Lovable’s monitoring is enough
For an app you are still changing every day, with few real users yet, a daily review in the editor catches broken logic in the code you just wrote. Lovable’s docs are frank that it doesn’t replace testing and can flag working behaviour as broken.
When you want Vigilia too
- Real users are on it. A problem at 9 p.m. reaches you at 9 p.m., not at 6:00 the next day, and only if you had edited the project.
- It’s down, not broken. Downtime, an expired certificate, a provider outage: Vigilia checks and says which.
- You want proof the fix worked. Vigilia confirms it with real visitors, so a fix that didn’t take is caught.
- Not everything is in Lovable. A second app built with Bolt or Cursor, or a client’s app, in the same place.
They work fine together: Vigilia is one script tag, and its fixes go to Lovable either way. How Vigilia fits into Lovable.
Watch your Lovable app for free
One app, uptime checks and a public status page. No card.
Questions
Does Lovable’s project monitoring check whether my app is up?
Its documentation doesn’t mention uptime. It reviews the project’s code and recent visitor errors on a schedule. Vigilia checks that the app answers every few minutes, and every minute on paid plans.
Can I use both?
Yes. Vigilia is one script tag in your app, and it hands its fix prompts to Lovable, by copy-paste or with Lovable reading them over MCP.