Offen Fair Web Analytics vs TelemetryDeck

Compare Offen Fair Web Analytics and TelemetryDeck on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Matomo, Mixpanel

Offen Fair Web Analytics

Germany· Web Analytics

Needs review

Shortlist when you want self-hosted, Apache-2.0 analytics that only measures after opt-in, encrypts events in the browser, and lets visitors open their own data in the Auditorium. Skip when you need cookieless full-coverage metrics, session replay/heatmaps, or zero-ops managed EU hosting—consider Plausible, Pirsch, or Friendly Analytics instead.

Opt-in onlyBrowser E2E encryptionSelf-hostedApache-2.0Visitor data accessBerlin-based project

View listing Visit Website

TelemetryDeck

Germany· Web Analytics

Needs review

Shortlist TelemetryDeck for multi-platform app analytics when on-device double-hash anonymization, cookieless signals, open SDKs, and a German-operated SaaS matter more than self-host or profile-heavy product suites. Skip when you need website-only simplicity (Plausible/Pirsch), full self-host control (Matomo/Plausible CE), or Mixpanel/Firebase-class identity and ecosystem depth—and have legal review the vendor’s “not personal data / not Art. 28 processor” DPA model plus AWS/Azure subprocessors.

Multi-platform app SDKsOn-device anonymizationCookieless signalsEU-operated (DE GmbH)Open-source client SDKsManaged SaaS (no self-host)

View listing Visit Website

Highlighted rows differ between the two products.

Offen Fair Web Analytics vs TelemetryDeck: Snapshot
Feature	Offen Fair Web Analytics	TelemetryDeck
Country of origin	Germany	Germany
Category	Web Analytics	Web Analytics
Open source	Yes	No
Self-hosted	Yes	No
Headquarters	Germany	Germany
Legal entity	Public legal notice lists Frederik Ring, Berlin (offen.software); product authors Frederik Ring and Hendrik Niefeld—no separate GmbH name verified on imprint	TelemetryDeck GmbH, Von-der-Tann-Str. 54, 86159 Augsburg (HRB 37541)
Governing law	Germany (indicative from Berlin imprint)	Germany (terms reference German law / Bayern courts; consumer protections may vary)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Low	Medium
Hosting / residency	Product is operator self-hosted (your VPS/cloud/on-prem). No Offen multi-tenant analytics SaaS or vendor subprocessor list for visitor events. Related marketing site (offen.software) names Hetzner Online GmbH (Germany) as host—not the analytics data path. Optional community deploys include Heroku (operator choice).	Product analytics: Microsoft Azure Amsterdam (NL), AWS Frankfurt (DE), Hetzner Falkenstein and Nürnberg (DE) per Privacy FAQ. Website privacy policy lists Microsoft Ireland Operations Ltd, Amazon Web Services Inc (US entity), and Hetzner Online GmbH as hosters with claimed Art. 28 contracts for site hosting. Account-side: HubSpot Inc (US CRM), Brevo/Sendinblue GmbH (DE email), Stripe payments per terms.
Summary	Open-source, self-hosted web analytics with opt-in consent, browser-side end-to-end encryption, and a shared Auditorium so visitors can see and control their own usage data.	German privacy-first app analytics SaaS: lightweight multi-platform SDKs, on-device double-hash anonymization, cookieless signals, and managed dashboards for mobile, desktop, and web products.
Tags	analytics privacy gdpr open-source self-hosted opt-in e2e-encryption	analytics privacy gdpr app-analytics cookieless mobile-sdk saas germany free-tier

At a glance: Offen Fair Web Analytics vs TelemetryDeck
At a glance	Offen Fair Web Analytics	TelemetryDeck
HQ / authors	Berlin, Germany (Frederik Ring & Hendrik Niefeld)	Not listed
License	Apache-2.0 (code/docs); logo CC-BY-NC-ND-4.0	Not listed
Delivery	Self-host only (binary, Docker, community deploys)	Not listed
Consent model	Opt-in only; first-party cookies	Not listed
Default retention	6 months (configurable shorter)	Not listed
Funding note	NLnet NGI support (project-stated)	Not listed
HQ	Not listed	Augsburg, Germany (TelemetryDeck GmbH)
Legal entity	Not listed	TelemetryDeck GmbH · HRB 37541 · VAT DE353418916
Product type	Not listed	Managed app/web analytics SaaS
Self-host	Not listed	No (open-source client SDKs only)
Hosting (vendor)	Not listed	Azure Amsterdam; AWS Frankfurt; Hetzner Falkenstein/Nürnberg
Commercial model	Not listed	Free tier + monthly event volume; plan-based query retention
DPA	Not listed	Public DPA/AVV asserting anonymized non-processor model; TOMs on request

