How Ravnsight works

Ravnsight watches your website from the outside and tells you when something is wrong – before your customers do. It checks that pages load, that certificates and domains are valid, that DNS has not changed, and alerts the right people when an outage is confirmed.

For WordPress sites, the Ravnsight Detective plugin (coming) adds the inside view: errors, plugin changes and performance, correlated with what the monitor sees.

Yes. The Free plan monitors one site every 5 minutes with HTTP, certificate and domain-expiry checks, content checks and e-mail alerts, with 30 days of history. No card, no trial clock. Upgrade to Pro when you need more sites, 1-minute checks, more monitor types or Slack/SMS alerts.

Sign in, click Add site and enter the address. We create an HTTP monitor for the start page and a certificate check right away; the first check runs within a minute. Then open the site page to add more monitors and decide who gets alerted.

A single failed check never alerts anyone. When a check fails we retry after 10 and 20 seconds from the same location, then ask a second location in another country to confirm. Only a confirmed outage becomes an incident and an alert. If your site is slow but answering you see degraded instead – visible, not paged.

An AI reading of everything we have collected about your site – uptime, incidents, certificates, detected technologies and the homepage snapshot – summarising the current state and pointing out the most likely causes with an honest confidence level. Connect the Detective plugin and the analysis also reads the site from the inside: PHP errors, the change timeline and the environment. It never claims something is a confirmed cause unless it could be reproduced.

From Ravnsight nodes in the EU (Germany, Finland, Sweden) with more regions on the roadmap. Every check records where it ran. Nodes only pull work from us – we never open connections from the cloud into your infrastructure.

Pro checks every minute instead of every 5, monitors 5 sites, unlocks DNS, API, TCP and heartbeat monitors, critical-page monitors, alert channels beyond e-mail (Slack, SMS, webhooks…), staged alerts with reminders, maintenance windows, status pages and reports, and keeps 13 months of history. Agency and Partner are Pro for many sites.

One domain you monitor. A site can have many monitors (several pages, certificate, domain, API, heartbeat) without using more slots. Paused sites do not count.

Upgrades apply immediately and are prorated. Downgrades take effect at the end of the current period; if you have more active sites or logins than the new plan allows we ask you to pause some first. Yearly plans cost ten months.

Ready-made components (uptime, monitors, incidents, alerts, Detective findings and an all-in-one dashboard) you paste into your own page to show live monitoring data from your account — no coding, works on any platform.

No. You create a widget token under Settings → Widgets and that is the only credential you need. You never create or expose an API key, and the token is read-only.

A token only exposes read-only monitoring data — never settings, billing or the ability to change anything. The allowed-domains list stops other sites from framing your widget in a browser. Because the token sits in your page HTML, treat it as semi-public: anyone who can view the embedding page can read the data, so embed on pages you trust and revoke a token any time.

No. It reads and records. It never updates, deactivates, cleans or optimises anything – not even when it is sure what the cause is. Isolation testing applies changes only inside an isolated session that requires a signed cookie and an administrator login, and it never writes to the plugin list in the database.

Not for the free plugin – it works entirely inside WordPress and makes no external requests until you opt in. An account (Pro) is needed to connect the site and get the correlation with external monitoring.

The budget is 5 ms and 2 MB per uncached front-end request, enforced by an automated benchmark in our build. If a release breaks the budget it does not ship.