Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by All Quiet GmbH · allquiet.app

Compare with ilert → Report an error on this page Is this your product? →

Link to this page

All Quiet: AI-assisted analysis on whats-best.ai All Quiet: AI-assisted analysis on whats-best.ai (dark)

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.

All Quiet at a glance

Vendor
All Quiet GmbH
Headquarters
Incorporated in Germany source, captured 6 Nov 2026
Data hosting
In the EU by default; pages mention the US, Germany and the United States source, captured 6 Nov 2026
Free plan
Not stated on the vendor’s pages as of 6 Nov 2026
Starting price
“Pick your plan, starting from $4.99 per user / month.” (vendor’s words) source, captured 6 Nov 2026
Panel verdict
The AI panel rates All Quiet 3.5/5, the mean of 6 judges. All Quiet is an on-call and incident management platform from All Quiet GmbH of Berlin. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

All Quiet alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

All Quiet is an on-call and incident management platform from All Quiet GmbH of Berlin. Strongest are sovereignty and on-call scheduling, both flat at 8: EU-region platform data is stored in Frankfurt with backups in Germany and never moved to the US region, a data processing agreement is published with a subprocessor annex, and scheduling covers daily-to-custom rotations, self-service overrides, a fill-up safety net and on-call hour export to payroll. Alerting and routing and integration and administration hold at 7, with fifty-plus integrations and a public API. Pricing transparency shows the widest split, from 5 to 7: higher scores rested on published tiers at $4.99 and $9.99 per user / month, while the lowest weighed the 'Talk to us' Enterprise tier, an unpriced auditing add-on and unstated VAT. Reliability and compliance span 5 to 6, where we found no public information on SLA credits, multi-region failover, penetration tests or DORA and NIS2 support. Incident response spans 6 to 7, split over postmortems prepared in Notion or Confluence and no public information on commander roles or runbooks.

Report an error

Speaks for it

  • On-call scheduling scores 8 across the table, with self-service overrides from the web or mobile app, a fill-up safety net for coverage gaps and automatic on-call hour export to payroll via CSV or the public API.
  • Sovereignty scores 8, with EU-region data in Frankfurt, backups in Germany and a published data processing agreement whose annex lists subprocessors — Stripe in Dublin, Sentry in Frankfurt for EU customers, Twilio in the United States off by default for EU customers.
  • Standard at $4.99 per user / month and Pro at $9.99 per user / month are published, with unlimited SMS and phone calls on Standard and stakeholders who only follow incidents unbilled.
  • Fifty-plus integrations span CloudWatch, Datadog, Grafana, Prometheus Alertmanager and ServiceNow inbound and Slack, Teams, Jira and Linear outbound, backed by a public REST API and a native Terraform provider.
  • The vendor states it runs no LLM on incident data — you bring your own model, and agents work through scoped API keys with no per-seat AI surcharge on Pro.

Report an error

Held against it

  • The Enterprise tier is 'Talk to us', the Auditing & Logging add-on carries no published price, and status-page SMS subscribers are 'Custom'.
  • We found no public information on SLA credits, multi-region failover, penetration tests, SOC 2 or BSI C5, or DORA and NIS2 support, and the terms state the platform is not HIPAA compliant.
  • We found no public information on incident commander roles, runbooks or in-product postmortem templates, with postmortems prepared through Notion or Confluence.
  • We found no public information on delivery receipts, a per-alert notification log, or the countries SMS and voice notifications reach.
  • The captured pages give different figures for call log retention — 365 days and 2 years.

Report an error

Best for

  • You run follow-the-sun or multi-team rotations and need self-service swaps, a fill-up safety net for gaps and on-call hours exported automatically to payroll.
  • You must keep incidents, alerts, schedules and user data in the EU region — Frankfurt hosting with backups in Germany, never moved to the US region — and present a published data processing agreement internally.
  • You want AI agents working your incidents under your own model and infrastructure, with the vendor stating it runs no LLM on incident data.
  • Your team fits the published tiers at $4.99 or $9.99 per user / month with monthly billing and seat changes at any time.

Report an error