Key capabilities: Offen Fair Web Analytics vs TelemetryDeck
Key capabilities	Offen Fair Web Analytics	TelemetryDeck
Opt-in only	Yes	Not listed
Browser E2E encryption	Yes	Not listed
Self-hosted	Yes	Not listed
Apache-2.0	Yes	Not listed
Visitor data access	Yes	Not listed
Berlin-based project	Yes	Yes
Multi-platform app SDKs	Not listed	Yes
On-device anonymization	Not listed	Yes
Cookieless signals	Not listed	Yes
Open-source client SDKs	Not listed	Yes
Managed SaaS (no self-host)	Not listed	Yes

Offen Fair Web Analytics

Opt-in only collection with first-party cookies
No analytics events are recorded until the visitor actively consents. Cookies are first-party and the tracker is meant to run on a same-site subdomain so third-party cookie restrictions and cross-site tracking models do not apply. Visitors who never opt in leave no usage trail—expect lower absolute volumes than cookieless tools that measure by default.
Browser-side end-to-end encryption of usage events
Clients encrypt usage data before it leaves the browser; the server stores ciphertext and cannot decrypt events alone. Only the visitor (via their cookie) and the matching operator account can open that visitor's data in the Auditorium. Practical impact: a compromised database or overly broad ops access does not yield plaintext browsing histories the way a typical self-hosted analytics DB would.
Auditorium for both operators and visitors
Operators see aggregates across pages where the installation is active (unique users/sessions, top pages, filters). Each opted-in visitor can open the same style of UI for their own data only, with plain-language metric explanations, and can delete data or fully opt out later. This is the fair design point: measurement is not a one-way glass.
Essential metrics without IP or User-Agent capture
Dashboards cover real-time activity, page views, unique users and sessions, bounce rate, returning users, top pages, referrers, UTM campaign/source, landing and exit pages, weekly retention, and load time. Location is country-level from timezone mapping; mobile share uses orientation capability—not IP geolocation or UA parsing. No heatmaps, session replay, or warehouse-grade product analytics.
Lightweight self-host: binary, Docker, SQLite or SQL
Production installs use a single binary (Linux/Windows/macOS) or the offen/offen image; docs also cover Heroku, Uberspace, and YunoHost. Default store is SQLite; MySQL and Postgres are supported. AutoTLS can request Let's Encrypt certificates. Config is environment variables or offen.env. You own uptime, backups, SMTP for password reset, and the subdomain layout.
Multi-site accounts, teams, and short retention
One installation can cover multiple websites with shared team access. Default retention is six months with automatic deletion; operators can shorten retention (e.g. 12 weeks, 30 days, 7 days) knowing shorter values purge older events on startup. Consent banner appearance is customizable; UI locales include EN, DE, FR, ES, PT, and VI.

TelemetryDeck

Multi-platform SDKs and HTTP signal ingest
Official clients for Swift (Apple platforms including visionOS), Kotlin/Android, JavaScript, Flutter, React/React Native, Vue, and a one-line web snippet, with community Unity, Rust WASM, and Vapor clients. Any runtime can POST to the documented ingest API. Suits cross-platform product teams; not a drop-in replacement for a full marketing tag manager suite.
On-device salt-and-hash user anonymization
Client SDKs salt and hash user identifiers on device; the server applies a second salt and hash so neither side can reverse the original ID. App analytics docs state IPs are never stored for signals; timestamps are rounded to the hour. Limit: publishers must not put personal data in custom metadata, or the anonymization model breaks for that payload.
Cookieless app and web tracking model
No analytics cookies for product signals: apps keep a local anonymized identifier; web derives a hashed identifier from date, site, and partial IP context without storing full IPs. Aimed at leaner consent UX and simpler App Store privacy labels versus cookie-based trackers—still confirm legal posture for your jurisdiction and configuration.
Product dashboards, funnels, TQL, and notebooks
Pre-built overview and AARRR-style customer journeys (acquisition, activation, retention, revenue), technical metrics (devices, versions, errors), visual funnel builder, Explore for raw signal types, TelemetryDeck Query Language for advanced insights, and Notebooks mixing live charts with markdown. Test mode separates IDE/dev traffic from production.
Volume-based SaaS with free tier and plan retention
Commercial model is monthly event/signal volume with a free tier and paid plans that differ on included volume and how long data stays query-ready (cold storage may hold older data). Free accounts can stop ingesting when the budget is exhausted; paid plans warn and may auto-upgrade after sustained overage. Check current limits on the vendor dashboard—no self-host option.

