Uptime Monitoring & Status Pages
Pulsetic
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Designmodo Inc. · pulsetic.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.
Pulsetic at a glance
- Vendor
- Designmodo Inc.
- Headquarters
- Incorporated in United States source, captured 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Pulsetic 3/5, the mean of 6 judges. Pulsetic, an uptime monitoring and status page service from Designmodo Inc. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Pulsetic, an uptime monitoring and status page service from Designmodo Inc. of New York, scores highest on status pages and pricing transparency, both at 7. Status pages publish on a custom domain with one CNAME record, white-label, with 10,000 email subscribers included and additional subscribers at $0.01 each; every tier and add-on is public — Free $0, Solo $9, Team $19, Organization $49 per month, teammates at $8 each, SMS and calls at $0.10 per alert — though we found no public information on VAT treatment. Checks and locations, alerting and on-call, and reports and reliability sit at 6-7, crediting confirmation from a second location before an alert fires and retention stated per plan up to five years. Sovereignty, at 4, is the outlier: the controller is Designmodo Inc. under New York law, personal data is stored in the United States and the European Union, and the captured pages name no EU entity. Scores vary by at most one point per category; the recurring reservation is that on-call scheduling and escalation run through the SIGNL4 integration rather than the product itself.
Speaks for it
- A failure is re-checked and confirmed by a second location before an alert fires, with a screenshot of the page at the moment it failed
- Status pages publish on a custom domain via one CNAME record, white-label with the vendor's branding removed, with uptime history up to five years and 10,000 email subscribers included (extras at $0.01 each)
- Every tier and add-on is public — Free $0 with 10 monitors and 3 status pages, Solo $9, Team $19, Organization $49 per month, teammates at $8 each, SMS and calls at $0.10 per alert, WhatsApp at $0.07 — with no credit card required on the free tier
- Phone-call alerts come from one consistent number that rings through Do Not Disturb
- A documented REST API with an OpenAPI spec covers monitors, heartbeats, domains, status pages, incidents, maintenance and notification channels, plus an MCP server and n8n
Held against it
- On-call scheduling, acknowledgement and escalation are documented through the SIGNL4 integration rather than in the product itself
- The controller is Designmodo Inc. of New York under New York law, personal data is stored in the United States and the European Union, and we found no public information on an EU entity or representative
- We found no public information on the vendor's own incident history, post-mortems or an SLA with credits
- The vendor states everything runs in one account with no per-client logins, and we found no public information on audit logs, SCIM provisioning or bulk import
- The captured pages give different figures for single sign-on — a feature page describes it while the plan comparison shows dashes — and we found no public information on VAT treatment
Best for
- You run an agency and want one white-label status page per client on a domain like status.clientsite.com, managed from a single account
- You need an outage to wake a sleeping engineer — phone-call alerts come from one consistent number that rings through Do Not Disturb
- You must present uptime over custom date ranges that match contract or billing periods, with retention up to five years and PDF or image export
- You want to compute the bill before signing up, with every tier and per-unit add-on published and a free tier requiring no credit card
Avoid if
- You require a European contracting entity or EU-only data residency — the controller is Designmodo Inc. of New York and storage includes the United States
- Your team needs built-in on-call rotations and escalation with timeouts — the documented route runs through the SIGNL4 integration
- You must give each client a separate login — the vendor states everything runs in one account with no per-client logins to manage
- You depend on keyword checks against JavaScript-rendered pages working without extra configuration — the default reads the static HTML the server sends
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 3.5 of 5 |
| API, monitoring as code & team administration | 3 of 5 |
| Uptime reports, data & the vendor's own reliability | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3.5 of 5 |
Checks, locations & failure confirmation
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
Every check type my sixty client sites need is documented: HTTP and HTTPS with keyword confirmation and a response-time requirement, TCP, port and ping, SSL expiry with reminders at 14, 7 and 1 days, domain expiry, DNS, cron heartbeats and API checks, as often as every 30 seconds from up to 15 locations, with a second location confirming a failure before an alert fires and maintenance windows to pause checks. The keyword page is honest that the default reads static HTML, so JavaScript-rendered pages need extra configuration. I found no public information on browser or transaction checks of a login or checkout, multi-step API checks with assertions, private locations, or the probe cities named. 16 2 19 18 12
The SaaS Platform Engineer
The captured pages show HTTP and HTTPS, keyword, TCP and port, ping, SSL, cron heartbeat, domain and DNS checks, as often as every 30 seconds from up to 15 worldwide regions, with an outage only declared once a second location confirms — the false-alarm discipline I want before anyone is woken. Response times are tracked by region, TCP latency per check, and maintenance windows can pause monitors. I found no public information on multi-step API checks with header and body assertions, browser or transaction checks of a login flow, private probes inside our own network, or probe locations named by city. 1 7 11 16 18 19
The Customer Support Lead
The catalogue covers what my team would watch: uptime, keyword checks that demand certain text inside a time limit, SSL expiry with reminders, ping, port and TCP with latency per check, cron heartbeats, domain and DNS, at intervals down to 30 seconds from up to 15 regions, with a second location confirming a failure before an alert fires, plus maintenance windows. The pages describe keyword checks reading static HTML, with JavaScript-rendered pages needing extra configuration. We found no public information on browser-flow or multi-step checks with assertions, on probe cities being named, or on private probes inside our own network. 1 2 7 11 16 18 19
The E-Commerce Operations Manager
This can watch the pages that actually earn money: keyword and response-time checks can demand the payment confirmation text within a set timeframe before calling a site up, alongside ping, TCP and port checks with latency per check, SSL with 14/7/1-day expiry reminders, DNS, domain expiry and cron heartbeats, at intervals down to 30 seconds from up to 15 regions, with a second region confirming the failure before an alert fires and a screenshot captured at that moment. We found no public information on browser or transaction checks walking a checkout, multi-step API checks with assertions on headers and body, private probes inside our own network, or probe locations named by city, and the keyword monitor reads the static HTML the server sends unless extra configuration is added for JavaScript-rendered pages. 16 19 12 2 11 1
The Information Security Officer
The check surface is broad and the failure logic is documented: HTTP(S), keyword checks that can also demand a response within a set time, ping, port, TCP, SSL expiry with 14-, 7- and 1-day reminders, DNS, domain expiry, cron heartbeats and API monitoring, at intervals down to 30 seconds from up to 15 locations, with a second location required to confirm a failure before an incident is called and a screenshot captured of the failed page. Maintenance windows are described, but the locations are counted rather than named by city, and we found no public information on multi-step checks with assertions, browser or transaction checks, or private locations inside our own network. 2 3 7 11 16 18 19
The Skeptic
The check catalogue is broad and documented — HTTP(S), keyword, ping, port, TCP, SSL with chain and renewal checks, domain expiry, DNS, cron heartbeats and API checks — at intervals down to 30 seconds from up to 15 regions, and the question I ask first is answered: a failure is re-checked and confirmed by a second location before an alert fires, with a screenshot of the page at the moment it failed. It stops short of the top level because the captured pages give a count of regions rather than a list of cities, JavaScript-rendered pages need extra configuration before keyword checks can see them, and we found no public information on private check locations inside a customer's own network. 1 2 3 11 12 16 18
Alerting, escalation & on-call
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
Email, SMS, WhatsApp, phone call, Telegram, Slack, Discord, Microsoft Teams and webhooks are all named, with recovery alerts, per-monitor channel routing and maintenance windows, and calls come from one consistent number that rings through Do Not Disturb — the exact thing I wanted after a client's angry call about an expired certificate. SMS and call alerts are priced at $0.10 per alert with included quotas per plan, and WhatsApp at $0.07. On-call scheduling, acknowledgement and escalation are covered by an integration with SIGNL4 rather than described natively, and I found no public information on alert grouping or incident timelines with who did what. 18 1 7 5 14
The SaaS Platform Engineer
Alerts reach people by email, SMS, WhatsApp, Telegram, Slack, Discord, Microsoft Teams and webhooks, phone calls come from one saved number that rings straight through Do Not Disturb, SMS and call alerts are priced at $0.10 per alert with credits per plan, and different monitors can be routed to different channels. On-call itself is delegated rather than built in: the documented route to scheduling, acknowledgement and automatic escalation is the SIGNL4 integration, not the product. I found no public information on native escalation policies with timeouts, on-call rotations, acknowledge-and-resolve from the app, or alert grouping. 1 5 6 7 13 14 18
The Customer Support Lead
When a site breaks my people can hear about it by email, SMS, WhatsApp, phone call from one saved number that beats Do Not Disturb, Telegram, Slack, Discord, Microsoft Teams or webhook, with recovery notices, per-monitor routing to different Teams channels, and maintenance windows to mute planned work. SMS and call alerts are included in plan quantities and cost $0.10 per alert beyond them. On-call scheduling, acknowledgement and escalation arrive only through the SIGNL4 integration, and we found no public information on built-in escalation policies, rotations, alert grouping or incident timelines. 1 5 7 13 14 18 19
The E-Commerce Operations Manager
Email, SMS, phone call, WhatsApp, Telegram, Slack, Discord, Microsoft Teams and webhooks are documented, the calls come from one consistent number that rings through Do Not Disturb, and recovery alerts, per-monitor routing to different channels and maintenance windows are all there — that phone call alone would have saved us a six-hour checkout outage. On-call scheduling, acknowledgement and automatic escalation are documented through a SIGNL4 integration rather than in the product itself, and SMS and call alerts are priced at $0.10 per alert on top of included credits per plan. We found no public information on native escalation policies with timeouts, rotation overrides, alert grouping or incident timelines. 1 5 7 13 14 18
The Information Security Officer
Channel coverage is strong and priced openly: email, SMS, WhatsApp, phone calls from a consistent number that rings through Do Not Disturb, Telegram, Slack, Discord, Microsoft Teams and webhooks, with recovery notices, per-monitor channels, maintenance windows, and SMS and calls both included per plan and priced at $0.10 per alert as an add-on. Native on-call stops there — escalation, rotations, acknowledgement and mobile push are documented through the SIGNL4 integration rather than in the product, and we found no public information on built-in escalation with timeouts, alert grouping or incident timelines showing who did what. 1 5 7 13 14 18
The Skeptic
Email, SMS, WhatsApp, phone calls from one consistent number that rings through Do Not Disturb, Telegram, Slack, Discord, Teams and webhooks are all documented, with recovery alerts, per-monitor routing to different channels and maintenance windows — and SMS and calls are both included in stated quantities per plan and priced at $0.10 per alert beyond them, so no fair-use surprise on page nine. On-call is outsourced: scheduling, acknowledgement and escalation come through the SIGNL4 integration rather than the product itself, and we found no public information on native escalation policies, alert grouping or incident timelines with who did what. 1 5 7 13 14 18
Status pages & incident communication
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
This is the core of the pitch for an agency: one status page per client on a domain like status.clientsite.com with a single CNAME record, my logo, colours and own CSS, white label with the Pulsetic branding coming off entirely, password protection or single sign-on to gate a page for one client, and 50 languages with one language per page. Monitors feed the page, uptime history sits behind it for up to five years, visitors subscribe to incident updates by email (up to 10,000 subscribers included, additional subscribers at $0.01 each), and embeddable badges carry a live uptime number. I found no public information on component groups, per-component subscriptions, subscriber channels beyond email, or how the page stays online if the main service is down. 17 4 15
The SaaS Platform Engineer
Pages publish on a custom domain via one CNAME record, carry our logo, colours and custom CSS with white label taking the Pulsetic branding off, are fed live status by the monitors we choose with per-element ordering, and show uptime history up to five years. Subscribers are emailed as an incident opens, updates and resolves (10,000 included, $0.01 each beyond), pages can be password-protected or SSO-gated for a single client, translation covers 50 languages, there are ready-made message templates with an AI assistant to polish updates, and status badges embed anywhere. I found no public information on subscriber channels beyond email (SMS, RSS or webhook subscribers), component groups, or how the page itself stays online if the main service is down. 1 4 7 15 17 18
The Customer Support Lead
After our last outage produced three hundred identical tickets, this is close to the page I wanted: on our own domain via one CNAME, with components we pick and order ourselves, eight ready-made incident templates plus an AI assistant to fix tone, email subscribers — 10,000 included, $0.01 each beyond that — up to five years of uptime history, and a private page for the largest accounts behind a password or single sign-on. Fifty languages with per-field wording, embeddable badges and fully removable branding round it out. We found no public information on component groups, per-component subscriptions, or subscriber channels other than email. 1 4 7 15 16 17 18
The E-Commerce Operations Manager
Custom-domain pages set up with one CNAME record, components I choose and order myself, incident updates, scheduled maintenance, password- or single-sign-on-protected private pages for a single client, white-label branding removal, embeddable badges and 50 languages (one language per page) are documented, with email subscribers up to 10,000 included and $0.01 for each additional one. We found no public information on SMS or RSS subscriber notifications, component groups, or how the status page itself stays online if the monitoring service goes down. 4 15 17 7 1
The Information Security Officer
The pages meet most of what an auditor-facing status process needs: custom domain via one CNAME record, components we choose and order fed by the monitors, incident updates and scheduled maintenance, email subscribers with 10,000 included and extras at $0.01 each, uptime history per page, password protection and single sign-on gating for a single customer, white-label branding with our own CSS, embeddable status badges and 50 languages. The captured pages give different figures on SSO-protected pages — the feature pages describe the option while the plan comparison shows dashes on every listed plan — and we found no public information on component groups, SMS or webhook subscribers, or how the page hosting is isolated from the main service. 1 4 6 15 16 17
The Skeptic
Custom-domain pages set up with one CNAME record, selectable and orderable components, incident updates, scheduled maintenance, up to 10,000 email subscribers at $0.01 each beyond that, uptime history behind the page for up to five years, password-protected or single-sign-on pages for a single client, 50 languages with eight message templates, embeddable badges and white-label with the vendor's branding removed. Subscriber notification is documented for email; we found no public information on RSS or webhook subscribers, and nothing on how the status page itself stays online when the main service is down — the question I ask every status-page vendor. 4 15 16 17 18
API, monitoring as code & team administration
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
The REST API is the strongest part for a shop like mine: monitors, heartbeats, domains, status pages, incidents, maintenance windows and notification channels are all reachable with a plain token, a full OpenAPI spec ships, and an MCP server and n8n sit on the same calls — enough to script monitors for sixty sites into existence. Teammates cost $8 each with Admin, Editor and Viewer roles, and two-factor authentication and single sign-on protect the dashboard. The vendor itself says everything runs in one account with no per-client logins to manage, and I found no public information on Terraform or a CLI, SCIM provisioning, audit logs or bulk CSV import. 6 17 1 16
The SaaS Platform Engineer
The REST API is genuinely broad — monitors, heartbeats, status pages, incidents, maintenance and notification channels, with an OpenAPI spec, token auth, a usage dashboard, plus an MCP server and n8n — so checks could be scripted even though I found no public information on a Terraform provider or monitoring-as-code CLI. Teammates join as Admin, Editor or Viewer at $8 each with role-based access, and two-factor is listed while the pricing page and feature pages give different signals on which plans include single sign-on. I found no public information on SCIM provisioning, audit logs, or per-client logins — the agency story is explicitly one shared account with no per-client logins to manage. 1 6 7 16 17
The Customer Support Lead
A token-authenticated REST API with an OpenAPI spec reaches monitors, heartbeats, status pages, incidents, maintenance and notification channels, and the MCP server and n8n let a team drive it from code or an assistant. Teammates join at $8 each as Admin, Editor or Viewer, with two-factor login and white-label presentation for client work. Everything runs in one account with no per-client logins, and we found no public information on Terraform or code-defined monitors, SCIM provisioning, audit logs or bulk import. 1 4 6 7 16 17
The E-Commerce Operations Manager
A documented REST API with an OpenAPI spec and token authentication covers monitors, heartbeats, domains, status pages, incidents, maintenance and notification channels, plus an MCP server, n8n and Zapier, and the account side has Admin, Editor and Viewer roles at $8 per teammate with two-factor authentication — enough to script our checkout monitors. The agency model is a single shared account with no per-client logins, which the vendor states itself, and we found no public information on Terraform or monitoring-as-code, SCIM provisioning, audit logs or bulk monitor import. The homepage mentions single sign-on while the pricing table shows dashes across its Single Sign-On row, so availability and price are unclear to me. 6 16 17 7 1
The Information Security Officer
The REST API is real and documented — monitors, heartbeats, status pages, incidents, maintenance and notification channels, with an OpenAPI spec, token authentication and a usage dashboard — and the team side has Admin, Editor and Viewer roles, teammates at $8 each, two-factor authentication, white-label presentation for clients and an MCP server for automation. It falls short of the administration I need before anyone gets a login: we found no public information on audit logs, SCIM provisioning, bulk import or a Terraform or CLI workflow, the vendor states everything runs in one account with no per-client logins, and the plan comparison shows dashes for single sign-on while a feature page describes it. 1 6 7 16 17
The Skeptic
A documented REST API shipping an OpenAPI spec covers monitors, heartbeats, domains, status pages, incidents, maintenance and notification channels, with an MCP server, n8n, Zapier and a per-key usage dashboard, and teammates join as Admin, Editor or Viewer at $8 each with two-factor authentication and white-label client reporting. The captured pages give different signals on single sign-on — one offers 2FA or SSO for the login while the pricing table shows dashes for it on every plan — and we found no public information on Terraform or monitoring-as-code, SCIM provisioning, audit logs or bulk import; the vendor itself states everything runs in one account with no per-client logins to manage. 1 5 6 7 16 17
Uptime reports, data & the vendor's own reliability
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
Monthly client reporting is well covered: uptime and response time over custom date ranges that can match a contract or billing period, scheduled delivery by email, a weekly report, PDF and image export, and retention stated per plan — three months on free, one year on Solo and Team, five years on Organization. Raw checks, events, downtime in seconds and stats over 1, 7, 30 or 90 days are pullable through the API, and the vendor publishes its calculation method (uptime as period minus downtime over period, month = 30.44 days, year = 365.25 days) with the caveat that an outage shorter than a monitor's check interval can go uncounted. I found no public information on response-time percentiles or breakdowns, a vendor SLA with credits, or a public incident history with post-mortems. 18 7 6 19 1
The SaaS Platform Engineer
The record side is strong: uptime and response times by region, SLA reports over custom date ranges, scheduled email and weekly reports, PDF and image export, raw check results and downtime totals in seconds through the API, retention stated per plan up to five years, and the uptime and downtime formulas published with their day-length averages. Client-ready branded reports fit the white-label case. What holds it back is the vendor's own side: beyond a status display reading 100% on captured pages, I found no public information on a public incident history, post-mortems, an SLA with credits, a published probe IP list beyond the automatic Cloudflare allowlisting, or a self-hosted edition. 1 6 7 12 18 19
The Customer Support Lead
This is the history I can hold up at a contract renewal: uptime kept up to five years with retention stated per plan, SLA reports over custom date ranges that match billing periods, scheduled and weekly email reports, raw checks and downtime counted in seconds through the API, and branded PDF or image exports for customers. The vendor's own page displays a status of 100%. We found no public information on its incident history or post-mortems, on an SLA with credits, or on a published probe IP list beyond the automatic Cloudflare allowlisting. 1 5 6 7 17 18 19
The E-Commerce Operations Manager
Uptime percentage, downtime counted in seconds with timestamps, response times by region, SLA reports over custom date ranges that can match our contract periods, scheduled and weekly email reports, retention up to five years on the top plan, white-label PDF and image export for the agency, and raw checks and events via the API are all documented, and the vendor even publishes its arithmetic (month = 30.44 days, year = 365.25 days) — enough to show the agency what a night of downtime cost. The vendor's own status page shows a current 100% figure, but we found no public information on its incident history, post-mortems, an SLA with credits, or response-time percentiles. 18 7 6 1 17 19
The Information Security Officer
The record is closer to audit-grade than most: downtime counted in seconds with timestamps, uptime and response history kept up to five years with retention stated per plan, SLA reports over custom date ranges matching contract periods with scheduled email delivery, PDF and image exports, raw checks, events and downtime totals retrievable by API, and the uptime and downtime formulas published with their day-length conventions plus the stated caveat that an outage shorter than the check interval can go uncounted. The gaps: we found no public information on response-time percentiles, a published probe IP list beyond automatic Cloudflare allow-listing, the vendor's own incident history and post-mortems, an SLA with credits, or a self-hosted edition. 1 6 7 17 18 19
The Skeptic
Retention is stated per plan — three months on free, one year on Solo and Team, five years on Organization — and the record is exportable: raw checks, events and downtime totals in seconds through the API, scheduled email and weekly reports, white-label PDF and image export, with the uptime formula and its calendar averages published alongside the honest caveat that an outage shorter than the check interval can go uncounted. The monitor's own trust record is where it thins out: we found no public information on the vendor's own incident history or post-mortems, on an SLA with credits, or on a published list of probe IP addresses — only a Cloudflare integration that keeps those IPs allowlisted. 1 6 7 18 19
European sovereignty
panel opinion
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 contracting entity is Designmodo Inc. of New York under New York law, and the privacy policy states that personal data is stored in the United States and in the European Union on hosting providers listed in the data processing agreement, with Standard Contractual Clauses (Module Two) as the transfer safeguard, a 24-hour breach notice, client audit rights, and 14 days' notice of sub-processor changes with a right to object. Twilio is named in the agreement for SMS and voice delivery. It is a US entity with US storage in the chain and no EU representative described, and I found no public information on the locations of the remaining sub-processors or on Designmodo's own certifications. 9 10 13 8
The SaaS Platform Engineer
The contracting entity is Designmodo Inc. of New York under New York law, and the privacy policy states personal data is stored in the United States and in the European Union, so the chain is partly non-EU. Real safeguards exist on paper: a published data processing agreement using Standard Contractual Clauses Module Two for transfers out of the EU, EEA, Switzerland and the UK, sub-processors listed in that agreement with Twilio named for SMS and voice, 24-hour breach notification, client audit rights and a DPO contact on request. I found no public information on an EU entity or EU representative or named EU hosting infrastructure, and the ISO 27001 and SOC 2 statements attach to the hosting providers rather than to Designmodo itself — for the names and phone numbers of a Berlin on-call rotation, that is not the chain I would pick. 8 9 10 13
The Customer Support Lead
The contracting entity and data controller is Designmodo Inc. of New York, and the captured pages state that personal data is stored in the United States and the European Union on hosting providers certified to ISO 27001 and SOC 2, without naming them. A published data processing agreement carries the EU Standard Contractual Clauses for transfers from Europe, names Twilio for SMS and voice delivery, grants audit rights and promises 14 days' notice of subprocessor changes. That is a documented chain, but an American one — we found no public information on a European entity, a self-hosted edition or named hosting infrastructure. 8 9 10
The E-Commerce Operations Manager
The contracting entity, data controller and governing law are Designmodo Inc. of New York, personal data including on-call names and phone numbers is stored in the United States and the European Union on providers named in the data processing agreement, Twilio carries the SMS and voice alerts, and the agreement publishes Standard Contractual Clauses, 24-hour breach notice, sub-processor change notice with an objection right and client audit rights. We found no public information on an EU contracting entity or EU representative, the hosting certifications are stated only as "such as ISO/IEC 27001 and/or SOC 2", and United States storage is part of the documented chain — a real agreement, but not a European one. 9 10 8
The Information Security Officer
The chain is American with contractual safeguards: Designmodo Inc. of New York is the controller and contracting entity under New York law, personal data — including the on-call phone numbers and status page subscriber emails the agreement enumerates — is stored in the United States and the European Union, transfers rely on the Commission's Standard Contractual Clauses (Module Two), and the published DPA names Twilio for SMS and voice with a 24-hour breach report, client audit rights and 14 days' notice of subprocessor changes. We found no public information on a European entity or representative or on a self-hosted edition that would keep every record on our own servers; hosting providers are described by their ISO 27001 and SOC 2 certifications rather than by name and location. 8 9 10
The Skeptic
The contracting entity, the data controller and the governing law all sit with Designmodo Inc. of New York, with disputes going to New York courts; personal data is stored in the United States and the European Union, a DPA with Standard Contractual Clauses Module Two is published, Twilio is named for SMS and voice delivery, and audit rights, a 24-hour breach notice and return-or-erase terms are in the agreement. That is a real paper trail rather than a bare privacy policy, but no EU entity or EU representative appears on the captured pages, the hosting providers are unnamed beyond ISO 27001 and SOC 2 certification claims, and we found no public information on where each named subprocessor sits. 8 9 10 13
Pricing transparency
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
I can price my whole stack from public pages: Solo $9, Team $19 and Organization $49 per month, additional monitors at $0.20 each, teammates at $8 each, SMS and call alerts at $0.10 per alert and WhatsApp at $0.07, additional subscribers at $0.01, yearly billing advertised as "Save 2 months", and a free tier of 10 monitors and 3 status pages without a credit card. Cancellation at the end of the billing period, a refund only on the original order within 20 days, 30 days' price-change notice and automatic renewal are all in the terms. The pages I read state no VAT treatment and no minimum term, and the per-plan check interval is not laid out on the pricing page, so the annual cost is not fully computable to the last euro. 7 8 17
The SaaS Platform Engineer
Pricing is unusually computable: Free $0, Solo $9, Team $19 and Organization $49 per month, with monitor counts (10, 10+, 50+, 300+), region checks (3, 5, 15, 15), teammates at $8 each, notify-only seats, subscriber allowances, and per-alert prices for SMS and calls ($0.10) and WhatsApp ($0.07), plus unit-priced add-ons — $0.20 per monitor, $5 per 100,000 RUM page views, $15 per 100 AI runs — adjustable anytime with usage-based charges added automatically to the billing cycle. Billing is monthly or yearly in advance ("Save 2 months" on yearly), with a 20-day refund on the original order only and cancellation at the end of the period. I found no public information on VAT treatment or status page counts per paid plan — a customer quote mentions unlimited status pages while the free plan lists three. 4 7 8 16
The Customer Support Lead
I can nearly compute our annual bill from the public pages: a free tier with 10 monitors and 3 status pages, Solo $9, Team $19 and Organization $49 per month, each tier's monitor count, region checks and included SMS, WhatsApp and subscriber allowances, teammates at $8 each, and add-ons priced to the cent — $0.20 per monitor, $0.10 per SMS or call alert, $0.07 per WhatsApp alert, $0.01 per extra subscriber — with usage-based add-ons charged automatically. Cancellation and refund terms are published. We found no public information on VAT treatment or a minimum term, and while one page presents single sign-on for the login, the plan table marks it with dashes rather than a price. 4 7 8 16 17
The E-Commerce Operations Manager
All four plans are public ($0 free, $9, $19 and $49 per month, "Save 2 months" on yearly billing) together with the scaling rules I need: monitors per plan plus $0.20 per extra monitor, teammates at $8 each, SMS and calls at $0.10 per alert, WhatsApp at $0.07, extra subscribers at $0.01 each, and priced add-ons for AI monitor runs and page views, with usage-based charges added automatically, cancellation at the end of the billing period and a 20-day refund window on the original order. We found no public information on VAT treatment, the Single Sign-On row shows dashes across the listed plans, and the captured pages leave the base check interval per plan unclear, so an exact annual total still has holes. 7 8 16
The Information Security Officer
Most of the bill is computable from public pages: Free $0, SOLO $9, TEAM $19 and ORGANIZATION $49 per month with per-plan monitor, teammate, subscriber, region-check and webhook counts, teammates at $8 each, and add-ons at $0.20 per monitor, $0.10 per SMS or call alert, $0.07 per WhatsApp alert, $5 per 100,000 RUM page views, $15 per 100 AI monitor runs and $0.01 per additional subscriber, with the terms covering monthly or yearly billing in advance, a 20-day refund on the original order only, cancellation at the end of the billing period and automatic charges for usage add-ons. VAT treatment is not stated on the captured pages, several inclusions appear as floors such as '10+' rather than exact counts, and which plans include the 30-second interval is not shown in the captured figures. 4 7 8 16
The Skeptic
Every tier is public — free at $0 with 10 monitors and 3 status pages, Solo $9, Team $19, Organization $49 per month, yearly billing shown as save 2 months — with scaling rules for monitors, region checks, webhooks per monitor, teammates at $8 each, notify-only seats and subscribers, and add-ons priced per unit: SMS and calls $0.10 per alert, WhatsApp $0.07, extra monitors $0.20, page views $5 per 100,000, AI runs $15 per 100, additional subscribers $0.01 each. Terms state monthly or yearly billing in advance, auto-renewal with 30 days notice of price changes, cancellation effective at the end of the billing period, and a refund only on the original order within 20 days. What keeps a buyer from computing the full annual cost: we found no public information on VAT treatment, the pricing table shows dashes for single sign-on, and status-page counts beyond the free plan's three rest on a customer testimonial describing unlimited status pages. 4 7 8 16 17
European sovereignty — proven facts
1 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 US ⚠ unverified | 0/2 pts | 9 Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Pulsetic
Is Pulsetic European?
No. whats-best.ai classifies Pulsetic as Rest of world. Its vendor, Designmodo Inc., is incorporated in United States, per the vendor’s page captured 1 Nov 2026.
Where does Pulsetic store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Pulsetic have a free plan?
Yes. Pulsetic has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Pulsetic?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) highest among the other 14 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Pulsetic alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 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 page gives a US registered office but names no state of incorporation or company register; "Designmodo Inc." plus the address are the only basis.
- Weak sourcing — Hosting location, Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- 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.
- 12 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 10 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (19)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage pulsetic.com Checked 1 Nov 2026 Details →
- 2 Features page (SSL monitoring) pulsetic.com Checked 1 Nov 2026 Details →
- 3 Features page (cron job monitoring) pulsetic.com Checked 1 Nov 2026 Details →
- 4 Features page (status pages) pulsetic.com Checked 1 Nov 2026 Details →
- 5 Integrations page pulsetic.com Checked 1 Nov 2026 Details →
- 6 API documentation pulsetic.com Checked 1 Nov 2026 Details →
- 7 Pricing page pulsetic.com Checked 1 Nov 2026 Details →
- 8 Terms of service pulsetic.com Checked 1 Nov 2026 Details →
- 9 Privacy policy pulsetic.com Checked 1 Nov 2026 Details →
- 10 Data processing agreement (dpa) pulsetic.com Checked 1 Nov 2026 Details →
- 11 Checks, locations & failure confirmation — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 12 Checks, locations & failure confirmation — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 13 Alerting, escalation & on-call — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 14 Alerting, escalation & on-call — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 15 Status pages & incident communication — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 16 API, monitoring as code & team administration — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 17 API, monitoring as code & team administration — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 18 Uptime reports, data & the vendor's own reliability — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →
- 19 Uptime reports, data & the vendor's own reliability — found from sitemap pulsetic.com Checked 1 Nov 2026 Details →