Offen Fair Web Analytics vs Pirsch Analytics

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

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

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

Pirsch Analytics

Germany· Web Analytics

Needs review

Shortlist Pirsch when you want German-operated, cookie-free web analytics with funnels/events, agency white-label, and a public DPA—hosted on Hetzner per vendor docs. Skip when you need free full-product self-host, session replay/heatmaps, or a stack with zero US-group subprocessors; consider Plausible or Simple Analytics instead.

Cookie-free hashingOpen-source core (AGPL)Hetzner DE hosting (claimed)Server-side trackingAgency white-labelPublic DPA/AVV

View listing Visit Website

Highlighted rows differ between the two products.

Offen Fair Web Analytics vs Pirsch Analytics: Snapshot
Feature	Offen Fair Web Analytics	Pirsch Analytics
Country of origin	Germany	Germany
Category	Web Analytics	Web Analytics
Open source	Yes	Yes
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	Emvi Software GmbH (Nickelstraße 1b, 33378 Rheda-Wiedenbrück; HRB 11575, AG Gütersloh)
Governing law	Germany (indicative from Berlin imprint)	Germany / EU GDPR
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).	Analytics: Hetzner Online GmbH, Germany (vendor claims Nuremberg/Falkenstein). Account/ops subprocessors named in privacy policy include AWS SES (Amazon Web Services EMEA), Google Workspace (Google Cloud EMEA), Stripe, Inc. (US), Intuition Machines, Inc. (US CAPTCHA), and Datev eG (DE).
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.	Cookie-free web analytics from Emvi Software GmbH in Germany: hash-based visitor IDs, open-source core, Hetzner-hosted SaaS with funnels, events, and agency white-label.
Tags	analytics open-source privacy gdpr self-hosted opt-in e2e-encryption	analytics open-source privacy gdpr web-analytics cookie-free saas germany server-side-tracking

At a glance: Offen Fair Web Analytics vs Pirsch Analytics
At a glance	Offen Fair Web Analytics	Pirsch 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	Rheda-Wiedenbrück, Germany
Legal entity	Not listed	Emvi Software GmbH
Category	Not listed	Web analytics (SaaS)
Open source	Not listed	Core library AGPL-3.0; full SaaS commercial
Self-host	Not listed	Enterprise on-prem option; not free CE
Commercial model	Not listed	Usage-based (monthly page views); trial available
Primary hosting (claimed)	Not listed	Hetzner Germany (Nuremberg/Falkenstein)

Key capabilities: Offen Fair Web Analytics vs Pirsch Analytics
Key capabilities	Offen Fair Web Analytics	Pirsch 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
Cookie-free hashing	Not listed	Yes
Open-source core (AGPL)	Not listed	Yes
Hetzner DE hosting (claimed)	Not listed	Yes
Server-side tracking	Not listed	Yes
Agency white-label	Not listed	Yes
Public DPA/AVV	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.

Pirsch Analytics

Cookie-free 24-hour visitor hashing
Recognizes visitors without cookies by hashing IP, User-Agent, date, and a per-site salt into a short ID. The vendor states IPs are not stored and cross-site linkage is blocked by the salt; sessions expire after 24 hours so long-term profiles are not built. Best for sites that want aggregate traffic metrics without a dedicated analytics cookie banner—confirm ePrivacy/TTDSG fit with counsel.
Server-side and script integrations
Instrument via JS snippet, CMS plugins (e.g. WordPress, Shopify, Webflow, Framer), or backend SDKs/API (Go library and other stacks). Server-side collection improves resilience when ad blockers strip client scripts. Tradeoff: backend integration costs more engineering time than a single script tag.
Funnels, events, goals, and tag segmentation
Goes past pageviews with custom events, conversion goals, multi-step funnels, session path exploration, outbound/download/404 tracking, and tags for A/B tests or channel segmentation. Webhooks and email reports push insights into existing tools. Some advanced metrics (e.g. custom event metrics, e-commerce revenue tracking) sit on higher commercial tiers—verify the live feature matrix.
Agency white-label and shared dashboards
Custom domains, themes, logos, and broader white-label options let agencies present analytics under their own brand. Public dashboards and unique access links support clients without full account sprawl; roles/teams scale collaboration. Strong fit for multi-client portfolios; less relevant for a single personal blog.
Migration imports, API, and unlimited retention (stated)
Import historical data from Google Analytics, Plausible, or Fathom; export CSV; use the REST API and SDKs for custom pipelines. Pricing docs state unlimited data retention across Standard, Plus, and Enterprise. Limits are usage-based on monthly page views (events and a share of session extensions count)—plan for growth, not perpetual free volume.

