Super Monitoring
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ideo Sp. z o.o. · supermonitoring.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Super Monitoring at a glance
- Vendor
- Ideo Sp. z o.o.
- Headquarters
- Incorporated in Poland source, captured 17 Nov 2026
- Data hosting
- In the EU by default source, captured 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Super Monitoring 2/5, the mean of 6 judges. Super Monitoring, an uptime and status-page service run by a Polish operator with hosting at IQ PL in Gdańsk, scores best on checks and locations (6-7 from five judges) and reports and reliability (6 from five judges): a broad catalogue including real-browser transaction checks that record a screenshot and the failed step, 60-second checks with multi-location incident confirmation, and permanent failure history with weekly and monthly reports and XLS export. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Super Monitoring, an uptime and status-page service run by a Polish operator with hosting at IQ PL in Gdańsk, scores best on checks and locations (6-7 from five judges) and reports and reliability (6 from five judges): a broad catalogue including real-browser transaction checks that record a screenshot and the failed step, 60-second checks with multi-location incident confirmation, and permanent failure history with weekly and monthly reports and XLS export. Pricing transparency is the weak point at 2-3 — the public pages show a free trial and one price, a $7/€6 net pack of 100 SMS notifications, so an annual cost cannot be computed. Judges split on status pages: high marks for unlimited pages on a custom domain with logo, custom CSS and four languages; the lowest mark for pages that list only selected checks, with no public information on subscriber notifications or component groups. Alerting and on-call and automation and teams sit at 4, sovereignty at 5-6, with no public information on escalation, on-call schedules, monitor creation through the API, or a published data processing agreement.
Speaks for it
- Transaction scenarios run in a real desktop or mobile browser and report failures with a screenshot and the failed step.
- Failure history is kept permanently unless purged, with weekly and monthly reports, PDF summaries and one-click XLS export.
- Unlimited public status pages run on your own domain via a CNAME record, with logo, colour scheme, custom CSS and four languages.
- The privacy policy names every subprocessor with a full legal address, including hosting at IQ PL in Gdańsk.
- Alerts go to any number of recipients by email and SMS with per-recipient quiet hours, at a published price of $7/€6 net per 100 notifications.
Held against it
- We found no public information on plan prices, monitor counts, seat costs or minimum terms, so an annual cost cannot be computed.
- We found no public information on escalation policies, on-call schedules, phone-call alerts or acknowledging an incident from an app.
- We found no public information on creating or editing monitors through the API, whose key is bound to one IP address and issued through support.
- We found no public information on single sign-on, two-factor authentication, audit logs or monitoring-as-code workflows.
- We found no public information on a published data processing agreement or security certifications.
Best for
- You run an online store and want a real browser to click through checkout, capturing a screenshot and the failed step when it breaks.
- You owe a client or agency a monthly uptime record — permanent failure history, downtime percentages and PDF summaries are documented.
- You want one branded public status page per client or product, on your own domain, in English, Spanish, German or Polish.
- Your procurement requires a subprocessor list naming each processor with its address, which the privacy policy provides.
Avoid if
- You must know your annual cost before committing — we found no public information on plan prices or monitor counts.
- Your on-call rotation relies on escalation policies, schedules or phone-call alerts — the documented channels are email, SMS, webhooks and RSS.
- Your security programme requires single sign-on, two-factor authentication or an audit trail — we found no public information on these.
- You manage infrastructure as code — we found no public information on monitor creation through the API, a Terraform provider or bulk import.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 2 of 5 |
| Status pages & incident communication | 2.5 of 5 |
| API, monitoring as code & team administration | 2 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 1.5 of 5 |
Checks, locations & failure confirmation
panel disagrees
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
The catalogue covers what my sixty client sites need — availability, keyword/content, web forms, page load, domain and SSL expiry with a warning before expiry, blacklists, file integrity and Core Web Vitals — plus transaction scenarios run in a real browser (desktop or mobile) with clicks, form fills and phrase verification, tests every 60 seconds, incidents confirmed from multiple locations before reporting, and response times broken into DNS, connect, pretransfer, starttransfer and redirect. We found no public information on cron or heartbeat checks, on named probe locations, maintenance windows or private agents, which is what holds it back from the top of the scale. 1 3 4 9 12
The SaaS Platform Engineer
The check catalogue is unusually broad: browser transaction scenarios with clicks, form fills and phrase verification, content, domain and SSL expiry, blacklists, change and file-integrity checks, plus database, mail and SIP protocols, tested every 60 seconds with failures confirmed from multiple locations and response times broken into DNS, connect and redirect components. The probe locations themselves are never named, and I found no public information on private probes, maintenance windows or sub-minute intervals, which is what keeps this short of what my team runs on. 1 3 4 9 12
The Customer Support Lead
The check catalogue is deep: transaction scenarios run in a real browser with clicks, form fills and phrase verification, alongside content, form, load-time, file-integrity, change, domain and SSL expiry, blacklist and Core Web Vitals checks, plus fourteen protocols from ping and port to MySQL and SSH, tested every 60 seconds with incidents only reported once confirmed from multiple locations. Probe locations are not named, and we found no public information on private locations inside a customer's network or maintenance windows that pause checks. 1 3 4 9 12
The E-Commerce Operations Manager
Transaction monitoring drives a real desktop or mobile browser through a click-and-fill scenario, registers the failure with a screenshot and the number of the broken step — that is what I need on checkout and the payment page, not just the homepage. Standard checks run every 60 seconds, a transaction scenario is set at 10, 30 or 60 minutes, and incidents are confirmed from multiple locations before being reported, across a broad catalogue from content and forms to SSL, domain expiry, blacklists, file integrity and website change. We found no public information on named probe locations, cron or heartbeat monitoring, private locations, sub-minute intervals or maintenance windows. 1 3 4 12
The Information Security Officer
The captured pages document a broad portfolio: availability with HTTP response codes, content and form monitoring, port-level checks across ftp, mail, database and other protocols, ping, DNS, SSL and domain expiry, blacklists, file integrity, change detection and browser-driven transaction scenarios with screenshots and step-level failure reporting, all on a 60-second interval with incidents confirmed from multiple locations and response times split into DNS, connect and transfer stages. We found no public information naming the probe locations, offering private locations inside our network, describing maintenance windows, or documenting cron or heartbeat checks, which is what keeps this short of the top of the range. 1 3 4 9 12
The Skeptic
A genuinely broad catalogue — availability, content, forms, load time, real-browser transaction scenarios with screenshots and step numbers on failure, domain and SSL expiry, blacklists, Core Web Vitals, change and file-integrity monitoring, plus protocols spanning ping, DNS, mail, telnet, SSH and databases — tested every 60 seconds with incidents confirmed from multiple locations and response times recorded with their components. But the probe locations are never named or counted, and we found no public information on sub-minute intervals, private locations inside the customer's network, cron or heartbeat checks, or maintenance windows that pause checks. 1 3 4 9 12
Alerting, escalation & on-call
panel disagrees
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
Immediate email and SMS alerts go to any number of recipients, with quiet-hour windows per contact, an option to resend daily until the problem is amended, and Slack, Discord, Google Chat, webhooks, Zapier and IFTTT on top; the SMS pack price of $7/€6 net for 100 notifications is published. We found no public information on phone-call alerts, escalation policies with timeouts, on-call schedules, acknowledging from the app or recovery notifications, so a 2 a.m. outage still rests on one person reading a text. 1 3 6
The SaaS Platform Engineer
Alerts go out by email and SMS (a pack of 100 notifications for $7/€6 net), webhooks, RSS and chat integrations including Slack, Discord and Google Chat, with per-recipient quiet hours and reminders resent daily until resolved. I found no public information on phone call alerts, escalation policies, on-call rotations or acknowledging from the app — as one of four people on a rotation, nothing here confirms anyone reliably gets woken. 1 3 6 9
The Customer Support Lead
Alerts go out by email, SMS, webhooks and RSS, with Slack, Discord, Google Chat, Zapier and IFTTT hooks, any number of recipients, per-recipient quiet hours for SMS, an option to resend daily until the problem is fixed, and SMS priced at 100 notifications for $7/€6 net. We found no public information on phone-call alerts, escalation policies, on-call schedules, acknowledgement from the app or maintenance windows that mute alerts. 1 3 6 9
The E-Commerce Operations Manager
Alerts go out immediately by email and SMS, also as webhooks and an RSS feed, to any number of recipients with per-person quiet hours, and a pack of 100 SMS notifications costs $7/€6 net — so the person on duty at night can be reached by text, and Slack, Discord, Google Chat, Zapier and IFTTT sit on the integration list. We found no public information on phone-call alerts, escalation policies, on-call schedules, alert grouping or acknowledging an incident from an app, so nothing documented wakes a second person if the first sleeps through the SMS. 1 6 9
The Information Security Officer
Alerts go out immediately by email and SMS, plus webhooks, an RSS feed and chat integrations including Slack, Discord and Google Chat, with unlimited recipients, per-recipient quiet hours, an option to re-send daily until the situation is amended, and SMS priced at $7/€6 net per 100 notifications. We found no public information on a push app, phone calls, forwarding to PagerDuty or Opsgenie, escalation policies, on-call schedules and rotations, recovery notifications or maintenance windows, so there is no documented path from an unacknowledged alert to the right person. 1 3 6 9
The Skeptic
Email and SMS alerts plus webhooks and an RSS feed, with Slack, Discord, Google Chat, Zapier and IFTTT integrations, any number of recipients, per-recipient quiet hours for text messages, an option to resend daily until the situation is amended, and SMS priced at 100 notifications for $7/€6 net. Every piece of on-call machinery is undocumented, though: we found no public information on phone call alerts, a mobile push app, escalation policies with timeouts, on-call schedules, acknowledge-and-resolve from the app, alert grouping, recovery notifications, or maintenance windows that mute alerts. 1 3 6 9
Status pages & incident communication
panel disagrees
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
Unlimited public status pages with my own domain via a CNAME record, per-page name, logo, colour scheme and custom CSS, in English, Spanish, German and Polish, each showing current status plus uptime and response-time charts over a week, month, quarter or year, with incident messages — that is close to the one-page-per-client set-up I want. We found no public information on subscriber notifications for the page, private or password-protected pages, scheduled maintenance announcements or component groups. 1 7 8
The SaaS Platform Engineer
Public status pages run on a custom domain via CNAME, show current status plus uptime and response-time charts over week to year periods, accept incident messages, and can be customised with logo, colour scheme and own CSS in English, Spanish, German and Polish, in unlimited numbers. I found no public information on subscriber notifications, scheduled maintenance announcements or private pages for internal teams, so the 3 a.m. update problem stays manual. 1 7 8
The Customer Support Lead
Unlimited public pages on my own domain via a CNAME, each showing current status plus uptime and response-time charts over a week, month, quarter or year, incident messages shown newest-first, custom logo, colours and CSS, and four languages — most of what I want on the table at a contract renewal. We found no public information on subscriber notifications, private or password-protected pages for the largest accounts, incident templates or scheduled-maintenance announcements. 1 7 8
The E-Commerce Operations Manager
Public status pages run on our own domain via a CNAME, are unlimited in number, carry our logo and our own CSS, and show current status with uptime and response-time charts over a week, month, quarter or year, plus incident messages we publish ourselves — available in English, Spanish, German and Polish, which suits our German-speaking customers. We found no public information on subscriber notifications, private or password-protected pages, component groups, scheduled maintenance announcements or embeddable widgets. 7 8
The Information Security Officer
Public status pages run on a custom domain via a CNAME record, show current status plus uptime and average response time charts over week, month, quarter or year, carry incident messages, accept a logo and custom CSS, come in four languages and can be created without limit. We found no public information on subscriber notifications by email, SMS or RSS, scheduled maintenance announcements, password-protected or private pages, or component groups, and nothing documented about how the page stays up if the main service is down. 7 8
The Skeptic
Unlimited public status pages on a custom domain via a CNAME record, showing current status plus uptime and average response time charts over week, month, quarter or year, with manual incident messages, a name, title, logo, colour scheme and custom CSS, and four languages (English, Spanish, German, Polish). The pages only list selected checks, and we found no public information on components and component groups, email or SMS subscribers, scheduled maintenance announcements, private or password-protected pages, embeddable widgets, or how the status page itself stays online when the main service is down. 1 7 8
API, monitoring as code & team administration
panel disagrees
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
There is a documented JSON API using API-key authentication for reading checks and failure events, with the key generated by contacting support and bound to a single IP address, plus webhooks, XLS exports, CMS plugins for WordPress, Drupal, Joomla!, Magento and PrestaShop, and sub-accounts with per-check access control depending on the plan. We found no public information on creating monitors through the API, bulk import, team roles, two-factor authentication, single sign-on or audit logs, so standing up two hundred monitors looks like handwork. 6 9 10 11
The SaaS Platform Engineer
There is a documented read API listing checks and events in JSON, with an API key bound to a single IP address and issued only by contacting support, plus webhooks, Zapier and IFTTT, CMS plugins, XLS export and plan-dependent sub-accounts with per-check access control. I found no public information on creating or changing monitors by API, a Terraform provider or any monitoring-as-code workflow, single sign-on, audit logs or two-factor authentication — so checks cannot live in version control next to the services they test. 6 9 10 11
The Customer Support Lead
There is a documented JSON API, with a key issued for one IP address on request to support, that lists checks and up to a year of their failure events, plus webhooks, CMS plugins and sub-accounts with per-check access control. We found no public information on creating monitors or status pages through the API, Terraform or CI workflows, roles, single sign-on, two-factor authentication or bulk import. 6 9 10
The E-Commerce Operations Manager
The documented API returns lists of checks and their failure events in JSON, authenticated by an API key issued for one IP address on request from support, with webhooks and integrations including Zapier, IFTTT, Slack and CMS plugins alongside it. Sub-accounts with per-check access control exist where the subscription plan allows them. We found no public information on creating or editing monitors through the API, monitoring-as-code or Terraform, single sign-on, SCIM, audit logs, two-factor authentication or bulk import. 6 9 10
The Information Security Officer
A documented REST API returns the checks list and per-check failure events as JSON, authenticated with an API key issued for one IP address and obtained through support, alongside webhooks, plugins for five CMS systems, and plan-dependent sub-accounts with per-check access control. We found no public information on creating monitors or status pages through the API, monitoring as code, single sign-on, SCIM, audit logs, two-factor authentication or bulk import — for our ISO 27001 programme, the missing single sign-on and audit trail are the blockers. 6 9 10
The Skeptic
A documented JSON REST API lists checks and failure events with a detailed-outages option and a maximum one-year range, but the key is bound to a single IP address and issued only by contacting support. Webhooks, chat and automation integrations, CMS plugins and plan-dependent sub-accounts with per-check access round out the picture; we found no public information on creating or changing monitors through the API, a Terraform provider or command-line tool, bulk import, user roles, two-factor authentication, single sign-on or audit logs. 6 9 10
Uptime reports, data & the vendor's own reliability
panel disagrees
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
Failure history is stored permanently with tables and charts, a totalling module reports failure counts and uptime/downtime percentages, summary PDF reports can be generated for all or a selected group of tests, weekly and monthly statements arrive by email, and history exports to XLS or the API (the API covering at most a one-year range per query) — the monthly per-client report I owe my customers is basically there. We found no public information on SLA reports with a stated method, response-time percentiles, the vendor's own status page and incident history, or published probe IP addresses. 9 11 12
The SaaS Platform Engineer
Failure history is kept permanently unless purged, shown as tables and charts with totals and uptime percentages, backed by weekly and monthly email reports, PDF summaries per group of tests, XLS export and API access to up to a year of events, plus root-cause artifacts like screenshots, HTML snapshots and HTTP headers. I found no public information on response-time percentiles, published probe IP addresses, the vendor's own public status page or an SLA with credits. 1 9 11 12
The Customer Support Lead
Failure history is kept permanently with tables and charts over any period, totals of failures and uptime percentages, weekly and monthly scheduled reports, PDF summaries per test group, one-click XLS export, and response times split into DNS, connect and transfer phases — exactly the record I would put in front of a client at renewal. We found no public information on the vendor's own status page, an SLA, post-incident reviews, response-time percentiles or published probe IP addresses. 1 9 11 12
The E-Commerce Operations Manager
Failure history is kept permanently unless we choose to purge it, recorded to one-minute accuracy, with a totalling module for downtime percentages, PDF summary reports per group of tests, and a weekly report each Monday plus a monthly statement — that is the paper trail I would put in front of the agency after downtime. History exports to XLS, individually or grouped, and response times break down into DNS, connect, pre-transfer, start-transfer and redirect components. We found no public information on SLA reports, percentiles, the vendor's own status page and incident history, published probe IP addresses or an SLA with credits. 11 12
The Information Security Officer
Every failure is recorded with time of detection, duration and failure type, kept permanently unless the user purges it, presented as tables and charts with uptime and downtime percentages, exportable one-click to XLS or through the API (limited to one year per query), and delivered as weekly and monthly reports plus PDF summaries; response times are broken into DNS, connect, pretransfer, starttransfer and redirect. We found no public information on SLA reporting and its method, percentiles, the vendor's own status page and incident history, its SLA, or published probe IP addresses — only a hint that the user agent contains "Super Monitoring" — and an auditor would ask for all of those. 4 9 11 12
The Skeptic
Failure history is stated to be kept permanently unless the user purges it, exportable one-click to XLS, group-exported in XLS and readable via the API, with weekly and monthly scheduled reports, PDF summary reports giving failure counts and uptime/downtime percentages, and response times broken into DNS, Connect, Pretransfer, Starttransfer and Redirect. The monitor's own trustworthiness rests on nothing public, though: we found no public information on SLA reports, response-time percentiles, published probe IP addresses, the vendor's own status page and incident history, or an SLA with credits. 9 11 12
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
The operator is a Polish business (VAT ID 5212118341) with hosting at IQ PL Sp. z o.o. in Gdańsk and a subprocessor list that names entities and addresses for payments (Blue Media, mElements, Stripe, PayPal), accounting (IFIRMA) and monitoring support (Reditus), while analytics and user-contact tools (Google, Meta, Mixpanel, OnboardFlow, tawk.to) sit outside the EEA with standard contractual clauses cited as the safeguard. We found no public information on a published data processing agreement or security certifications, and the server location follows from the hosting provider's registered address rather than an explicit location statement. 2
The SaaS Platform Engineer
The operator is a Polish entity, storage runs with IQ PL in Gdańsk, and the privacy policy names every subprocessor with its address — Polish and EU payment and accounting providers alongside Hotjar in Malta, plus Google, Meta, Mixpanel, OnboardFlow and tawk.to outside the EEA under standard contractual clauses or adequacy decisions. I found no public information on a published data processing agreement or security certifications, and the server location is inferred from the host's registered address rather than explicitly stated. 1 2
The Customer Support Lead
The operator is Polish, personal data sits on named Polish hosting (IQ PL), and the privacy policy lists every subprocessor with a full legal address, from Polish payment providers to Hotjar in Malta and PayPal in Luxembourg. Support chat and analytics run through providers outside the EEA, with standard contractual clauses named as the safeguard, and we found no public information on a data processing agreement or security certifications. 2
The E-Commerce Operations Manager
The operator is a Polish business and the privacy policy names its subprocessors with registered addresses — hosting with IQ PL in Gdańsk, Polish payment and accounting providers, PayPal in Luxembourg, Stripe in Ireland, and Google, Meta, Mixpanel, OnboardFlow and tawk.to outside the EEA with standard contractual clauses named as the transfer safeguard. We found no public information on a published data processing agreement, security certifications, or an explicit statement of where check results and on-call contact data are processed. 2
The Information Security Officer
The operator is a Polish sole proprietorship identified with VAT and REGON numbers, hosting sits with IQ PL in Gdańsk, and the privacy policy lists every subprocessor with full addresses — Polish and EU payment, accounting and monitoring providers alongside Google, Meta, Mixpanel, tawk.to and OnboardFlow outside the EEA — with standard contractual clauses and adequacy decisions named as safeguards. We found no public information on a published data processing agreement, security certifications such as ISO 27001 or SOC 2, or a self-hosted edition, and the server location is inferred from the hoster's registered address rather than stated, so the chain is visible but not fully evidenced. 1 2
The Skeptic
A Polish operator with a named Polish host (IQ PL in Gdańsk) and an unusually detailed subprocessor list giving addresses and registration numbers for payments (Blue Media, mElements, Stripe in Ireland, PayPal in Luxembourg), accounting (IFIRMA) and additional monitoring (Reditus in the Netherlands). Google, Meta, Mixpanel, OnboardFlow and tawk.to sit outside the EEA with only a general standard-contractual-clauses clause in the policy, the hosting location is inferred from the provider's registered address rather than an explicit statement, and we found no public information on a published data processing agreement or security certifications. 2
Pricing transparency
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
A free trial exists and the one price I can verify is $7/€6 net for an additional pack of 100 SMS notifications, with sub-accounts only noted as something the subscription plan may or may not offer. We found no public information on tier prices, how cost scales with the number of monitors or the check interval, seat or status-page costs, minimum term or VAT treatment, so I cannot compute what two hundred monitors would cost my agency per year. 1 3 6
The SaaS Platform Engineer
There is a free trial and one stated price — a pack of 100 SMS notifications for $7/€6 net — but the captured pages give no subscription tiers, monitor counts, interval or seat prices, so a real annual cost cannot be computed from them. I found no public information on plan pricing, the trial's limits, minimum term or VAT treatment. 1 3 6
The Customer Support Lead
A free trial is offered and SMS alerts are priced publicly at 100 notifications for $7/€6 net, the one cost my team could compute from these pages. We found no public information on plan prices, how cost scales with monitors or check interval, seats, minimum term or VAT treatment beyond the stated net figures. 1 3 6
The E-Commerce Operations Manager
The pages show a free trial, one concrete price — a pack of 100 SMS notifications for $7/€6 net — and a note that sub-accounts depend on the subscription plan. We found no public information on plan prices, monitor counts, intervals or seats per plan, minimum term, overage handling or VAT treatment, so the annual cost of monitoring my checkout cannot be worked out from the public pages. 1 3 6
The Information Security Officer
A free trial and one concrete price — a pack of 100 SMS notifications at $7/€6 net — are public, and the remaining SMS quota is visible in the account section. We found no public information on tier prices, how cost scales with monitors or check intervals, seats or sub-accounts, status pages, minimum term, overage handling or VAT treatment, so an annual cost cannot be computed from these pages alone. 1 3 6
The Skeptic
A free trial exists and one price is public — an additional pack of 100 notifications for $7/€6 net, with the remaining SMS quota visible in the account section — but the captured pages name no subscription tier prices, no monitor counts or intervals per plan, no seat or status-page costs, no VAT treatment beyond "net", no minimum term and no overage handling, while sub-accounts are gated on "your subscription plan" without a published plan list. A buyer cannot compute a real annual cost from these pages alone. 1 6
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in PL
unverified
Why unverified?The operator is a Polish sole proprietorship registered in CEIDG, and only the privacy policy (no imprint or terms) names it. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The location is inferred from the hosting provider's registered address rather than an explicit server-location statement, and the same policy allows personal data to be transferred to providers outside the EEA (e.g. tawk.to, OnboardFlow). |
2/4 pts | 2 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Super Monitoring
Is Super Monitoring European?
Not determined: the vendor’s pages as captured do not say where Super Monitoring is based. Its vendor, Ideo Sp. z o.o., is incorporated in Poland, per the vendor’s page captured 17 Nov 2026.
Where does Super Monitoring store data?
Super Monitoring stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 17 Nov 2026.
Does Super Monitoring have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Super Monitoring?
As of 19 Nov 2026, the panel rates Hyperping (3.5/5), Uptimia (3.5/5) and Checkly (3.5/5) highest among the other 23 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Hyperping (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Super Monitoring alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The operator is a Polish sole proprietorship registered in CEIDG, and only the privacy policy (no imprint or terms) names it.
- Weak sourcing — Hosting location. The location is inferred from the hosting provider's registered address rather than an explicit server-location statement, and the same policy allows personal data to be transferred to providers outside the EEA (e.g. tawk.to, OnboardFlow).
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page supermonitoring.com Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage www.supermonitoring.com Checked 17 Nov 2026 Details →
- 3 Checks, locations & failure confirmation — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 4 Checks, locations & failure confirmation — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 5 Alerting, escalation & on-call — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 6 Alerting, escalation & on-call — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 7 Status pages & incident communication — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 8 Status pages & incident communication — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 9 API, monitoring as code & team administration — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 10 API, monitoring as code & team administration — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 11 Uptime reports, data & the vendor's own reliability — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →
- 12 Uptime reports, data & the vendor's own reliability — found from sitemap www.supermonitoring.com Checked 17 Nov 2026 Details →