System status
The parts that keep watch.
A monitoring product owes you honesty about its own health. These are Formitor's components; live operational status and incident history surface in your dashboard, where they can't go stale.
Formitor components
Dashboard (app.formitor.com)
The hub UI where you manage sites, forms and alerts.
The hub UI where you manage sites, forms and alerts.
Check runners
The workers that submit test leads and synthetic orders on schedule.
The workers that submit test leads and synthetic orders on schedule.
Delivery verification pipeline
SMTP delivery watching, render checks, deep browser checks.
SMTP delivery watching, render checks, deep browser checks.
Seed mailboxes
The dedicated inboxes that receive and classify tagged test leads.
The dedicated inboxes that receive and classify tagged test leads.
Alerting
In-app, email, Slack, Teams, SMS and webhook notifications.
In-app, email, Slack, Teams, SMS and webhook notifications.
Client status pages
Public read-only /s/<slug> pages served for your clients.
Public read-only /s/<slug> pages served for your clients.
This page is intentionally static. A status page that says "all systems operational" while being served from a cache is monitoring theatre, the exact thing Formitor exists to avoid. Real-time health, check queues and incident notices live inside the dashboard, and confirmed incidents that affect your monitoring are announced by email and in-app.
Your clients get status pages too.
Every client can have a read-only status page showing their forms are watched.