Assurance & compliance: Offen Fair Web Analytics vs Pirsch Analytics
Assurance & compliance	Offen Fair Web Analytics	Pirsch Analytics
Independent security / architecture audit	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.	Not found Open-source core allows code review; no public third-party audit PDF located in this research pass.
ISO 27001	Not found No public ISO 27001 certification claim found on official site or docs.	Not found No ISO 27001 certificate or registry entry found on official trust pages reviewed.
SOC 2 / SOC 3	Not found No public SOC 2/3 report found.	Not found No public SOC 2/3 report referenced on official pages reviewed.
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 Emvi Software GmbH; cookie-free hashing design; public DPA; German Hetzner hosting claims. Vendor also cites CCPA/PECR/Schrems II—treat as claims, confirm with counsel.
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 entity / no known US parent and Hetzner DE analytics hosting, but privacy policy names AWS SES, Google Workspace, Stripe, and Intuition Machines (US-group services) for email/CAPTCHA/payments. 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.	Vendor claimed Downloadable English DPA and German AVV PDFs linked from docs.pirsch.io/privacy.
EU AI Act	Not applicable Web analytics metrics product; not an AI system product.	Not applicable Classical web analytics product; not marketed as an AI system.

Considerations & known limitations: Offen Fair Web Analytics vs Pirsch Analytics
Considerations & known limitations	Offen Fair Web Analytics	Pirsch 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.	Medium Procurement teams that require ISO 27001 or SOC 2 evidence will need vendor questionnaires or NDA materials; public pages did not show those certs.
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 account/ops subprocessors	Not listed	Medium Even with German analytics hosting claims, customer email, CAPTCHA, and payments involve AWS, Google, Stripe, and Intuition Machines. Sovereign or “no US cloud” policies need explicit exception handling or Enterprise architecture review.
Open-source core ≠ free full self-host	Not listed	Low Teams assuming AGPL means free on-prem of the entire product may be surprised; full on-prem is positioned as Enterprise.
Fingerprinting still needs legal fit review	Not listed	Low Cookie-free hashing is not automatically lawful everywhere without information/consent analysis. Banner removal should be validated for your jurisdiction and tag stack.
Page-view usage limits	Not listed	Low Plans are metered on monthly page views (with events and partial session extensions counting). Hitting the cap can restrict dashboard access until upgrade or cycle reset—model traffic before cutover.

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.

Pirsch Analytics

Best fit when

EU sites replacing Google Analytics that need pageviews, campaigns, events, and funnels without analytics cookies
Agencies needing multi-site dashboards, client access links, and white-label branding
Teams that can instrument server-side or proxy scripts for better ad-blocker resilience
Buyers who want a German GmbH, downloadable DPA, and Hetzner-Germany residency claims for analytics data
Orgs evaluating Enterprise SAML, raw data access, or on-prem/managed private deployment

Poor fit when

Teams that require a free, full-product self-hosted community edition (core library ≠ full SaaS)
Product or UX research needing session replay, heatmaps, or persistent cross-site user identity
Procurement policies that forbid any US-group subprocessor (email CAPTCHA/billing still touch AWS/Google/Stripe/Intuition Machines)
Heavy product-analytics / multi-product identity graphs (closer to Amplitude/Mixpanel class tools)

Consider instead when

When: You need a free full-stack self-hosted analytics product with AGPL community edition
Consider: Plausible Analytics (CE) or other open full products in your shortlist
Pirsch open-sources the tracking core; on-prem of the full product is Enterprise-scoped.
When: You want the simplest possible privacy-first metrics with a Dutch vendor
Consider: Simple Analytics
Fewer advanced funnel/white-label features; different packaging tradeoffs.
When: You need heatmaps or session replay more than classical web analytics
Consider: Hotjar, Microsoft Clarity, or EU UX-analytics peers
Expect heavier consent and data-minimization review.
When: You must stay inside Google’s advertising and BigQuery measurement ecosystem
Consider: Google Analytics / Google Tag Manager stack
Opposite privacy and transfer posture—only if legal review accepts it.

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?

Pirsch Analytics

Can Enterprise on-prem exclude AWS SES / Google Workspace / Stripe / CAPTCHA US-group dependencies for the customer’s deployment?
Is any ISO 27001, SOC 2, or independent penetration-test summary available under NDA?
Exact data centers, backup locations, and encryption-key custody for multi-tenant SaaS—beyond marketing Hetzner claims?
Which feature flags on Standard vs Plus vs Enterprise apply to funnels, A/B tags, e-commerce metrics, and white-label depth at contract time?