Avoid if

  • You need HIPAA-covered processing — the terms state the platform is not HIPAA compliant.
  • You must compute an enterprise cost in advance — the Enterprise tier is 'Talk to us' and the auditing add-on and SMS status-page subscribers are unpriced.
  • Your audit trail must capture reads and failed authentication attempts — the audit log covers create, update and delete attributed to the key.
  • You need incident records kept beyond six months on Standard or twelve on Pro without an Enterprise deal — longer retention is a custom Enterprise matter.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

On-call schedules, rotations & escalation

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

Report an error

The SRE Lead

Daily to custom rotations, overrides handled by the team themselves from the web or mobile app, a fill-up safety net that pulls higher-tier members into uncovered gaps, round robin per schedule, and escalation tiers with severity and time filters are all documented, with a follow-the-sun setup among six worked examples. On-call hours are logged automatically and exportable as CSV or straight into payroll via the public API, which is exactly what compensation and working-time accounting in Germany needs. We found no public information on fairness or fatigue reports or rest-period enforcement. 1 2 3 4 20 21 24

Report an error

The IT Operations Manager

Daily, weekly, biweekly, monthly and custom rotations with 24/7 or timed coverage, follow-the-sun setup examples, three kinds of self-service overrides including cover for sick colleagues from the mobile app, round-robin per schedule, a fill-up safety net for gaps, and unlimited escalation tiers with configurable cadence, stop-on-acknowledge, severity and time filters — including a documented example of escalating after ten minutes to the next tier, which is exactly my deputy rule. On-call hours are logged automatically and exported as CSV or via the public API to HR and payroll, and schedules, escalations and overrides are manageable as code through Terraform and the API. We found no public information on fairness or fatigue reporting, rest-period rules, or importing schedules from HR or workforce tools. 1 3 4 20 21

Report an error

The MSP NOC Lead

Rotations run daily to custom with overnight windows, follow-the-sun example setups and self-service swaps from the mobile app, and escalation tiers repeat with severity and time filters — exactly the per-team rotas I need for each key account and the night shift. On-call hours are logged automatically and exported as CSV or via the API to payroll. Gaps are covered by a fill-up from higher tiers rather than flagged in advance, and schedules, escalations and overrides are manageable through the public API and Terraform. 3 4 20 21 24

Report an error

The ICT Risk Officer

Daily to custom rotations with follow-the-sun setups, self-service overrides and swaps from the mobile app, round-robin per schedule, and escalation tiers with severity and time filters, repeat tiers and a fill-up safety net are all documented. Shift reminders, iCal export and automatic on-call logging exported to CSV or via the public API into HR and payroll close the loop for working-time documentation. We found no public information on fairness or fatigue reports or enforced rest periods. 3 4 20 21 24

Report an error

The Engineering Manager

Follow-the-sun is a documented use case with daily-to-custom rotations, handoff days and times, round-robin per schedule and a fill-up safety net where a higher tier covers gaps, and my engineers can swap shifts and arrange cover themselves from the mobile app. On-call hours are logged automatically per person, shown in an on-call report and exportable as CSV or via the public API straight into our payroll. I found no public information on a warning when the same person is paged three nights in a row, or on rest-period rules, and time zones are set once per team rather than per responder. 1 2 3 4 20 21

Report an error

The Skeptic

Schedules run daily, weekly, biweekly, monthly or custom rotations with 24/7 or timed coverage, follow-the-sun example setups, and self-service offline, covering and online overrides from the web app or mobile; escalations are unlimited tiers with repeat, severity and time filters, round-robin per schedule, and a fill-up safety net that pulls people from higher tiers into coverage gaps. On-call hours are logged automatically and exported as CSV or through the public API to payroll and HR, with shift reminders by email or push, iCal calendar export, and schedules and overrides manageable via Terraform and the API. We found no public information on fairness or fatigue reporting, rest-period rules, or per-plan scheduling limits, which is what the very top of this scale asks for. 2 3 4 20 21 24

Report an error

Alert delivery, routing & noise reduction

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

Report an error

The SRE Lead

