How we rank these tools — 4-step process
-
1
European ownership, verified
The company is headquartered and incorporated in the EU, EEA or Switzerland, and processes customer data in Europe. A US parent company disqualifies a tool from this page regardless of where its servers are.
-
2
Category fit and hands-on review
What the tool actually does, who it suits, and where it falls short — checked against the vendor’s own documentation, changelog and pricing page rather than its marketing copy.
-
3
Compliance and pricing check
GDPR posture, hosting location and the prices quoted on this page are verified against the vendor’s public pricing before publication, and re-checked when we revisit the category.
-
4
Position on this page
Placement on this page can be paid, and that can affect which tools appear here and the order they appear in. It never buys a good review: a tool that fails the checks above is not here at any price, and payment does not change the shortcomings we write about. A vendor can ask us to correct a factual error — not to remove a criticism.
Vendors can pay for visibility on this page. It never changes what an entry says about a product, including the criticism, and we earn nothing when you click through to a vendor. Paid placement can affect which tools appear here and the order they appear in. Editorial policy
Best European Alternatives to PagerDuty
Privacy-focused incident management and on-call scheduling platforms.
Elastic APM
Application performance monitoring & alerting
Key takeaways
- PagerDuty's European region runs on AWS in Frankfurt and Ireland, is available on every pricing plan, and an existing account can be relocated by Professional Services for a fee — which is a better position than either Sentry or Datadog offers.
- The bill counts responders, not machines: $21 per user per month on Professional billed annually, $41 on Business, across everyone who might be woken.
- Opsgenie stopped being sold on 4 June 2025 and disappears on 5 April 2027, which removes the main source of price pressure on PagerDuty.
- Elastic APM, the one tool on this page, ships a PagerDuty connector rather than a replacement for it: no schedules, no escalation policies, no voice calls.
- Better Stack is the name most often offered as the European answer, and its own terms of use name Better Stack, Inc., a Delaware corporation, as the provider.
Why people leave PagerDuty
PagerDuty is bought for one guarantee: that at three in the morning a named person's phone rings, and that if nobody picks up within the minutes you specified, the next phone rings. The integrations, the status pages and the analytics are all built around that promise. It is also the only promise in this category that no tool on this shortlist makes.
So dispose of the argument you came expecting. PagerDuty runs two service regions, and the European one sits on AWS in Frankfurt and Ireland.
Every pricing plan can use it, EU accounts live on a subdomain with eu in it, and if you are on the wrong one the documentation offers a way out: Professional Services may be able to move the account to another region, usually for a fee. Among the American tools in this part of the stack, that is the most accommodating position on record — Sentry documents no such move at all.
What is left is the shape of the bill and the shape of the market. Professional is $21 per user per month billed annually and $25 without the commitment; Business is $41 and $49.
The users are not machines or events but the people who might be woken, so the meter is a headcount that has to be deep enough to be humane. And the competitor that used to hold that price down is closing: Opsgenie stopped being sold on 4 June 2025 and shuts down entirely on 5 April 2027.
- The meter is a person on a rota Everything else in observability charges for machines, events or gigabytes. On-call charges for humans, which inverts the usual incentive. A rota of four people is brutal and a rota of eight is civilised, and the civilised one costs twice as much on Professional and twice as much again on Business. Teams facing a budget review shrink the rota rather than the estate, and a shorter rota is exactly the wrong thing to buy with the saving.
- Residency is answered here; disclosure is not Give PagerDuty credit: the EU region is genuinely available on every plan, and an existing account can be relocated through Professional Services instead of being abandoned. What that changes is where the incident records sit. PagerDuty, Inc. remains at 600 Townsend Street in San Francisco, certified under the EU-U.S. and Swiss-U.S. Data Privacy Framework with the Federal Trade Commission holding jurisdiction over that certification, and represented in the EU by an outsourced Article 27 contact rather than an operating company. Choosing Frankfurt does not move the company.
- The alternative that kept it honest is being switched off Opsgenie reached end of sale on 4 June 2025 and will be shut down on 5 April 2027, with customers directed into Jira Service Management, where the alerting and on-call features now live. If your last renewal negotiation used an Opsgenie quote as leverage, that lever is gone. The replacement route is not a jurisdictional improvement either: Atlassian's own product terms name OpsGenie, Inc. as the entity behind Opsgenie and Atlassian Pty Ltd, an Australian company, as the entity behind Jira Service Management. Neither is European.
- A rota is a personnel record as well as an operational one The account accumulates the mobile numbers of everyone who can be paged, their notification rules, which nights each of them was required to be reachable, how long they took to acknowledge, and whatever they typed into an incident at four in the morning. That is a more personal dataset than a stack trace or a host metric, and it is the one part of the observability stack that describes employees rather than systems.
What you have to replace, not just match
Split what PagerDuty does into four jobs before you compare anything, because they are usually bought as one thing and they do not move as one thing.
Detection is knowing that something is wrong. Routing is deciding which team owns it and at what severity. Delivery is the part people actually pay for: a phone that rings, again, and then someone else's phone, until a human acknowledges. And the record afterwards is the timeline, the notes, the postmortem and the analytics that tell you which service is burning your nights.
Elastic APM covers detection and a useful slice of routing — Kibana rules fire into connectors for email, Slack, Teams, webhooks, Jira and ServiceNow, and it can open a case. It does not cover delivery, and it does not pretend to: PagerDuty is one of the connectors it ships.
That is the honest shape of this page. If the phone call is what you are buying, the European vendors that match PagerDuty are on-call specialists rather than observability platforms, and ilert GmbH in Cologne is the clearest of them — made and hosted in Germany, ISO 27001 certified, free for up to five users.
The alternatives compared
| Position | Tool | Headquarters | Pricing | Jurisdiction |
|---|---|---|---|---|
| #1 | Elastic APM | Amsterdam, Netherlands | Free tier / custom pricing | EU (Netherlands) |
How each alternative compares to PagerDuty
- Which law reaches it. EU (Netherlands). PagerDuty is run from the United States, so the CLOUD Act obliges the provider to hand over data on a valid order regardless of which country the servers are in.
- Where the data sits. Self-hosted, or Elastic Cloud in EU regions.
- Source code. Open source, where PagerDuty is not: you can read what it does rather than take the description on trust.
- Independently checked. GDPR.
Best for: Teams keeping PagerDuty for the wake-up and moving everything beneath it to Europe
Elastic APM is the only tool on this page, and it is important to be precise about what it is doing here. It is not an on-call platform. It is the layer that decides an alert should exist at all, and its relationship with PagerDuty is a connector rather than a contest — Kibana ships one, next to Opsgenie and xMatters, because paging is understood to be a separate product.
What that buys you against PagerDuty is a change in volume rather than in vendor. Most rotas are noisy because the alerting underneath them is threshold-based and blind to context: a host is at 90 per cent, a queue is deep, a check timed out.
Rules written over traces, metrics and the log lines from inside the same request fire on evidence that something is actually broken, and the pages that never get sent are the ones that cost nothing to route. On a rota of six, cutting the night-time page rate is worth more than any licence negotiation.
The second gain is where the record ends up. Run the stack yourself and the alert history, the investigation and the log lines behind it stay on hardware you control, while PagerDuty keeps the incident timeline and the responder details in one of its two regions.
The cost is the familiar one: the company behind it, Elastic N.V., is registered in Amsterdam, but somebody still has to run the cluster, and everything above Elastic's free tier ends in a sales conversation rather than a price list.
What Elastic APM does better than PagerDuty
- Nothing in it is priced per responder, so widening a thin rota costs hardware rather than another $21 a head each month
- Alerts are derived from traces, metrics and logs in one store, so fewer of them are noise that has to be routed to a human at all
- Self-managed, the alert history and investigation notes never reach a vendor, where PagerDuty holds the incident timeline and responder details in one of its regions
- An AGPL option for Elasticsearch and Kibana has existed since September 2024, announced at the end of that August, so the alerting layer needs no commercial licence to run
- No Article 27 representative and no Data Privacy Framework certification stand between you and the supplier, because the supplier is registered inside the EU
Where Elastic APM is a step down from PagerDuty
- No on-call schedules, no escalation policies, no voice calls and no acknowledgement tracking: it integrates with PagerDuty instead of replacing it
- An alert that nobody opens simply sits there, where PagerDuty escalates to the next person automatically
- No status pages, no stakeholder notifications and nothing resembling PagerDuty's incident analytics
- Somebody has to keep a cluster healthy, and the alerting is only as reliable as the thing it runs on — a rota does not page you when the pager itself is down
- The commercial tiers are quoted rather than listed, so the comparison against a published per-seat price has to start with a sales call
Standout against PagerDuty. It is the only tool here that can reduce the number of pages rather than route them more cheaply, and on a small rota that is worth more than the licence it would have saved.
What actually breaks when you switch
Contact details are the first thing that does not move. Mobile numbers, personal notification rules, quiet hours, holiday overrides and the order in which each engineer wants to be reached are per-person records that exist in PagerDuty's user profiles and export into nothing useful. Every responder has to re-enter their own, and somebody has to verify that the escalation really rings — with a deliberate test page, at an unsociable hour, before the first shift depends on it.
Then there are the keys. More than 750 integrations means a routing key pasted into monitoring tools, cloud alarms, CI pipelines, a Lambda and at least one script written by someone who has left. Those senders keep firing at the old endpoint long after anyone is watching it, so the migration is not finished when the new rota goes live; it is finished when the old account stops receiving events.
And on-call cannot be trialled the way software can. Either the system pages you or it does not, and the answer only arrives during an incident. The workable approach is to route one low-severity service to the new tool for a month while the things that wake people stay where they are — which means two subscriptions for that month, and a team that has agreed in advance which alerts belong to which system.
Can I move an existing PagerDuty account into the EU region?
Yes, which is unusual enough in this market to be worth checking before you plan anything more drastic. PagerDuty operates a United States region and a European one, the European region runs from AWS data centres in Frankfurt and Ireland, and the documentation states that all pricing plans are available in any service region. EU accounts are recognisable by the eu in the subdomain.
Relocation is a Professional Services engagement rather than a setting, and the documentation says there is typically a fee. The alternative it offers is the one every other vendor offers by default: open a new account in the region you want, rebuild the configuration and accept that the history stays behind.
Get the quote before assuming the answer. If the requirement came from a procurement rule about where records are stored, a fee that lands somewhere between a few thousand euros and nothing at all is cheaper than replacing the system that wakes your engineers.
Does anything on this page actually replace the pager?
No, and a page that implied otherwise would be doing you harm. Elastic APM detects the problem and can send a message about it. What it has no concept of is a schedule with handovers, an escalation policy with timeouts, a repeated voice call, an acknowledgement that stops the escalation, or an override because somebody is on a plane.
The proof is in Elastic's own connector list. Alongside email, Slack, Teams, webhooks, Jira and ServiceNow sit connectors for PagerDuty, Opsgenie and xMatters, because paging is understood to be somebody else's job. Elastic is the thing that decides an alert should exist; it is not the thing that guarantees a person hears it.
Teams occasionally try to build the missing half out of a Slack connector and a rota in a spreadsheet. It works until the first incident that begins at two in the morning with every phone face-down and on silent, which is the exact scenario the product you are cancelling was purchased for.
Can the per-seat bill be brought down without shrinking the rota?
Partly, and the first lever is licence mix rather than negotiation. Most organisations put people into PagerDuty who will never be paged — managers, account teams, whoever wants to see the incident. Those are stakeholder licences, sold as an add-on, rather than full responders, and auditing that split is usually the largest single saving available.
The second is to be honest about how small you are. The free plan covers up to five users with one on-call schedule and one escalation policy, 750-odd integrations and an allowance of 100 international phone and SMS notifications a month. For a five-person team with a single rota that is not a demo; it is a working on-call system, and the notification allowance is the ceiling to watch rather than the user count.
What does not work is trimming responders. Every name removed from the rotation lands on the names that remain, and the cost of that shows up in attrition rather than on the invoice, where nobody is looking for it.
What should Opsgenie customers do before April 2027?
Decide deliberately, because the default path is a decision too. Opsgenie stopped being sold on 4 June 2025, continues to run until 5 April 2027, and Atlassian has moved its alerting and on-call capabilities into Jira Service Management with an automated migration for existing data and configuration.
If your team already lives in Jira, that route is the least work and it does not answer a jurisdiction question: Atlassian's product terms list OpsGenie, Inc. as the contracting entity for Opsgenie and Atlassian Pty Ltd, in Australia, for Jira Service Management. You are moving between two non-European suppliers.
If the shutdown is being used as the moment to reconsider, it is a good moment. You are rebuilding schedules, escalation policies and integration keys either way, and that is the same work whether the destination is Jira Service Management, PagerDuty or a European on-call vendor. Do the comparison once, now, rather than twice.
Which one to pick
If you are here because somebody asked where the incident data is stored, PagerDuty has already answered it and you may not need this page. The European region is on every plan, and an existing account can be relocated through Professional Services for a fee. Ask for that number first.
If you are here because the bill grows every time the rota gets deeper, the lever is the licence mix rather than the country. Audit who is a responder and who only wants to be told, move the second group to stakeholder licences, and if you are five people with one rotation, check the free plan before you do anything else.
If you are here because an American company should not hold your engineers' phone numbers and their night shifts, Elastic APM is not the answer to that question — it connects to PagerDuty. The answer is a European on-call vendor, and ilert GmbH in Cologne is the one whose address, hosting and ISO 27001 certification check out. Read the terms of anything else recommended to you as European, because the best-known candidate contracts through a Delaware corporation.
And if what you want is simply to be woken less often, that is what Elastic APM is doing on this page. Better alerting underneath the rota is a cheaper quarter than replacing the rota, and it is the only change here that improves the thing everyone actually complains about.
Frequently Asked Questions
None of them is on this page, and it is better to say so. Elastic APM replaces the detection layer underneath PagerDuty and integrates with PagerDuty rather than displacing it.
If what you need is the rota and the phone call, look at a European on-call specialist instead: ilert GmbH in Cologne is made and hosted in Germany with ISO 27001 certification and a free tier for up to five users. The realistic plan for most teams is to move the telemetry to Europe and leave the paging where it works.
Yes, and more completely than most American vendors in this stack. There are two service regions, the European one running on AWS in Frankfurt and Ireland, and PagerDuty states that all pricing plans are available in any service region — so it is not gated behind Enterprise. European accounts are identifiable by the eu in their subdomain.
It can, which separates PagerDuty from most of its neighbours. The documentation says Professional Services may be able to migrate an account to a different service region, typically for a fee, and offers the usual fallback of creating a fresh account in the target region and rebuilding the configuration without the history. Ask for the quote before assuming a migration project is the only option.
PagerDuty, Inc., at 600 Townsend St. #200, San Francisco, CA 94103. The privacy policy names an outsourced EU representative reachable through gdprlocal.com rather than a European operating company, states compliance with the EU-U.S. and Swiss-U.S. Data Privacy Framework, and confirms that the Federal Trade Commission has jurisdiction over that compliance. Standard Contractual Clauses cover transfers outside the framework.
Professional is $25 per user per month, or $21 billed annually. Business is $49 and $41. Enterprise is quoted. AIOps, stakeholder licences, status pages and live call routing are add-ons rather than plan features, so the list price is a floor rather than an estimate.
For a genuinely small one, yes. It covers up to five users, one on-call schedule, one escalation policy, more than 750 integrations and 100 international phone and SMS notifications a month. The constraint that bites first is usually the notification allowance during a bad week, not the five-user limit, and the single escalation policy stops working the moment you have two teams with different owners.
No. Elastic detects and routes: rules fire into connectors for email, Slack, Microsoft Teams, webhooks, Jira, ServiceNow and others, and it can open a case to hold the investigation. Scheduling, escalation timeouts, voice calls and acknowledgement tracking are absent, which is why PagerDuty, Opsgenie and xMatters appear in that same connector list.
Opsgenie reached end of sale on 4 June 2025 and will be shut down on 5 April 2027, after which it is no longer accessible. Atlassian has folded the alerting and on-call features into Jira Service Management and provides an automated migration for existing data and configuration. Anyone still on it has until then to move, and the work involved is the same work any other on-call migration requires.
Check the terms before you rely on it for that reason. Better Stack's own terms of use name Better Stack, Inc., a Delaware corporation, as the entity providing the service, even though its engineering is well known to sit in Prague.
The product itself is strong on this ground — a responder licence is $34 a month, or $29 billed yearly, with unlimited phone call and SMS alerts, and telemetry can be kept in a European region. If your reason for leaving PagerDuty is the cost or the ergonomics, it competes. If your reason is which country can compel disclosure, the contracting entity is the thing to read.
Who worked on this review
Explore More European Alternatives
Discover privacy-focused European alternatives to other popular US tech services.