Features
Everything StatusCheck does.
Start with a cloud check on any URL, host or port. Connect your vendors when you are ready. Get alerting, reporting and status pages that work the same way across all of it.
No integration required
Cloud checks
Watch any endpoint from outside your network, the same way your customers reach it. Nothing to install, no collector, no firewall change.
- HTTP(S) checks with the request method and expected status-code range you choose.
- TCP checks against any host and port — a mail server, a database, a VPN concentrator.
- Your own timeout and your own interval, set per check.
- Response latency on every run, with consecutive-failure tracking and the last error kept.
- Bulk import, so a hundred targets is one paste instead of a hundred forms.
- Every check is a monitored device: assign it to a site and use any alert rule.
One dashboard
Multi-vendor device monitoring
Connect a vendor account and StatusCheck discovers every device, classifies it, and starts polling. Your NOC view stops depending on which portal someone left open.
- UniFi, Meraki and Domotz today — live status, real polling, real device detail.
- Devices organized by client and site, with per-site rollups and uptime.
- Per-device polling intervals from one minute to twenty-four hours.
- Device identity survives re-connection: no duplicate rows when an integration is re-added.
- API keys go straight into an encrypted vault — never into a readable column.
The part everyone gets wrong
Alerting that stays quiet
A tool that pages you forty times on a Tuesday gets muted, and a muted tool gets canceled. Every default ships with one question answered first: how many notifications does this create on a normal day?
- Up/down rules with an offline threshold you set, plus metric threshold rules.
- Flap suppression, so a link that bounces twice does not page you twice.
- Severities and escalation chains, so the 3 a.m. rule is a different rule.
- Cooldowns and acknowledgement, so one bad afternoon is one conversation.
- Maintenance windows, so planned work never generates an incident.
Delivery
Every channel you already use
Notifications are only worth anything if they arrive where you are already looking.
- Email, Slack, Discord and generic webhooks.
- Fully custom webhook payloads — they can open tickets in anything that accepts JSON.
- Per-rule channel routing, so noisy rules and urgent rules go to different places.
Show your work
Reporting and status pages
The evidence that the thing you are being paid to keep up was, in fact, up.
- SLA and uptime reporting, scheduled and branded.
- No recipient limit — send the client report to everyone who needs it.
- Public status pages per site or per client, with the detail you choose to publish.
- Full status history per device, not a rolling window of the last hundred entries.
Built for people with clients
Tenancy, roles and audit
Multi-tenancy is not a tier here. It is how the database is built.
- Every client isolated at the database layer by row-level security.
- Role-based access, with unlimited users on every plan.
- Full audit log of who changed what.
- No per-site device cap: monitor a 4,000-device campus as one site if that is what it is.
How it behaves
The things you only notice in month two.
It sets itself up
Discovery, classification and sensible alerting defaults out of the box.
Tunable when you need it
Per-device intervals and per-rule thresholds when the defaults are not right.
Credentials in a vault
Encrypted at rest, decryptable only by the backend, purged when you disconnect.
Nothing to install
No agent, no collector, no inbound firewall rule.
Honest roadmap
What we do not do yet is published, with dates.
We monitor ourselves
Our own platform status is public, on the same product.
Monitored in the next ten minutes.
Start free — no card, no call, no “book a demo” wall.