Push, SMS, voice, email and Slack on every plan, personal channel preferences with fallback channels, multi-channel persistence as the retry path, grouping, deduplication and snoozing, and live call routing documented down to dial timeouts, shuffled tier order and a press-one bridge, on your own Twilio or Bird number at zero markup. Routing reacts to severity and attributes, heartbeat monitoring covers silent failures, and maintenance windows are unlimited. We found no public information on delivery receipts, a per-alert notification log, or the countries where SMS and voice are delivered. 4 5 6 9 21 23

Report an error

The IT Operations Manager

Push, SMS, voice, email, Slack and Teams with per-user preferences, fallback channels when delivery fails and multi-channel persistence up to voice for critical incidents, plus grouping, deduplication, snoozing, routing on severity, attributes and time, maintenance windows, heartbeat monitoring, and live call routing documented down to dial timeouts, press-1 acceptance before bridging a hotline caller, and call logs kept two years. Alert acknowledgement is documented from the app or a Slack message; we found no public information on delivery receipts, a notification log per alert, or the countries where SMS and voice are delivered, which keeps this below the top band. 4 5 6 11 22 23

Report an error

The MSP NOC Lead

Push, SMS, voice, email, Slack and Teams arrive on every plan with per-user fallback channels, grouping, snoozing, maintenance windows, heartbeat and cron monitors, and live call routing on my own Twilio or Bird number with a documented dial chain, timeouts and IVR. Routing rules react to severity and attributes, so routing by customer is workable. We found no public information on delivery receipts, a per-alert notification log, or which countries SMS and voice are delivered to. 5 6 9 11 22 23

Report an error

The ICT Risk Officer

Push, SMS, voice, email, Slack and Teams are on every plan, with per-user channel preferences and fallback channels, routing on severity and attributes, grouping, snoozing and maintenance windows, plus heartbeat and cron monitoring. Live call routing is documented down to dial timeouts, IVR keypad routes and call logs with press-1 acknowledgement. We found no public information on delivery receipts per alert or the countries and channels where SMS and voice are delivered. 5 9 22 23

Report an error

The Engineering Manager

Push, SMS, voice, email and chat are all in the core product with per-user channel preferences and fallback channels, a critical incident escalates to a voice call after five minutes unacknowledged, and live hotline routing is documented down to press-1 acceptance, per-user dial timeouts and call statistics. Routing on severity, attributes and time conditions plus grouping, deduplication, snoozing, maintenance windows and heartbeat monitoring are described. I found no public information on delivery receipts, a notification log per alert, or the countries where SMS and voice are delivered. 4 5 6 9 11 21 22 23

Report an error

The Skeptic

Push, SMS, voice, email and Slack delivery with per-user channel preferences, fallback channels and push-to-SMS-or-voice persistence is documented, as are grouping and snoozing, routing on severity, attributes and other conditions, maintenance windows, heartbeats, and live call routing on your own Twilio or Bird number with dial timeouts, IVR keypads, call logs and call stats — the mechanics are unusually specific. We found no public information on which carriers deliver the outbound SMS and voice pages, on delivery receipts or a per-alert notification log, or on the countries SMS and voice reach. The "~100k Notifications / day" figure is a capacity claim, not delivery evidence. 4 5 6 9 15 22 23

Report an error

Incident response, status pages & post-incident review

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

Report an error

The SRE Lead

Incidents open from any webhook or in Teams with severities, a timeline, MTTA and MTTR reporting, and status pages documented end to end — services, subscribers, private pages, and incidents from linked integrations automatically affecting the right services. The AI story is stated plainly: no LLM inference on their servers, the customer picks the model and where it runs, with scoped tokens for agents on Pro. We found no public information on incident roles or a commander, runbooks, a video bridge, or postmortem templates with tracked follow-up actions. 5 6 11 22 24 25 27

Report an error

The IT Operations Manager

Incidents carry severities and a timeline with MTTA, MTTR and incident-count reporting plus a weekly incident report, and the status page documentation runs deep — services, subscribers, maintenances, uptime graphs, password and IP access control, publish and unpublish of public comments. Postmortems are prepared through Notion or Confluence, workflows combine conditions, actions and channels, and AI is bring-your-own-model with a clear statement that incidents are never analysed by an LLM on the vendor's servers. We found no public information on incident roles or a commander, a video bridge, in-product postmortem templates with tracked follow-up actions, or incident types with their own process. 5 6 11 22 24 25

Report an error

