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 Engineering Manager

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Engineering Manager

Panel median The Engineering Manager This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Engineering Manager
On-call schedules, rotations & escalation 4 of 5 4 of 5
Alert delivery, routing & noise reduction 3.5 of 5 3.5 of 5
Incident response, status pages & post-incident review 3 of 5 3.5 of 5
Integrations, API & administration 3.5 of 5 3.5 of 5
Platform reliability, security & compliance 3 of 5 3 of 5
European sovereignty 4 of 5 4 of 5
Pricing transparency 3 of 5 3.5 of 5

On-call schedules, rotations & escalation

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

Alert delivery, routing & noise reduction

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

Incident response, status pages & post-incident review

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

Integrations, API & administration

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

Platform reliability, security & compliance

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

European sovereignty

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

Pricing transparency

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

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 →