Assurance & compliance: Offen Fair Web Analytics vs TelemetryDeck
Assurance & compliance	Offen Fair Web Analytics	TelemetryDeck
Independent security / architecture audit	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.	Not found Vendor claims no IP storage and open SDK code for inspection; no public third-party no-logs or security audit report found in this pass.
ISO 27001	Not found No public ISO 27001 certification claim found on official site or docs.	Not found No public ISO 27001 certificate page located.
SOC 2 / SOC 3	Not found No public SOC 2/3 report found.	Not found No public SOC 2/3 report located.
GDPR / EU data protection	Vendor claimed EU authors; opt-in, data minimization (no IP/UA), visitor access/erasure, short default retention, Datensparsamkeit framing. Self-host means operator remains controller—confirm your legal basis and notice.	Vendor claimed EU (German) controller entity; privacy policy and Privacy FAQ document anonymization, non-storage of IPs for signals, and EU hosting regions. Vendor asserts analytics signals are not personal data—validate with counsel for your config.
US CLOUD Act exposure (indicative)	Partial EuropeanStack assessment: no known US parent; product not delivered as US-hosted vendor SaaS. Operator-chosen infrastructure (including optional Heroku/US cloud) can still create CLOUD Act paths for stored ciphertext/metadata. Not legal advice.	Partial German GmbH, no known US parent, EU regions named—but public hosters include AWS and Microsoft (US groups) and HubSpot (US) for CRM. Indicative medium exposure. Not legal advice.
Data processing agreement (B2B)	Not applicable No multi-tenant vendor analytics processing relationship documented; operator self-hosts and is typically controller. Custom development/support via offen.software is separate from a standard SaaS DPA.	Partial Public DPA at telemetrydeck.com/dpa (German AVV prevails). Document asserts TelemetryDeck is not Art. 28 processor/joint controller because signals are anonymized; TOMs on request. Not a classic processor AVV—legal review required.
EU AI Act	Not applicable Web analytics metrics product; not an AI system product.	Not applicable Product analytics / telemetry; not marketed as an AI system core offering.

Considerations & known limitations: Offen Fair Web Analytics vs TelemetryDeck
Considerations & known limitations	Offen Fair Web Analytics	TelemetryDeck
Opt-in undercounts absolute traffic	High Visitors who never consent generate no events. Growth and content KPIs will not match cookieless tools or GA-style default measurement—treat as design, not a misconfiguration.	Not listed
You own uptime, backups, and secrets	Medium No managed Offen cloud. Operators must run HTTPS/subdomain layout, set OFFEN_SECRET for stable sessions, configure SMTP for resets, and back up SQLite/SQL—plus avoid reverse proxies that log IPs if minimization is a goal.	Not listed
E2E crypto is vendor-claimed architecture	Medium Browser-side encryption and server inability to decrypt are core claims from project docs/README, not independently audited in public materials found. Security-sensitive orgs should review source or commission assessment.	Not listed
Hosting choice reintroduces cloud jurisdiction	Medium Self-host on US-group cloud or Heroku means CLOUD Act/subprocessor analysis shifts to your host even though Offen itself is Berlin-based OSS without a vendor SaaS region map.	Not listed
No public ISO/SOC or audit pack	Low Procurement checklists that require vendor ISO 27001/SOC 2 will stall; evidence is open source and design docs, not cert registry entries.	Not listed
Essential metrics only	Medium No heatmaps, session replay, advanced funnels, or product-analytics warehouse features. Wrong tool if the shortlist criterion is UX research depth rather than fair traffic statistics.	Not listed
US-group cloud and CRM subprocessors	Not listed	Medium Even with EU regions, AWS and Microsoft Azure are US-group providers; HubSpot processes customer CRM data in a US SaaS path. Buyers with strict no-US-cloud policies need written architecture confirmation or another vendor.
Anonymization / non-processor legal model	Not listed	Medium Public DPA states TelemetryDeck is neither processor nor joint controller for service data. Strong if true for your configuration; risky if custom metadata reintroduces personal data or if counsel disagrees with the anonymization analysis.
No public ISO/SOC or independent audit	Not listed	Medium No ISO 27001, SOC 2, or independent no-logs audit found publicly. Enterprise security questionnaires may need NDA materials or alternate assurance.
Free-tier ingest hard-stop	Not listed	Low Free plans discard events after the included monthly budget; overage data is not recoverable. Production apps on free tier need monitoring or a paid plan.
No self-hosted product	Not listed	Low Only client SDKs are open source. Organizations that must keep analytics databases on-prem cannot use TelemetryDeck as a full stack.