The MSP NOC Lead

Incidents carry severities, timelines, weekly engagement reports with MTTA and MTTR, post-mortems prepared in Notion or Confluence, and status pages with subscribers, password protection, IP filters and maintenances. The AI position is unusually clear: no vendor model touches incident data, and agents run against scoped API tokens with a bring-your-own model. We found no public information on incident commander roles, a dedicated channel with video bridge, runbooks or tracked follow-up actions, and Jira and Linear receive issues without a documented bidirectional ticket sync. 5 6 11 22 24 25

Report an error

The ICT Risk Officer

Incidents carry severities, a timeline and MTTA/MTTR reporting, postmortems are prepared pre-filled in Notion or Confluence, and status pages are documented in depth with services, subscribers, maintenance windows, uptime graphs and access controls. The AI story is bring-your-own-LLM: the vendor states it runs no model on incident data, which answers my subprocessing question but leaves that chain under our own control. We found no public information on runbooks, incident commander roles or incident types, and incident retention is six months on Standard and twelve on Pro, which is short if the record must stand up in a supervisory review. 6 11 24 25

Report an error

The Engineering Manager

Incidents carry severities and timelines, MTTA and MTTR reports exist, and status pages are documented in real depth with services, email and SMS subscribers, password and IP-based access, maintenances and uptime graphs. Post-mortems are prepared through Notion or Confluence rather than in-product templates, and I found no public information on a dedicated incident channel, a commander role, runbooks or tracked follow-up tasks. The AI story is clearly documented and unusual: no vendor model runs on our incident data, we bring our own agent and model. 5 6 9 22 24 25

Report an error

The Skeptic

Any webhook source opens an incident with severities and a timeline, messages land in the Teams or Slack channels you choose, incidents auto-resolve and reopen onto status pages with services, subscriber emails, password and IP access controls, and reports give MTTA, MTTR and incident counts, with postmortems prepared in Notion or Confluence. On AI the position is unusually clean: bring your own model, scoped API keys, and the statement that no LLM runs on your incidents on the vendor's servers. We found no public information on incident roles such as a commander, runbooks, incident types with their own process, follow-up actions tracked into Jira or Linear, or a service catalogue with dependencies. 6 21 24 25 27

Report an error

Integrations, API & administration

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

Report an error

The SRE Lead

Prometheus Alertmanager, Grafana and Sentry are named inbound among fifty-plus integrations, Slack, Teams, Jira and Linear outbound, a public REST API covering incidents, escalations, on-call, overrides, status pages, routing rules and audit logs, a native Terraform provider, OIDC with SCIM provisioning on Pro, and granular team and organization administrator roles documented page by page. The Terraform provider is documented for keys, teams and integrations, so schedules I would keep through the API rather than as code. We found no public information on bidirectional ticketing sync, multi-tenant separation for service providers, or a built-in import path from other tools. 6 8 11 20 24 26

Report an error

The IT Operations Manager

More than fifty integrations name PRTG, Grafana, Prometheus Alertmanager, Datadog, CloudWatch, Sentry and ServiceNow inbound and Slack, Teams, Jira, Linear, Notion and Confluence outbound, with inbound and outbound webhooks and flexible mapping so any tool that can send a webhook can open an incident — Checkmk is not among the tools named on the captured pages, though that webhook path would cover it. The public REST API is documented with coverage of incidents, teams, escalations, on-call, overrides, integrations, status pages, routing rules and audit logs, alongside a native Terraform provider, OIDC and SCIM single sign-on, team and organisation roles, scoped tokens and audit logging. We found no public information on bidirectional ITSM synchronisation, multi-tenant separation for service providers, or two-factor authentication. 6 8 9 10 11 24

Report an error

The MSP NOC Lead

Fifty-plus named integrations include Grafana, PRTG, Prometheus and Datadog inbound and Slack, Teams, Jira and Linear outbound, with a public REST API covering incidents, teams, escalations, on-call, overrides and routing rules, a native Terraform provider, OIDC with SCIM and audit logs attributed to API keys. Zabbix, Autotask and ConnectWise are not among the named integrations, so my monitoring and PSA stack would run on the generic webhook and the API. We found no public information on bidirectional ITSM sync, two-factor authentication or service-provider tenant separation. 6 8 11 24

