# SIGNL4 — On-Call & Incident Management

SIGNL4 by Derdack GmbH holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: EU-Made; sovereignty: not determined.

- Vendor: Derdack GmbH (https://www.signl4.com)
- Category: [On-Call & Incident Management](https://whats-best.ai/software/incident-management.md)
- Provenance (editorial classification): EU-Made
- Canonical page: https://whats-best.ai/software/incident-management/signl4
- Alternatives: https://whats-best.ai/software/incident-management/signl4/alternatives ([markdown](https://whats-best.ai/software/incident-management/signl4/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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

## 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.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SRE Lead | The IT Operations Manager | The MSP NOC Lead | The ICT Risk Officer | The Engineering Manager | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| On-call schedules, rotations & escalation | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alert delivery, routing & noise reduction | 3/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 3/5 |
| Incident response, status pages & post-incident review | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2/5 |
| Integrations, API & administration | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Platform reliability, security & compliance | 2/5 | 2/5 | 2.5/5 | 2/5 | 2/5 | 2/5 |
| European sovereignty | 1.5/5 | 1/5 | 1.5/5 | 1/5 | 1.5/5 | 1.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **3/5** | **2.5/5** | **3/5** | **2.5/5** |

### The judges

- **The SRE Lead** (v1.0): Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
- **The IT Operations Manager** (v1.0): Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
- **The MSP NOC Lead** (v1.0): Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
- **The ICT Risk Officer** (v1.0): ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
- **The Engineering Manager** (v1.0): Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
- **The Skeptic** (v1.0): Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Encryption: yes [S4]
- GDPR: yes [S4]
- Security privacy: yes [S5]
- TISAX: yes [S4]

**Data**
- CSV export: yes [S2]

**Hosting**
- Copyright entity: DERDACK Group [S7]
- Edge proxy: Edge Proxy component offered [S3]

**Integrations**
- API surface: REST API · Webhook · Email [S6]
- Count: Github · 200+ [S7]
- Count: 200 [S4]
- Github scripts: yes [S5]
- Inbound webhook: yes [S7]
- Itsm tools: ServiceNow · Kaseya · Halo ITSM [S5]
- Methods: email · webhooks · REST APIs · two-way connectors [S1]
- Methods: email · webhooks · REST APIs · 2-way connectors [S4]
- Named: Checkmk · ConnectWise · PRTG [S3]
- Nav: Overview, REST API, Webhook, Email, Checkmk, ConnectWise, PRTG [S2]
- Outbound webhook: yes · account management · REST API [S7]
- Protocols: email · webhooks · REST · 2-way connectors [S5]
- Rest API: yes [S1]
- Rest API: yes [S3]
- Rest API: yes · provisioning and configuration automation · 3rd party application integration [S7]
- Systems: integrates with monitoring, ITSM and operational systems [S2]
- Webhook: yes [S3]

**Legal**
- Copyright: 2026 · DERDACK Group [S2]
- Copyright entity: DERDACK Group [S1]
- Copyright entity: DERDACK Group [S6]
- Entity: DERDACK Group [S3]
- Owner: DERDACK Group [S4]

**Pricing**
- Free trial: 30 · yes [S1]
- Free trial: 30 [S6]
- Free trial: yes [S4]
- Free trial days: 30 [S5]

**Product**
- Access control: yes [S4]
- Acknowledge close alerts: yes [S6]
- Acknowledgment tracking: yes [S5]
- After hours call routing: yes [S3]
- AI capabilities: smart_alert_distribution · ai_alert_summaries · intelligent_scheduling · ai_insights [S1]
- AI coverage gaps: yes [S2]
- AI data training: no [S1]
- AI scheduling: yes [S2]
- AI scheduling: yes [S3]
- Aiops: yes [S6]
- Alert channels: mobile push · SMS · voice call [S2]
- Alert channels: mobile push · SMS · voice calls [S3]
- Alert chat annotations: yes [S6]
- Alert customization: yes [S4]
- Alert enrichment: yes [S4]
- Alert history: yes [S6]
- Alert tracking: yes [S3]
- Alerting channels: Alerting channels include push, text, voice, email, chat [S1]
- API interfaces: yes [S4]
- API support: yes [S4]
- Apps: Android · iOS [S3]
- Audit trail: yes [S2]
- Auto escalation: yes [S4]
- Automated escalation: yes [S3]
- Automated workflows: yes [S4]
- Automatic alert routing: yes [S3]
- Automatic punch: yes [S2]
- Availability: 99.95%+ [S4]
- Calendar sync: yes [S3]
- Central hub: Central alert management hub streamlines alerting from multiple enterprise systems [S4]
- Cloud based: cloud [S5]
- Conference bridge: conference bridge setup mentioned as team need [S5]
- Custom alert payloads: yes [S4]
- Custom channel sequences: yes [S6]
- Custom push tones: yes [S6]
- Customer count: 1000 [S4]
- Customers count: 1000 [S5]
- Dashboard on call visibility: yes [S6]
- Delivery tracking: yes [S1]
- Detailed alert view: yes [S6]
- Detection to resolution lifecycle: full incident lifecycle [S5]
- Dnd override: yes [S2]
- Duty dashboard: yes [S2]
- Duty log on off: yes [S6]
- Duty scheduling: yes [S5]
- Dynamic alert routing: yes [S4]
- Edge proxy: Edge Proxy offered [S1]
- Escalation: yes [S2]
- Escalation: yes [S4]
- Escalation chains: yes [S5]
- Escalation engine: yes [S5]
- Escalation until ack: yes [S6]
- Escalations: yes [S1]
- Event filtering: yes [S4]
- Event processing engine: noise filtering · de-duplication · delay non-critical alerts for auto-recovery [S5]
- Handover assistant: yes [S2]
- Haptic feedback: yes [S6]
- Incident chat: yes [S1]
- Integrations count: 200 [S1]
- Integrations count: 200 [S5]
- Manual alarm triggering: yes [S6]
- Minimum staffing: yes [S2]
- Minute precision: yes [S2]
- Mobile app: yes [S1]
- Mobile app: yes [S4]
- Mobile apps: Android · iOS [S2]
- Mobile remediation: yes [S5]
- Mttr tracking: yes [S4]
- Multi channel notifications: text · voice · push · email [S4]
- Multiple people per shift: yes [S2]
- Native dark mode: yes [S6]
- Notification channels: push · SMS · voice · email · persistent_alerting [S6]
- On call scheduling: yes [S1]
- On call scheduling: Create and manage on-call schedules, automatic alert routing, escalation until response [S3]
- On call scheduling: yes [S4]
- On duty management: yes [S4]
- Onboarding time: 5 [S4]
- One click contact: call · SMS · email [S6]
- Opsgenie migration: Positioned as Opsgenie migration option [S1]
- Overlapping schedules: yes [S2]
- Override dnd android: yes [S6]
- Override silent ios: yes [S6]
- Persistent alerting: yes [S5]
- Platform type: SaaS · open and flexible [S7]
- Platform type: yes [S4]
- Platforms: Android · iOS [S6]
- Post duty reports: yes [S5]
- Post shift reports: yes [S2]
- Postmortem reports: yes [S1]
- Privacy controls: yes [S2]
- Push reminders: yes [S2]
- Reporting analytics: yes [S4]
- Role management: role · skill · location [S4]
- Rotation builder: drag & drop on-call rotation building in browser [S2]
- Schedule copy: yes [S2]
- Security claim: Enterprise-grade security and privacy [S3]
- Setup time minutes: 5 [S5]
- Shareable duty board: yes [S2]
- Shift reminders: yes [S6]
- Shift templates: yes [S3]
- Smart filtering: yes [S4]
- Stakeholder communication: Active Stakeholder Communication feature [S1]
- Stand ins absence: yes [S3]
- Stand ins in app: yes [S6]
- Standin mobile: yes [S2]
- Templates: yes [S2]
- Timezone support: yes [S2]
- Trial days: 30 · yes [S2]
- Trial length: 30 · free_trial [S3]
- Two way communication: yes [S4]
- Two way sync: yes [S5]
- Use case scope: IT · cybersecurity · production · facility management · logistics [S4]
- Use cases: IT, security operations, industrial OT alerting and response [S1]
- Use cases: 10 [S6]
- User notifications: yes [S5]
- Voice call routing: yes [S1]
- Who is on call pages: yes [S3]

**Support**
- Online docs: Online Support · YouTube onboarding videos [S3]
- Resources: docs · online_support · youtube_videos · trust_center · system_status_page [S1]

## Questions

### 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)](https://whats-best.ai/software/incident-management/ilert), [All Quiet (3.5/5)](https://whats-best.ai/software/incident-management/all-quiet) and [OneUptime (3.5/5)](https://whats-best.ai/software/incident-management/oneuptime) 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](https://whats-best.ai/software/incident-management/ilert) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [SIGNL4 alternatives](https://whats-best.ai/software/incident-management/signl4/alternatives).

## Head-to-head

- [SIGNL4 vs OnPage](https://whats-best.ai/compare/onpage-vs-signl4.md)

## What this page leaves out

- 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.
- 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.

## Sources

- [S1] Vendor homepage: https://www.signl4.com/ (checked 2026-11-06)
- [S2] Features page (on-call scheduling): https://www.signl4.com/on-call-scheduling/ (checked 2026-11-06)
- [S3] Features page (on-call management): https://www.signl4.com/on-call-management/ (checked 2026-11-06)
- [S4] Features page (alert management): https://www.signl4.com/alert-management/ (checked 2026-11-06)
- [S5] Features page (incident management): https://www.signl4.com/incident-management/ (checked 2026-11-06)
- [S6] Features page (mobile app): https://www.signl4.com/mobile-alerting-app/ (checked 2026-11-06)
- [S7] Integrations page: https://www.signl4.com/integrations-api/ (checked 2026-11-06)

---

Cite as: whats-best.ai, "SIGNL4 — On-Call & Incident Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/incident-management/signl4

Corrections: https://whats-best.ai/correct/1620?target=page
