SIGNL4
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Derdack GmbH · www.signl4.com
Compare with OnPage → 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.
SIGNL4 at a glance
- Vendor
- Derdack GmbH
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates SIGNL4 2.5/5, the mean of 6 judges. SIGNL4 is an on-call alerting and incident management platform from Derdack GmbH of Potsdam, Germany. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
SIGNL4 is an on-call alerting and incident management platform from Derdack GmbH of Potsdam, Germany. On-call scheduling is strongest, scoring 7: minute-precision rotations with overlapping slots and time zones, flagged coverage gaps, stand-ins from the mobile app, escalation chains with timeouts, and monthly duty records as CSV. Integration and admin holds at 6: 200+ verified integrations documented on GitHub, a REST API, two-way sync into service-desk tools. Alerting and routing spreads 6 to 7 on persistent multi-channel delivery with acknowledgement tracking, though heartbeat monitoring and SMS/voice delivery countries are not documented. Incident response scores 4 to 5 on a documented lifecycle with incident chat, postmortems and MTTR analytics, but no public information on status pages with subscribers, commander roles or timelines. Reliability and compliance scores 4 to 5 on a stated 99.95%+ availability and TISAX label, with no public information on SLA credits or ISO 27001/SOC 2. Sovereignty scores spread 2 to 3: the German entity and GDPR/EU-compliance claims earn credit, while hosting location, subprocessors and a data processing agreement remain undocumented. Pricing: only a free 30-day trial.
Speaks for it
- Minute-precision rotations with overlapping slots, time-zone support, automatically flagged coverage gaps and CSV exports of monthly duty records.
- Persistent multi-channel alerting via push, SMS, voice and email with delivery and acknowledgement tracking and do-not-disturb and silent-mode overrides on Android and iOS.
- 200+ verified integrations documented on GitHub, including Checkmk, PRTG, ServiceNow, Kaseya and Halo ITSM.
- Two-way sync of incident ownership and annotations back into monitoring and service-desk tools.
- AI alert summaries stated not to use customer data for model training.
Held against it
- We found no public information on hosting location, subprocessors or a published data processing agreement.
- The 99.95%+ availability figure stands with no public information on SLA credits or ISO 27001/SOC 2 certification.
- We found no public information on single sign-on, SCIM provisioning, two-factor authentication or exportable admin audit logs.
- We found no public information on public status pages with subscribers, incident commander roles or an incident timeline.
- Beyond the free 30-day trial we found no published per-user prices, plan tiers or notification volumes.
Best for
- You run distributed on-call rotations across time zones and need auditable, CSV-exportable duty records for payroll.
- Your monitoring and ITSM stack matches the named connectors and you want incident ownership synced back into it.
- You operate after-hours hotlines and need paging that persists and escalates until someone acknowledges.
Avoid if
- You must document hosting regions, subprocessors and a data processing agreement in a third-party risk register before signing.
- Your procurement requires an SLA with credits or ISO 27001/SOC 2 certification.
- Your major-incident process depends on public status pages with subscribers, a commander role and an incident timeline.
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3.5 of 5 |
| Alert delivery, routing & noise reduction | 3.5 of 5 |
| Incident response, status pages & post-incident review | 2.5 of 5 |
| Integrations, API & administration | 3 of 5 |
| Platform reliability, security & compliance | 2 of 5 |
| European sovereignty | 1.5 of 5 |
On-call schedules, rotations & escalation
Show reasoningHide reasoning
How this is scored
Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
0 — No schedules or escalation of any kind; alerts go to a fixed list of people.
3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.
5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.
8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.
10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.
The SRE Lead
Drag-and-drop rotations with minute precision, overlapping schedules, multiple people per shift, time-zone support, stand-ins arranged from the mobile app, coverage gaps flagged before they happen, minimum staffing, and monthly duty records exported as CSV with past shifts locked for audit integrity. The REST API is documented for updating schedules and duties, which is the configuration-automation hook I want; fairness and rest-period reporting are not described. 2 3 6 7
The IT Operations Manager
The pages show minute-precision rotations with overlapping shifts, several people on one shift, time-zone support, coverage gaps flagged automatically before they bite, stand-ins arranged straight from the mobile app, and escalation chains that move to the next person when the first responder does not reply within a set period — exactly my deputy-after-ten-minutes case. Monthly duty records export as CSV files for pay and working-time purposes, and the REST API updates schedules and duties. Follow-the-sun hand-offs, round-robin distribution and fairness reports were not described. 2 5 6 7
The MSP NOC Lead
This is close to what my night-shift and per-account rotas need: drag-and-drop rotations with overlapping time slots to the minute, several people per shift, stand-ins from the mobile app, minimum staffing enforced, and coverage gaps flagged before they become issues, plus monthly duty records as CSV files I can hand to payroll. Escalation chains that keep firing until someone responds are documented, and schedules and duties can be updated through the REST API. I found no public information on follow-the-sun hand-offs or round-robin escalation. 2 3 5 7
The ICT Risk Officer
The drag-and-drop rotation builder with templates, minute-level precision, overlapping schedules, multiple people per shift and built-in time-zone support covers our rosters, coverage gaps are flagged automatically before they bite, and minimum staffing is enforced. Stand-ins can be arranged from the mobile app, past shifts are locked to preserve audit integrity, monthly duty records export as CSV, and schedules and duties are manageable through the REST API. We found no public description of follow-the-sun hand-offs or round-robin and conditional escalation, which keeps it below top marks. 2 3 5 7
The Engineering Manager
This is the strongest area for our works-council setting: minute-precision rotations with overlapping time slots and built-in time-zone support, coverage gaps flagged before they become issues, stand-ins arranged from the phone, push reminders before shifts, calendar sync, and downloadable CSVs of all monthly duty records — exactly the export our monthly on-call payroll needs. Escalation chains with timeouts that keep going until someone responds are documented, and the REST API covers updating schedules and duties. We found no public information on a fatigue warning when the same person is paged several nights running, on fairness reports, or on round-robin hand-offs described as such, which keeps it just short of the top level. 2 3 4 5 6 7
The Skeptic
This is a real scheduling product: drag-and-drop rotations down to the minute with time zones, overlapping schedules, stand-ins arranged from the phone, escalation chains with timeouts, monthly duty records downloadable as CSV, and shifts locked for audit integrity. Coverage gaps are flagged before they become issues and schedules can be driven through the REST API, which lifts it above the middle; what I found no public information on is follow-the-sun hand-offs described as such, or the duty-hour export tied to pay and working-time rules. 2 3 5 7
Alert delivery, routing & noise reduction
Show reasoningHide reasoning
How this is scored
Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.
0 — Sends no alerts to people; a dashboard or log viewer only.
3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.
5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.
8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.
10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.
The SRE Lead
Push, SMS, voice and email with do-not-disturb override on both iOS and Android, persistent delivery until acknowledgement, delivery and acknowledgement tracking per alert, after-hours voice call routing with real-time forwarding or voicemail, and an event engine that filters, suppresses and de-duplicates. Grouping or correlation logic, heartbeats, and the countries where SMS and voice are delivered are not described. 3 4 5 6 7
The IT Operations Manager
Push, SMS, voice and email with persistent notification until someone acknowledges, do-not-disturb and silent-mode override on both Android and iOS, delivery and acknowledgement tracking, noise filtering with de-duplication, and real-time after-hours call routing are all described. For my Checkmk pages I still found no public information on acknowledging a voice call by keypad, planned maintenance windows, or the countries where SMS and voice are delivered. 2 3 4 5 6
The MSP NOC Lead
Push, SMS, voice and email with do-not-disturb override on both Android and iOS, delivery and acknowledgement tracking, persistent alerting until someone responds, and an event engine whose noise filtering, de-duplication and suppression logic is described. After-hours voice call routing to the on-call team covers my hotline case, and the inbound webhook with JSON payloads plus per-team email addresses with routing rules give me the hooks for routing by customer. I found no public information on heartbeats for silent failures or on which countries SMS and voice delivery covers. 1 3 4 5 6 7
The ICT Risk Officer
Push, SMS, voice, email and chat delivery with do-not-disturb and silent-mode overrides on both platforms, plus persistent alerting until someone responds, is what a pager must do, and delivery and acknowledgement are tracked throughout. The event processing engine filters noise, de-duplicates and suppresses, routing follows schedule, expertise, location or availability, and after-hours calls are forwarded in real time or taken as voicemail. We found no public information on maintenance windows, heartbeat monitoring, documented grouping logic, or the countries where SMS and voice are delivered. 1 4 5 6
The Engineering Manager
Push, SMS, voice, email and chat with do-not-disturb override on both Android and iOS, persistent alerting until acknowledgement, delivery and acknowledgement tracking, and a documented event engine that filters noise, de-duplicates and delays non-critical alerts for auto-recovery — the reliability our developers need at three in the morning. Live after-hours voice call routing and dedicated team email addresses with routing rules are documented. We found no public information on heartbeat monitoring for silent failures or on the countries and channels where SMS and voice are delivered. 1 3 4 5 6 7
The Skeptic
Push, SMS, voice and email with silent mode overridden on iOS and volume and do-not-disturb overridden on Android, delivery and acknowledgement tracked, notification repeated until someone responds, and after-hours calls forwarded live or taken as voicemail — the channels and the receipts are documented, which is what I probe first. Deduplication, noise filtering and suppression are claimed; I found no public information on heartbeat monitoring for silent failures, maintenance windows, or the countries where SMS and voice are actually delivered. 1 2 4 5 6
Incident response, status pages & post-incident review
Show reasoningHide reasoning
How this is scored
What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.
0 — No incident record of any kind beyond the alert itself.
3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.
5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.
8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.
10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.
The SRE Lead
Manual alarm triggering from the app, real-time incident chat with comments directly on alerts, active stakeholder communication, automated post-duty and postmortem reports, and MTTR plus response-time analytics across the full lifecycle. We found no public information on Slack or Teams incident channels, incident roles, a public status page with subscribers, or an incident timeline, which is what I need to run a major incident. 1 4 5 6
The IT Operations Manager
The pages describe a detection-to-resolution lifecycle with real-time incident chat, comments on alerts, manual alarm triggering from the app, active stakeholder communication, automated post-duty reports naming each incident and its owner, postmortem reports, and response-time and resolution-time analytics. I found no public information on public status pages with subscribers, incident commander roles, or a dedicated incident timeline. 1 4 5 6
The MSP NOC Lead
There is a documented detection-to-resolution lifecycle with priorities as severities, real-time incident chat, postmortem and post-duty reports, active stakeholder communication, and response and resolution time analytics I could put into a monthly per-customer report, with AI alert summaries stated not to use customer data for training. I found no public information on a public status page with subscribers, incident roles or a commander, or follow-up actions tracked into a ticketing tool; a conference bridge appears only as a described team need, not a documented feature. 1 4 5
The ICT Risk Officer
The full lifecycle from detection to resolution is covered with real-time incident chat, comments on alerts, postmortem reports and automated post-duty reports naming each incident's owner and handling, and response and resolution times are tracked in the analytics suite. Stakeholder communication keeps affected users updated as incidents progress, and the AI alert summaries state that customer data is not used for model training. We found no public information on status pages with subscribers, incident roles such as a commander, or regulatory reporting templates, which is what I would need for DORA classification evidence. 1 4 5
The Engineering Manager
The full lifecycle from detection to resolution is covered with real-time incident chat, automated post-duty reports naming the owner and how it was handled, postmortem reports, MTTA and MTTR analytics, stakeholder updates, and AI alert summaries with a statement that customer data is not used for model training. Automated response workflows via ITSM platforms and two-way sync of ownership and annotations back into the service desk are documented. We found no public information on incident roles such as a commander, a timeline view, or public status pages with subscribers, so it is a solid response toolset rather than the full package. 1 4 5 6
The Skeptic
There is a genuine incident layer: real-time incident chat, active stakeholder communication, postmortem and post-duty reports, response-time and MTTR analytics, and AI summaries with the one data-handling sentence I insist on — customer data is not used for model training. But I found no public information on a public status page with subscribers, incident roles or a commander, an incident timeline, or follow-up actions tracked into Jira or Linear, which caps this at the lower middle of the scale. 1 2 4 5
Integrations, API & administration
Show reasoningHide reasoning
How this is scored
How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.
0 — No integrations and no administration beyond a single shared account.
3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.
5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.
8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.
10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.
The SRE Lead
Two hundred verified integrations documented on GitHub, named monitoring (Checkmk, PRTG) and ITSM (ServiceNow, Kaseya, Halo ITSM) links with two-way sync back into the service desk, dedicated team email addresses and an inbound webhook taking JSON payloads, and a REST API covering schedules and duties. Single sign-on, SCIM, a Terraform provider and exportable audit logs are not described. 3 4 5 7
The IT Operations Manager
Checkmk, PRTG and ConnectWise are named, over 200 tested integrations are claimed with documentation hosted publicly, an inbound webhook takes JSON payloads, and incident ownership, annotations and actions sync back into monitoring and service-desk tools for a full audit trail. Single sign-on, two-factor authentication, SCIM provisioning and administrative audit logs were not described on the captured pages, which matters for my five-admin setup. 3 4 5 7
The MSP NOC Lead
Two hundred tested integrations with named Checkmk, PRTG, ConnectWise, ServiceNow, Kaseya and Halo ITSM, an inbound JSON webhook, per-team email addresses with routing rules, and two-way sync of ownership and annotations back into service desk tools would let tickets close themselves without anyone copying text, and the REST API covers schedule provisioning. For a service provider the gaps matter: I found no public information on single sign-on, SCIM provisioning, audit logs beyond locked past shifts, or multi-tenant customer separation, and neither Autotask nor Zabbix is among the named integrations. An Opsgenie migration path is pitched. 1 3 4 5 7
The ICT Risk Officer
More than 200 tested integrations are documented on GitHub, with monitoring tools such as Checkmk and PRTG and ITSM systems such as ServiceNow, Kaseya and Halo ITSM named, alongside a documented REST API, inbound webhooks with JSON payloads and per-team email addresses with routing rules. Incident ownership and annotations sync back into monitoring and service desk tools creating a complete audit trail, and the API covers schedules and duties for configuration automation, with user and team management by role, skill and location. We found no public information on single sign-on, SCIM provisioning, Terraform or configuration as code, exportable audit logs, or multi-tenant set-ups. 4 5 7
The Engineering Manager
Over 200 verified integrations with how-to documentation on GitHub, named connectors for Checkmk, PRTG, ConnectWise, ServiceNow, Kaseya and Halo ITSM, plus inbound and outbound webhooks and a REST API described for provisioning and configuration automation such as updating schedules — good fit for a team spread over three countries. Two-way connectors sync incident ownership and annotations back into monitoring and service desk tools. We found no public information on single sign-on, SCIM provisioning, a Terraform provider or exportable audit logs, so the administration side is thinner than the integration side. 1 3 4 5 7
The Skeptic
Two hundred verified integrations with how-to documentation on GitHub, a REST API whose stated purpose includes updating schedules and duties, two-way sync of ownership and annotations back into ServiceNow-class tools, outbound webhooks registrable via the API, and user management by role, skill and location — a strong mid-weight story. I found no public information on single sign-on, SCIM provisioning, a Terraform provider or exportable admin audit logs; the Opsgenie-retirement positioning points migrating buyers at it, but I saw no documented import path. 1 4 5 7
Platform reliability, security & compliance
Show reasoningHide reasoning
How this is scored
Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.
0 — Nothing on availability, security or how the service is operated.
3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.
5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.
8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.
10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.
The SRE Lead
A stated availability of 99.95%+, a public system status page and trust centre, encrypted communications, and a TISAX label for automotive-grade security assurance. Hosting regions, an SLA with credits, encryption at rest, ISO 27001 or SOC 2, and data retention are not described on the captured pages. 1 4
The IT Operations Manager
The pages state a 99.95%+ availability figure, point to a trust centre and a system status page, and claim industry-standard encryption of communications, GDPR compliance and a TISAX label. Hosting regions, an SLA with credits, ISO 27001 or SOC 2 certification, and data retention were not described, so I cannot judge what happens when the plant's own network is the thing that is down. 1 4
The MSP NOC Lead
A public system status page, a trust centre, a stated 99.95%+ availability, encrypted communications, GDPR compliance and a TISAX label are more than a bare enterprise-security claim. I found no public information on hosting regions, ISO 27001 or SOC 2 certifications, SLA credits, data retention, or DORA and NIS2 support, which is thin for the audits my sixty customers put us through. 1 4
The ICT Risk Officer
An availability figure of 99.95 percent or better is stated, a system status page and a trust centre are referenced, communications are protected with industry-standard encryption, and the TISAX label together with locked shift records and acknowledgement tracking gives some assurance. But no ISO 27001 or SOC 2 statement, no SLA with credits, no hosting regions, no data retention terms and nothing at all on DORA or NIS2 appear on these pages; an availability marketing figure is not an SLA I can register for a BaFin-supervised payments house. 1 2 4
The Engineering Manager
A public system status page and a trust centre for security and data privacy are listed, availability is stated as 99.95%+, communications are described as protected with industry-standard encryption protocols, and the vendor states GDPR compliance and a TISAX label. We found no public information on hosting regions, encryption at rest, ISO 27001 or SOC 2, SLA credits, data retention or multi-region failover, so I could not yet satisfy our auditors or the works council from these pages alone. 1 3 4 5
The Skeptic
A public system status page and a trust centre exist, availability is stated at "99.95%+", communications are called industry-standard encrypted, and a TISAX label is claimed — more than a bare enterprise-security line. But I found no public information on an SLA with credits, hosting regions or multi-region failover, ISO 27001 or SOC 2, penetration tests or data retention, and on these pages the availability figure stands alone with nothing behind it. 1 4 5
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country 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 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 voice, AI, 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 including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The SRE Lead
The vendor is a German company (Derdack GmbH of Potsdam) claiming full GDPR and EU compliance with a TISAX label. We found no public information on where alerts, incident records and account data are hosted, which subprocessors sit in the chain, or a published data processing agreement. 2 4
The IT Operations Manager
The copyright holder across the pages is DERDACK Group, the vendor is registered in Potsdam, Germany, and the pages claim the service is GDPR and EU-compliant. Where alerts, duty records and contact data are hosted, and which subprocessors process them, were not described on the captured pages. 3 4
The MSP NOC Lead
The vendor is Derdack GmbH of Potsdam with copyright to the DERDACK Group, and the pages claim full GDPR and EU compliance with encrypted communications and a trust centre, which points to a European chain. However, hosting location, subprocessors including the SMS and voice carriers, and a published data processing agreement are not documented in the pages I read, so I cannot verify where my customers' alert, duty and phone data actually sits. 1 2 4
The ICT Risk Officer
Derdack GmbH of Potsdam is the contracting party and the pages claim fully GDPR and EU-compliant operation with privacy built in, which is the right starting point. But hosting location, the subprocessor list including whoever processes the AI alert summaries and chat transcripts, and a published data processing agreement are all unstated on the captured pages, so I cannot yet map this service into our register of ICT third-party providers; the trust centre is referenced but its contents are not shown. 1 4
The Engineering Manager
The vendor is Derdack GmbH of Potsdam, Germany, and the captured pages claim full GDPR and EU compliance along with a trust centre for security and data privacy. We found no public information on where alerts, duty records and phone numbers are hosted, on the subprocessor chain for SMS, voice and push delivery, or on a published data processing agreement, so for our data-protection review the chain beyond the German contracting entity remains open. 1 3 4
The Skeptic
The contracting party is a German company — Derdack GmbH, registered in Potsdam — and the pages claim "Fully GDPR and EU-compliant – privacy built in" plus a TISAX label, which is a European starting point. Beyond that the chain is unproven: I found no public information on where alerts, timelines and contact data are hosted, who the subprocessors are, or a published data processing agreement, and unproven is not the same as sovereign. 2 4
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.
0 — No public prices at all; every customer is a sales call.
3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.
5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".
8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.
The SRE Lead
A free 30-day trial is the only pricing information on the captured pages. No per-user price, plan structure, notification volumes, add-on prices or VAT treatment are documented. 2 3 5 6
The IT Operations Manager
The captured pages offer only a free 30-day trial; no per-responder price, plan structure, included notification volumes, add-ons or currency were found, so I cannot begin to compute the annual cost for my five administrators from what was captured. 5 6
The MSP NOC Lead
The only pricing information in the captured pages is a free 30-day trial. We found no public information on price per user or per plan, SMS and voice volumes, add-ons, platform fees or billing terms, so I cannot begin to compute what this would cost across sixty customers. 2 5
The ICT Risk Officer
The captured pages offer a free 30-day trial and nothing else; we found no public price per user or responder, no plan structure, no notification volumes or overage costs, and no currency or VAT treatment. A buyer cannot compute an annual cost from these pages alone. 5 6
The Engineering Manager
The only pricing information on the captured pages is a free 30-day trial. We found no public information on a price per responder, on whether read-along managers are free, on SMS and voice volumes and overage costs, on plan boundaries or on VAT treatment — with managers in three countries only reading along, I cannot begin to compute our annual cost from these pages. 2 5 6
The Skeptic
The only price-adjacent fact I could find on the captured pages is a free 30-day trial; I found no public information on a price per user, plan tiers, SMS and voice volumes or per-country costs, add-ons, platform fees, minimum seats, or VAT treatment. A buyer cannot compute even a rough annual cost from what is published here, and that is exactly the transparency gap I score. 2 3 5
European sovereignty — proven facts
0 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | 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 | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about SIGNL4
Is SIGNL4 European?
Yes. whats-best.ai classifies SIGNL4 as EU-Made.
Where does SIGNL4 store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does SIGNL4 have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to SIGNL4?
As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/5) highest among the other 16 On-Call & Incident Management 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 ilert (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: SIGNL4 alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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 product 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
- We read 7 of the 21 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.signl4.com Checked 6 Nov 2026 Details →
- 2 Features page (on-call scheduling) www.signl4.com Checked 6 Nov 2026 Details →
- 3 Features page (on-call management) www.signl4.com Checked 6 Nov 2026 Details →
- 4 Features page (alert management) www.signl4.com Checked 6 Nov 2026 Details →
- 5 Features page (incident management) www.signl4.com Checked 6 Nov 2026 Details →
- 6 Features page (mobile app) www.signl4.com Checked 6 Nov 2026 Details →
- 7 Integrations page www.signl4.com Checked 6 Nov 2026 Details →