Report an error

The ICT Risk Officer

More than fifty integrations including the monitoring stack we run and ServiceNow, a public REST API covering incidents, teams, escalations, on-call, overrides, status pages and audit logs, a native Terraform provider, OIDC with SCIM, and team versus organization administrator roles with scoped API keys and personal access tokens. Audit logging is an add-on covering create, update and delete attributed to the key, but it excludes reads and failed authentication, which matters when the trail must serve as evidence. We found no public information on bidirectional ITSM sync or multi-tenant separation for service providers. 8 11 24

Report an error

The Engineering Manager

More than fifty named integrations cover CloudWatch, Datadog, Grafana, Prometheus, Sentry and ServiceNow on the way in and Slack, Microsoft Teams, Jira, Linear, Salesforce and webhooks on the way out, backed by a public REST API covering incidents, escalations, on-call, overrides and audit logs, a native Terraform provider, OpenID Connect with SCIM, and team-level administrator roles with self-service overrides for members. Audit logging is positioned as an add-on or Enterprise feature. I found no public information on bidirectional ITSM sync, multi-tenant setups for service providers, or documented migration tooling from competitors. 6 8 9 11 24

Report an error

The Skeptic

Fifty-plus named integrations span monitoring (CloudWatch, Datadog, Grafana, Prometheus Alertmanager, PRTG, Sentry, ServiceNow) and collaboration and ticketing (Slack, Teams, Jira, Linear), webhook intake with flexible mapping covers anything else, a native Terraform provider provisions keys, teams and integrations, OIDC and SCIM single sign-on ships on Pro, roles split team and organization administrators, audit logs attribute creates, updates and deletes to a key, and the public API's coverage of incidents, escalations, on-call and routing rules is spelled out. We found no public information on bidirectional ITSM sync, multi-tenant or service-provider setups, or migration tooling from competitors — the Uberspace story shows one customer moved over, not how a buyer would. 6 8 9 11 24

Report an error

Platform reliability, security & compliance

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

Report an error

The SRE Lead

A public status page with component health and a displayed 99.9996 percent web-app uptime sits next to a contractual 99.9 percent monthly availability guarantee with defined fault-rectification times, Frankfurt and US-East-1 regions that are fully separated, TLS in transit with rotating-key encryption at rest, ISO 27001 certified by a UKAS-accredited body, and retention periods published to the day. We found no public information on SLA credits, multi-region failover testing, penetration tests, or DORA and NIS2 mappings; the terms state the platform is not HIPAA compliant. 13 14 17 18 22 23 24

Report an error

The IT Operations Manager

The vendor runs its own public status page with component health and a 99.9996 percent web app uptime figure, guarantees 99.9 percent monthly platform availability in its terms with five-hour rectification for serious faults, encrypts payloads in transit and at rest with rotating keys, and is ISO 27001 certified by a UKAS-accredited body, with retention documented down to seven-day server logs, call log retention and per-plan incident retention. As a hosted service independent of our own plant network that is reassuring; we found no public information on SLA credits, multi-region failover, redundant notification carriers with automatic failover, penetration tests, or DORA and NIS2 material. 11 13 14 17 18 24

Report an error

The MSP NOC Lead

A public status page, a 99.9 percent monthly availability guarantee in the terms with 99.95 percent for the delivery partner, AWS Frankfurt hosting with backups in Germany, TLS and rotating-key encryption at rest, ISO 27001 through a UKAS-accredited body, a published data processing agreement and stated retention periods. We found no public information on SLA credits, multi-region failover, penetration tests, SOC 2 or BSI C5; the terms state the platform is not HIPAA compliant and the region is fixed once the organisation is created. 13 14 17 24

Report an error

The ICT Risk Officer

The terms guarantee 99.9% monthly platform availability with serious faults rectified within five hours outside service hours, the public status page shows component uptime of 99.9996% for the web app, and the EU region runs in Frankfurt with backups in Germany, TLS in transit and rotating-key encryption at rest under an ISO 27001 certificate from a UKAS-accredited body. Retention is documented in detail, though the documentation gives different figures for call log retention. We found no public information on SLA credits, multi-region failover, SOC 2 or BSI C5, penetration tests, or a DORA or NIS2 addendum — the last is what I would need before signing. 13 14 17 24

