The EU-hosted, GDPR-native Sentry alternative
MOJAQ is error tracking for EU teams: keep the Sentry SDKs you already use, but your stack traces stay in the EU under a GDPR-native DPA — alongside analytics, uptime, render, feature flags and realtime in one platform.
EU-hosted in Helsinki · GDPR-native · free during the beta, no fixed end date
MOJAQ vs Sentry
| MOJAQ | Sentry | |
|---|---|---|
| Data residency | EU only — Helsinki, Finland | US by default; EU region on higher tiers |
| GDPR / DPA | GDPR-native, DPA included | DPA available |
| SDK compatibility | Sentry-compatible SDKs — drop-in | Native Sentry SDKs |
| Issue grouping & releases | Yes | Yes |
| Also included | Analytics · Uptime · Render · Flags · Realtime | Errors + APM (priced separately) |
| Price | Free during the private beta | Paid, scales with event volume |
Why EU teams move error tracking off Sentry
Error events are rarely anonymous. A single exception can carry the request URL, headers, a user id, an IP address and fragments of application state, which is personal data under GDPR even after you scrub the obvious fields. When that stream defaults to US ingestion, error tracking quietly becomes a cross-border transfer your security and legal teams keep having to justify.
MOJAQ keeps the whole pipeline in Helsinki, with a DPA included and no US transfers. For teams under GDPR, selling to the public sector, or answering enterprise security reviews, that turns a recurring compliance conversation into a settled one, without giving up the crash visibility developers rely on.
What stays the same when you switch
Because MOJAQ is compatible with the Sentry SDKs, the migration is a configuration change, not a rewrite. Your instrumentation, issue grouping, releases, environments, breadcrumbs and source-map matching keep working: you point the DSN at MOJAQ and verify the first event arrives.
What you add is the rest of the platform. The same API key gives you cookieless analytics, uptime monitoring, render, feature flags and realtime, so a new regression can be lined up against a deploy and its traffic in one place instead of four dashboards.
Switching is easy
Already on Sentry? Point your existing SDK's DSN at MOJAQ — it speaks the Sentry protocol, so there are no code changes. Capture, grouping and release tagging keep working.
Questions
Is MOJAQ a drop-in Sentry replacement?
MOJAQ is compatible with the Sentry SDKs, so for most apps you change only the DSN — error capture, fingerprint grouping and release tagging behave the same.
Where is my error data stored?
In the EU — Helsinki, Finland. Nothing is transferred to the US, and a GDPR DPA is included by default.
What does it cost?
MOJAQ is free during the private beta, with no fixed end date. Paid plans are announced in advance.
Move your error tracking to the EU
One API key. Six tools. Your data in Helsinki. Free while we're in beta.
Request beta access →