Skip to content

Sentry hosting in Germany: why GDPR compliance is not a nice-to-have

Sentry SaaS vs. self-hosted in Germany: EU data residency, CLOUD Act, subprocessors and why managed Sentry hosting is the safest route to GDPR compliance.

9 min readNETZFABRIK Team

Key points

  • Even with Sentry's EU region, user accounts, 2FA data and integration metadata sit in the US.
  • Sentry is a US company and subject to the CLOUD Act, regardless of the server location.
  • Self-hosting solves the privacy problem but means operating more than 20 services.
  • Managed Sentry hosting in Germany brings data residency and a data processing agreement with a German company, without the ops effort.

Sentry in the stack: a standard, but not without risk

Over the past few years Sentry has become the de facto standard for application monitoring and error tracking. React frontend, Django backend or mobile app: integration takes minutes, and the SDK ecosystem covers practically every language and framework. For engineering teams Sentry is no longer optional tooling but a fixed part of the observability stack.

The problem is not the tool itself but the way it is operated. By design Sentry captures highly sensitive data:

  • Stack traces

    with variable contents

  • Breadcrumbs

    with user interactions

  • Session replays

    with potentially personal information

  • Request headers

  • IP addresses

  • Device fingerprints

With the standard SaaS offering all of this flows to infrastructure operated by Functional Software, Inc., a US company.

For companies subject to the GDPR this is not a trivial detail. It is a compliance risk that has to be actively managed.

Sentry's EU region: progress with gaps

Sentry has responded and has offered EU data residency since 2024. When a new organisation is created you can choose between the US and the EU location. EU data sits on Google Cloud Platform in Frankfurt, which is a good step in principle. The option is available on all plans, including the free Developer plan, and there is no surcharge.

A closer look, however, reveals structural gaps that matter for full GDPR compliance.

In practice this means that even with the EU region, personal data flows to the US. The email address, name and authentication data of every user with access to the Sentry organisation are processed on US infrastructure. From a GDPR perspective this is a third-country transfer that needs its own legal basis.

Another point: existing Sentry organisations cannot be migrated to the EU region afterwards. A new organisation has to be created, with a separate subscription, separate users and separate projects. For teams already running Sentry in production that is a considerable migration effort.

CLOUD Act and the residual DPF risk

Even if all data physically sits in Frankfurt, Sentry is a US company and therefore subject to the US CLOUD Act. This law empowers US authorities to demand data from US companies regardless of where it is stored. That explicitly includes data of European customers on European servers.

The European Data Protection Board (EDPB) has taken a clear position: disclosing personal data solely on the basis of the CLOUD Act is generally not permitted and can violate Art. 48 GDPR. A breach falls under the higher fine range of Art. 83(5) GDPR: up to 20 million euros or 4 % of worldwide annual turnover.

The legal basis for transatlantic data transfers is currently the EU-U.S. Data Privacy Framework (DPF), which was upheld by the CJEU in September 2025. Sentry has self-certified under the DPF. But the stability of this framework is by no means assured. NOYB filed a new action immediately after the ruling, and political observers point out that the current US administration regards the privacy executive orders introduced under the Biden administration as a bureaucratic burden. In the context of the broader deregulation agenda that argument carries weight.

Subprocessors and data processing agreements

An often underestimated aspect: Sentry uses subprocessors that in turn process personal data. According to Sentry's subprocessor list (version 2.2.0, May 2025) these include Google Cloud Platform and other US-based services. Each of these sub-engagements is subject to the same GDPR requirements for a legal basis, technical and organisational measures and contractual safeguards.

Especially relevant for enterprise customers: to date Sentry has no legal entity of its own in the EU. The contract is concluded with Functional Software, Inc. in San Francisco. For many companies, particularly in regulated environments (finance, healthcare, the public sector), that is a knockout criterion. In the community discussion on GitHub users call this a real dealbreaker that forces them to evaluate alternatives to the SaaS product.

Sentry does offer a self-service DPA (Data Processing Addendum), but the question remains: is a DPA with a US company without an EU establishment enough to demonstrate compliance to a German supervisory authority? The answer depends on the specific context, but the risk lies with the controller, not with Sentry.

Self-hosted Sentry: full control, full effort

The obvious answer to all of these problems is to host Sentry yourself. Sentry is open source (BSL-licensed), and the self-hosted variant lets you run the entire infrastructure on your own servers in Germany. No third-country transfer, no CLOUD Act, no US subprocessors: the GDPR problem is structurally solved.

The downside: self-hosted Sentry is not "docker compose up" and done. Production operation means managing more than 20 services:

  • Kafka
  • ClickHouse
  • PostgreSQL
  • Redis
  • Snuba
  • Relay
  • Symbolicator
  • and more

On top of that come regular updates to new releases, monitoring of the Sentry infrastructure itself, backup strategies, scaling as event volume grows and security hardening of the whole stack.

For an average engineering team that is considerable ops overhead that distracts from the actual product. Even experienced DevOps engineers report that upgrading between major versions is an error-prone process that needs thorough testing and often manual intervention. And that for a tool that is supposed to find errors, not produce new ones.

Managed Sentry hosting: the best of both worlds

This is exactly where managed Sentry hosting comes in. The idea: Sentry runs self-hosted, but on dedicated infrastructure in Germany, fully managed by a specialised hosting provider. The result meets the GDPR requirements for data residency and data processing and keeps the operational effort away from the engineering team.

In concrete terms: the Sentry instance runs on servers in a German data centre, the hosting provider takes care of installation, configuration, updates, backups and monitoring, and a data processing agreement under Art. 28 GDPR is concluded directly with a German company. The engineering team receives a ready-to-use login and can focus on what Sentry is for: finding and fixing errors.

At NETZFABRIK we run managed Sentry hosting on our own infrastructure in Frankfurt am Main. The instance is ready within a few hours, updates are applied promptly after release, and the whole operation is secured by redundant systems and professional monitoring. Because it is a dedicated instance, our customers keep full control over configuration, data retention and access management, without the operating costs of running it themselves.

See managed Sentry hosting at NETZFABRIK

Comparison: SaaS vs. self-hosted vs. managed

CriterionSentry SaaS (EU)Self-hostedManaged hosting (DE)
Data residency in GermanyPartlyYesYes
No US subprocessorNoYesYes
No CLOUD Act riskNoYesYes
DPA with a German companyNoYour responsibilityYes
Ops effort for your teamNoneHighNone
Update managementAutomaticManualManaged
Full control over the instanceNoYesYes
Independence from the DPFNoYesYes

Conclusion: GDPR compliance is a management matter

Sentry is an excellent tool, no doubt about it. But how and where it is operated is not a purely technical decision. It directly affects a company's compliance posture. Sentry's EU region is a step in the right direction but does not solve everything: user account data in the US, US subprocessors, no EU legal entity and the latent uncertainty of the Data Privacy Framework remain as residual risks.

For companies that treat GDPR compliance as an actual requirement rather than a checkbox, the way leads through self-hosted or managed hosting. And for everyone who wants to focus on their product instead of infrastructure ops, managed Sentry hosting is the most pragmatic route to a clean compliance architecture.

Run Sentry GDPR-compliant, without the ops effort

Managed Sentry hosting on dedicated infrastructure in Frankfurt am Main. Fully configured, regularly updated, with a data processing agreement under Art. 28 GDPR.