Report an error

The Engineering Manager

A public status page with an uptime figure for the web app, a 99.9 percent monthly availability guarantee in the terms, Frankfurt or US-East hosting with the regions fully separated, TLS and at-rest encryption with rotating keys, ISO 27001 certification through a UKAS-accredited body, and detailed retention rules for call logs and server logs give us most of what an audit asks for. I found no public information on SLA credits, multi-region failover, penetration tests or guidance for DORA and NIS2 customers, and the terms state the platform is not HIPAA compliant. 13 14 17 18 23 24

Report an error

The Skeptic

The vendor runs its own status page showing "99.9996 %" uptime for the web app in the US region, the terms guarantee "99.9%" monthly availability with serious faults rectified within 5 hours, data sits in Frankfurt or US-East on AWS with backups and fully separated regions, payloads are encrypted at rest with rotating keys and in transit with TLS, ISO 27001 is certified by a UKAS-accredited body, and retention periods are itemised. Missing for an auditor: no SLA credits are stated, no failover between regions is described, outbound notification carriers are not named, the certificate's scope is not published, and the terms state outright that the platform is not HIPAA compliant. We found no public information on penetration tests or DORA and NIS2 support. 13 14 17 18 22

Report an error

European sovereignty panel opinion

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

Report an error

The SRE Lead

The contracting entity is All Quiet GmbH in Berlin with a Hamburg commercial register entry and a German VAT ID, the EU region keeps all platform data in Frankfurt with backups in Germany and never moves it to the US region, and a published data processing agreement carries a subprocessor annex with locations and transfer mechanisms — Stripe in Dublin, Sentry in Frankfurt for EU customers, Twilio in the US switched off by default for EU customers. ISO 27001 is stated and no LLM inference runs on their servers at all. We found no public information on ownership or financing beyond the German entity. 14 16 18 19 22 24

Report an error

The IT Operations Manager

The contracting entity is All Quiet GmbH in Berlin with a Hamburg commercial register number and German VAT ID, the EU region keeps all platform data in Frankfurt with backups in Germany and never moves it to the US region, a data processing agreement is published, and the subprocessor list with each provider's location and transfer mechanism sits in its annex — Twilio is off by default for EU customers and payment processing runs through Stripe in Dublin. With ISO 27001 stated as well, this is a European chain I could defend internally; the certification's scope is not spelled out and the full subprocessor enumeration lives in the agreement rather than on a public page. 14 16 17 18 19 24

Report an error

The MSP NOC Lead

The contracting entity is All Quiet GmbH in Berlin with a Hamburg commercial register number, EU customers run on AWS Frankfurt with backups in Germany and data never moved to the US region, and a published data processing agreement lists subprocessors with location and transfer mechanism in its annex. Twilio sits in the United States but is switched off by default for EU customers with the EU-US Data Privacy Framework stated, Stripe processes payment from Dublin, and no vendor-run AI touches incident data. The individual SMS and push carriers live in the agreement annex rather than on the website, so I cannot name each one from the public pages. 14 16 18 19 24

Report an error

The ICT Risk Officer

The contracting entity is All Quiet GmbH of Berlin, and for EU customers alerts, timelines, schedules and user data sit in Frankfurt on AWS with backups in Germany, never moved to the US region, which is chosen at signup and fully separated. A data processing agreement is published with a subprocessor annex stating each provider's location and transfer mechanism — Twilio in the US off by default for EU customers, Stripe in Dublin, a Sentry region in Frankfurt — and the vendor states it runs no LLM on incident data, so the AI chain remains ours. Certifications are named without their scope, and we found no public information on ownership behind the GmbH. 14 16 19 24

Report an error

The Engineering Manager

All Quiet GmbH in Berlin is the contracting entity and GDPR controller, EU customers keep incidents, alerts, schedules and users in Frankfurt on AWS with backups in Germany and never moved to the US region, and the published data processing agreement lists subprocessors with their locations in its annex. US telephony through Twilio is switched off by default for EU customers and payment runs through Stripe in Dublin, with ISO 27001 certification stated. That is a chain I can defend to our works council, though the certification scope is implied rather than spelled out. 14 16 18 19 24 27

