About Norvane
What this is, who builds it, and how to reach a person.
Norvane is an n8n monitoring tool for agencies.
What Norvane does
n8n tells you when a workflow fails. Norvane tells you when it silently stops running — across every client instance you manage.
n8n raises an alert when a workflow errors. It says nothing when a workflow simply stops running — a schedule trigger that quietly deactivates, an instance that restarts and loses state, a webhook source that stops firing. There is no error to catch, so an error workflow cannot help. Norvanewatches for the absence instead: it infers each workflow's expected cadence from its cron configuration and its execution history, and opens an incident when a run that should have happened did not.
It is built for the agency shape of the problem — one n8n instance per client, ten clients, ten dashboards nobody checks. Every instance lands on one screen, worst first, and each client can be given a status page that shows their automations are being watched.
Who builds it
Norvane is built by Abdullah Hassan. It is a small, independent product with a narrow remit: reliability for n8n fleets. It is not a portal, not a hosting service, and not a replacement for the n8n interface.
Two rules shape the product. Never fake a signal — a monitoring tool that draws a tick it cannot prove is worse than no tool, so the interface shows unmonitored ground as unmonitored rather than as healthy. And never hold your data hostage — remove an instance and its mirrored data goes with it.
How to get in touch
Email hello@norvane.dev for questions, bugs, or anything about how monitoring works. Mail goes to a person, not a queue.