Offen Fair Web Analytics vs Wide Angle Analytics

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

Both listed as alternatives to: Fathom Analytics, Google Analytics, Matomo

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

Wide Angle Analytics

Germany· Web Analytics

Needs review

Do not shortlist Wide Angle for new multi-year analytics: the vendor is winding the product down by end of August 2026. Existing customers should migrate using the promised data snapshot. For new EU privacy-analytics shortlists prefer Plausible, Pirsch, Simple Analytics, or Piwik PRO; keep Matomo-class stacks when self-host control is mandatory.

Cookieless by defaultGerman GmbH (Berlin)OVHcloud FR/DE hostingSaaS only (no self-host)EOL Aug 2026

View listing Visit Website

Highlighted rows differ between the two products.

Offen Fair Web Analytics vs Wide Angle Analytics: Snapshot
Feature	Offen Fair Web Analytics	Wide Angle Analytics
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	Input Objects GmbH, Scharnhorststraße 24, 10115 Berlin, Germany
Governing law	Germany (indicative from Berlin imprint)	Not listed
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).	Visitor analytics: OVHcloud limited to FR/DE (vendor). Account path: Paddle (payments), Brevo email/automation, Infomaniak; older vendor post notes Brevo/Sendinblue encrypted DR involving AWS/GCP. No known US corporate parent.
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 cookieless-by-default web analytics SaaS (Input Objects GmbH, OVHcloud FR/DE). Product announced for discontinuation end of August 2026—prefer living EU peers for new deployments.
Tags	analytics privacy gdpr open-source self-hosted opt-in e2e-encryption	analytics privacy gdpr web-analytics cookieless saas germany google-analytics-alternative end-of-life

At a glance: Offen Fair Web Analytics vs Wide Angle Analytics
At a glance	Offen Fair Web Analytics	Wide Angle Analytics
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	Berlin, Germany (Input Objects GmbH)
Product launch	Not listed	November 2021
Hosting (visitor path)	Not listed	OVHcloud France & Germany (vendor-stated)
Open source	Not listed	No
Self-host	Not listed	No
Status	Not listed	Discontinuing end of August 2026
Commercial model	Not listed	Event/site SaaS tiers + 14-day trial (see official pricing)

Key capabilities: Offen Fair Web Analytics vs Wide Angle Analytics
Key capabilities	Offen Fair Web Analytics	Wide Angle Analytics
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	Not listed
Cookieless by default	Not listed	Yes
German GmbH (Berlin)	Not listed	Yes
OVHcloud FR/DE hosting	Not listed	Yes
SaaS only (no self-host)	Not listed	Yes
EOL Aug 2026	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.

Wide Angle Analytics

Cookieless request-based sessions with daily rotating salt
Default mode hashes site + IP + User-Agent with a non-persisted daily salt (SHA-256). Same-day uniques without cookies or long-lived IDs; past sessions cannot be re-linked after salt rotation. Optional 24h cookie or canvas fingerprinting change the consent analysis.
Optional tracking modes for SPA and consent-gated detail
Enable HTTP(S)-only 24h cookies, client fingerprinting, or service-issued IDs for SPA reliability. Fingerprinting is off by default and may require consent—controllers must re-assess before enabling.
Marketer dashboards, custom events, and multi-site teams
Real-time charts for sources, pages, devices, UTM campaigns, goals, custom actions, and e-commerce revenue attribution. Higher tiers add multi-user sharing, permissions, and many sites without SQL.
CMS one-click installs and lightweight script embed
Plugins/integrations for WordPress, Squarespace, Wix, Ghost, Webflow, and common JS stacks; custom sites add a script tag. Built for marketers rather than BI engineers.
OVHcloud EU regions (FR/DE) for visitor analytics path
Vendor states product hosting is limited to OVHcloud France and Germany with no end-user analytics transfer outside EU/EEA and no sale of visitor data. Account billing/email use separate subprocessors (see Trust).

Assurance & compliance: Offen Fair Web Analytics vs Wide Angle Analytics
Assurance & compliance	Offen Fair Web Analytics	Wide Angle Analytics
Independent security / architecture audit	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.	Not found No public independent pen-test or no-logs audit PDF found on site materials reviewed.
ISO 27001	Not found No public ISO 27001 certification claim found on official site or docs.	Not found No public ISO 27001 certificate page found.
SOC 2 / SOC 3	Not found No public SOC 2/3 report found.	Not found No public SOC 2/3 report found.
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 German controller/processor entity; cookieless-default design; DPO named (DPO CONSULTING). Not legal advice.
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 EU GmbH, no known US parent, OVH FR/DE visitor hosting; offset by Paddle and Brevo-related infrastructure (incl. encrypted AWS/GCP DR per vendor blog). Assessment row—not vendor marketing.
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.	Vendor claimed Vendor blog/compliance materials state a signed DPA is offered; confirm current template with vendor.
EU AI Act	Not applicable Web analytics metrics product; not an AI system product.	Not applicable Web analytics product, not an AI system under typical AI Act product framing.

Considerations & known limitations: Offen Fair Web Analytics vs Wide Angle Analytics
Considerations & known limitations	Offen Fair Web Analytics	Wide Angle Analytics
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
Product end-of-life (August 2026)	Not listed	High Vendor announced discontinuation; service runs until end of August 2026 with pro-rata refunds and a vendor-prepared snapshot—not a self-service export. New deployments risk forced migration within weeks.
No self-host continuity path	Not listed	High SaaS-only design means the product cannot be retained on your infrastructure after shutdown.
Account subprocessors beyond OVH	Not listed	Medium Paddle, Brevo, Infomaniak (and historical Brevo DR via US-group clouds) affect customer-account and support data paths even if visitor analytics stay on OVH EU.
Optional fingerprinting/cookies	Not listed	Medium Non-default modes can reintroduce consent obligations; misconfiguration is a controller risk.
No public ISO/SOC/independent audit	Not listed	Medium Assurance rests on design docs, DPA, and vendor claims unless private reports are provided under NDA.

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.

Wide Angle Analytics

Best fit when

Existing Wide Angle customers completing migration before the announced August 2026 shutdown
Historical evaluation of cookieless, marketer-oriented EU SaaS analytics design (daily-salted sessions, OVH FR/DE)
Teams that needed multi-site CMS installs and shared reports without running Matomo themselves (while service remained live)
Controllers comparing default cookieless vs optional fingerprint/cookie modes on a single product

Poor fit when

Any new production deployment expected to outlive August 2026
Buyers requiring open-source self-host continuity (use Plausible CE, Matomo, or similar)
Product analytics, session replay, heatmaps, or ad-tech attribution platforms
Orgs that need public ISO 27001 / SOC 2 certificates without requesting private packs
Free forever hosted analytics

Consider instead when

When: You need a living cookieless EU SaaS analytics product
Consider: Plausible Analytics, Pirsch Analytics, or Simple Analytics
All remain active EU-oriented peers in this directory category.
When: You need self-host or deep plugin/on-prem control
Consider: Matomo (self-host or hosted peers) or Piwik PRO
Wide Angle never offered self-host and is shutting down.
When: You accept US ad-stack analytics for free depth
Consider: Google Analytics (GA4)
Different jurisdiction, cookie/consent model, and product surface—not a like-for-like privacy swap.

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?

Wide Angle Analytics

Exact cutover date/time and timezone for service stop after August 2026?
When and in what open format is each tenant's data snapshot delivered?
Current signed subprocessor list and SCCs under the active DPA (vs 2022 blog / iubenda summary)?
Any residual access window or deletion certificate after EOL?
Are private security assessments available under NDA before remaining term ends?