Report an error

The Skeptic

The contract is with All Quiet GmbH in Berlin, registered at the Hamburg court with a German VAT ID; EU residency keeps all platform data, application hosting and backups in Frankfurt on AWS, fixed at signup and never moved to US-East, and the published data processing agreement carries the subprocessor list with locations and transfer mechanisms in its annex — Stripe in Dublin, Sentry split Frankfurt and US-East, Twilio in the United States switched off by default for EU customers under the EU-U.S. Data Privacy Framework. ISO 27001 is stated, GDPR compliance is claimed, and the vendor says it runs no LLM on your incident data, so the AI leg of the chain is yours to place. The certificate's scope is not published and the vendor's own website runs Google Tag and Google Ads conversion tracking, which keeps this off the very top. 14 16 18 19 24

Report an error

Pricing transparency

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

Report an error

The SRE Lead

Standard at $4.99 per user per month and Pro at $9.99 per user per month are public with their inclusions — unlimited SMS and phone calls on Standard, stakeholders free, telephony at zero markup with a $0 platform fee, AI included in Pro with no surcharge, monthly billing and cancellation at any time. The Enterprise tier is 'Talk to us', the auditing add-on and SMS subscriptions are individually unpriced, and we found no public information on VAT treatment or an annual billing option. 6 11 17 21 22 24 25

Report an error

The IT Operations Manager

Standard at "$4.99 per user / month" and Pro at "$9.99 per user / month" are published with their inclusions, unlimited SMS and phone calls on Standard, every alert channel on every plan, free stakeholders and unbilled members outside teams, zero markup on telephony with a $0 call routing platform fee, monthly billing with cancel-any-time and seat changes allowed at any time. The Enterprise tier is "Talk to us", the Auditing & Logging add-on and SMS subscribers are unpriced or custom, and we found no public information on VAT treatment or an annual billing option. 6 11 17 21 22

Report an error

The MSP NOC Lead

Standard at $4.99 and Pro at $9.99 per user per month come with unlimited users, integrations, incidents, SMS, phone calls, emails and push notifications, stakeholders free, monthly billing with cancel-any-time, telephony at zero markup on a provider number I own, and AI inside Pro with no separate fee. Enterprise is contact sales, the auditing add-on and SMS status-page subscribers are unpriced, and we found no public information on VAT treatment or an annual billing option. 1 6 11 21 22

Report an error

The ICT Risk Officer

Standard at $4.99 per user / month and Pro at $9.99 per user / month are published with their inclusions, including unlimited SMS and phone notifications, stakeholders not billed, every alert channel on every plan, monthly billing with cancellation any time and no separate AI SKU. Live call routing carries a $0 platform fee with zero telephony markup under a bring-your-own-number model where you pay the provider directly. The Enterprise tier is "Talk to us", the auditing add-on and status-page SMS subscriptions are unpriced, and we found no public information on VAT treatment. 11 17 22

Report an error

The Engineering Manager

Standard at $4.99 per user per month and Pro at $9.99 per user per month are published with their inclusions, SMS and phone calls are unlimited on every plan, live call routing carries a $0 platform fee with 0% markup on telephony, and members who only follow incidents, such as managers reading along, are not billed. The Enterprise tier is contact-sales only, the auditing add-on and SMS status-page subscribers carry no published price, and I found no public information on annual billing options or VAT treatment, so the full annual cost is not quite computable from public pages alone. 11 17 21 22 25

Report an error

The Skeptic

Two tiers are priced in public — "$4.99 per user / month" and "$9.99 per user / month" — with the entry plan bundling unlimited users, integrations, incidents, emails and push, SMS and phone calls and monitors, stakeholders who only follow incidents unbilled, AI included with no per-seat surcharge, live call routing at a "$0" platform fee and "0% Markup" telephony on your own Twilio number, monthly billing, seat changes any time, and cancellation in written form before month's end. Still not computable from public pages: the Enterprise tier is "Talk to us", the auditing and logging add-on carries no price, status-page SMS subscribers are "Custom", and VAT treatment is unstated. For a standard or pro team the annual number is derivable; for an enterprise buyer it is not. 6 11 17 22 25