Fit

Offen Fair Web Analytics

Best fit when

Public-sector, media, NGO, or mission-driven sites that need visitor-visible transparency and strict opt-in
EU teams that must keep analytics off third-party trackers and can run a small always-on instance
Operators who want first-party subdomain cookies, CSP-aware embedding, and no IP/User-Agent collection
Organisations evaluating fair-processing design over maximum measurement coverage
Teams comfortable with SQLite or SQL self-host ops (binary or Docker) and publishing their own privacy notice

Poor fit when

Product or growth teams that require near-complete traffic measurement without consent friction
Needs for heatmaps, session replay, funnels, or ad-ecosystem attribution comparable to Hotjar/Mixpanel/GA
Buyers seeking a vendor-managed multi-tenant analytics cloud with SLAs and a signed vendor DPA as processor
Large enterprises that require public ISO 27001/SOC 2 or third-party security audit packs before shortlist

Consider instead when

When: You want privacy-oriented analytics with managed EU hosting and lower consent friction
Consider: Plausible Analytics or Pirsch Analytics
Typically optimised for simpler cookieless or low-friction models and hosted plans; less radical visitor Auditorium design than Offen.
When: You need EU hosted privacy analytics with operator support and less self-host burden
Consider: Friendly Analytics
European catalog peer oriented to hosted privacy analytics; compare consent model and feature depth to Offen’s opt-in + E2E approach.
When: You need deep product analytics, funnels, or session UX tooling rather than fair traffic metrics
Consider: Hotjar, Mixpanel, or a full GA4 stack (with legal review)
Different category: richer product/UX analytics, different jurisdiction and subprocessor profile.

TelemetryDeck

Best fit when

Mobile/desktop/web app teams that instrument events in code (Swift, Kotlin, Flutter, RN, JS) rather than only a website script
Product orgs prioritizing cookieless, double-hashed identifiers and leaner App Store privacy narratives versus ad-tech SDKs
Teams leaving Firebase Analytics or Mixpanel who accept a simpler event model for privacy-oriented defaults
European buyers wanting a German legal entity and EU-region hosting (Azure NL, AWS Frankfurt, Hetzner DE) with public privacy docs
Indie and small teams that want a free tier to start and volume-based paid plans as signal volume grows

Poor fit when

Organizations that must self-host the full analytics stack on their own infrastructure
Website-only traffic measurement without native app SDKs (Plausible/Pirsch are usually better fits)
Buyers that require public ISO 27001/SOC 2 certificates or a conventional Art. 28 processor DPA without the vendor’s anonymization legal model
Teams needing deep identity graphs, CRM-style user profiles, or full product-analytics marketing suites
Workloads that forbid US-group cloud providers entirely (AWS and Microsoft Azure are in the public host list)

Consider instead when

When: You only need privacy-friendly website analytics with a simple script
Consider: Plausible Analytics or Pirsch Analytics
Stronger web-first UX; weaker native multi-platform SDK story than TelemetryDeck
When: You must self-host analytics and own the database
Consider: Matomo (self-host) or Plausible Community Edition
TelemetryDeck is managed SaaS only
When: You need Firebase/Google ecosystem depth or free crash+remote-config adjacency
Consider: Firebase Analytics (accept Google jurisdiction and tracking model)
Different privacy and lock-in trade-offs
When: You need enterprise product analytics with rich identity and experimentation packaging
Consider: Mixpanel or Amplitude
Heavier privacy/cookie surface; more suite features

Open questions for due diligence

Offen Fair Web Analytics

Will your traffic and KPI model tolerate opt-in-only measurement after a pilot on a non-critical property?
Where will you host the instance (EU on-prem/VPS vs US-group cloud), and who holds OFFEN_SECRET and DB backups?
Do procurement rules require third-party audits or ISO/SOC that Offen does not publish?
Do you need a signed vendor DPA as processor, or is controller-only self-host acceptable to counsel?
Is subdomain + CSP (script-src/frame-src + unsafe-inline styles for the banner) feasible on your main site?

TelemetryDeck

Will counsel accept the public non-processor DPA/AVV model for your app’s identifier and metadata configuration?
Can TelemetryDeck provide TOMs, subprocessor list for the analytics plane, and any ISO/SOC or pen-test reports under NDA?
Which exact AWS/Azure services and accounts process customer organization data versus anonymized signals?
What contractual options exist to exclude or pin HubSpot and other US SaaS tools for account administration?
Current free-tier and paid plan event limits and retention windows for your expected volume (confirm on live plans UI)?