Report an error

European sovereignty — proven facts

4 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

Customers who choose the US region (US-East-1) at signup are hosted outside the EU, and the same sentence also admits TADPF-certified (US) data centers, so EU storage is not guaranteed for all customers.

2/4 pts 12 Report an error
Hosting options EU region selectable unverified
Why unverified?

The region is fixed once the organization is created and cannot be switched later, and the platform is otherwise SaaS-only (the terms state it is never physically transferred to the customer).

1/1 pts 14 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The full agreement text is published on the site, but it supplements a main agreement/order confirmation rather than being concluded via an online click-through.

1/1 pts 19 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about All Quiet

Is All Quiet European?

Yes. whats-best.ai classifies All Quiet as EU-Made. Its vendor, All Quiet GmbH, is incorporated in Germany, per the vendor’s page captured 6 Nov 2026.

Where does All Quiet store data?

All Quiet stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention the US, Germany and the United States as hosting locations, per the vendor’s page captured 6 Nov 2026.

Does All Quiet have a free plan?

Not stated on the vendor’s pages as of 6 Nov 2026.

What are the best alternatives to All Quiet?

As of 18 Nov 2026, the panel rates ilert (4/5), OneUptime (3.5/5) and FireHydrant (3/5) highest among the other 16 On-Call & Incident Management products evaluated. 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: All Quiet alternatives.

Where this could be wrong

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.

Sources (27)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage allquiet.app Checked 6 Nov 2026 Details →
  2. 2 Features page (on-call) allquiet.app Checked 6 Nov 2026 Details →
  3. 3 Features page (scheduling) allquiet.app Checked 6 Nov 2026 Details →
  4. 4 Features page (escalation policies) allquiet.app Checked 6 Nov 2026 Details →
  5. 5 Features page (alerting) allquiet.app Checked 6 Nov 2026 Details →
  6. 6 Features page (incident management) allquiet.app Checked 6 Nov 2026 Details →
  7. 7 Features page (status pages) allquiet.app Checked 6 Nov 2026 Details →
  8. 8 Integrations page allquiet.app Checked 6 Nov 2026 Details →
  9. 9 Documentation docs.allquiet.app Checked 6 Nov 2026 Details →
  10. 10 API documentation allquiet.app Checked 6 Nov 2026 Details →
  11. 11 Pricing page allquiet.app Checked 6 Nov 2026 Details →
  12. 12 Security / trust page allquiet.app Checked 6 Nov 2026 Details →
  13. 13 Public status page status.allquiet.app Checked 6 Nov 2026 Details →
  14. 14 Data residency and hosting regions docs.allquiet.app Checked 6 Nov 2026 Details →
  15. 15 About page allquiet.app Checked 6 Nov 2026 Details →
  16. 16 Legal notice allquiet.app Checked 6 Nov 2026 Details →
  17. 17 Terms of service allquiet.app Checked 6 Nov 2026 Details →
  18. 18 Privacy policy allquiet.app Checked 6 Nov 2026 Details →
  19. 19 Data processing agreement (dpa, with subprocessors) allquiet.app Checked 6 Nov 2026 Details →
  20. 20 On-call schedules, rotations & escalation — found from sitemap docs.allquiet.app Checked 6 Nov 2026 Details →
  21. 21 On-call schedules, rotations & escalation — found from sitemap allquiet.app Checked 6 Nov 2026 Details →
  22. 22 Alert delivery, routing & noise reduction — found from sitemap allquiet.app Checked 6 Nov 2026 Details →
  23. 23 Alert delivery, routing & noise reduction — found from sitemap docs.allquiet.app Checked 6 Nov 2026 Details →
  24. 24 Incident response, status pages & post-incident review — found from sitemap allquiet.app Checked 6 Nov 2026 Details →
  25. 25 Incident response, status pages & post-incident review — found from sitemap docs.allquiet.app Checked 6 Nov 2026 Details →
  26. 26 Integrations, API & administration — found from sitemap allquiet.app Checked 6 Nov 2026 Details →
  27. 27 Integrations, API & administration — found from sitemap allquiet.app Checked 6 Nov 2026 Details →