fusedeck® vs Offen Fair Web Analytics

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

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

fusedeck®

Switzerland· Web Analytics

Needs review

Shortlist fusedeck when you need Swiss-operated cookieless-capable web analytics plus tag management and on-site activation (scoring, modals, A/B, server-side ad exports) in one SaaS. Skip when you only need lightweight pageviews (consider Plausible or Simple Analytics) or must self-host open-source analytics (consider Matomo-class tools).

Cookieless + cookie modesServer-side tag managerOn-site activationEU storage (claimed)Swiss HQSaaS (Shared/Owned)

View listing Visit Website

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

Highlighted rows differ between the two products.

fusedeck® vs Offen Fair Web Analytics: Snapshot
Feature	fusedeck®	Offen Fair Web Analytics
Country of origin	Switzerland	Germany
Category	Web Analytics	Web Analytics
Open source	No	Yes
Self-hosted	No	Yes
Headquarters	Switzerland	Germany
Legal entity	Capture Media AG (imprint); privacy policy controller listed as cptr AG — same Zurich address	Public legal notice lists Frederik Ring, Berlin (offen.software); product authors Frederik Ring and Hendrik Niefeld—no separate GmbH name verified on imprint
Governing law	Swiss data protection (FADP) for the operator; German GTC apply to cptr Germany GmbH contracts; confirm order form	Germany (indicative from Berlin imprint)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Low
Hosting / residency	Main storage claimed in the EU (encrypted). Public subprocessors: AWS EMEA SARL (compute), ClickHouse, Inc. (US) with data on AWS Ireland, Aiven Oy (Finland) DBaaS on AWS, VSHN AG (CH) for Kubernetes on AWS, cptr Hungary Kft. (development). Optional customer exports to Meta/LinkedIn/TikTok/Google are separate transfer paths.	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).
Summary	Cookieless analytics, server-side tagging, and on-site activation from Switzerland—Track, Analyse, and Activate workflows for marketing teams leaving cookie-only stacks.	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.
Tags	analytics privacy cookieless server-side-tracking tag-manager activation saas	analytics privacy open-source self-hosted opt-in gdpr e2e-encryption

At a glance: fusedeck® vs Offen Fair Web Analytics
At a glance	fusedeck®	Offen Fair Web Analytics
HQ	Zurich, Switzerland	Not listed
Legal entity (public)	Capture Media AG (imprint); cptr AG (privacy controller)	Not listed
Product type	Cookieless analytics + activation SaaS	Not listed
Hosting (public)	EU storage claimed; AWS + ClickHouse on AWS Ireland	Not listed
Open source	No	Not listed
Self-hosted	No (Shared / Owned SaaS stacks)	Not listed
Commercial model	Paid monthly SaaS; Shared vs Owned stacks	Not listed
HQ / authors	Not listed	Berlin, Germany (Frederik Ring & Hendrik Niefeld)
License	Not listed	Apache-2.0 (code/docs); logo CC-BY-NC-ND-4.0
Delivery	Not listed	Self-host only (binary, Docker, community deploys)
Consent model	Not listed	Opt-in only; first-party cookies
Default retention	Not listed	6 months (configurable shorter)
Funding note	Not listed	NLnet NGI support (project-stated)

Key capabilities: fusedeck® vs Offen Fair Web Analytics
Key capabilities	fusedeck®	Offen Fair Web Analytics
Cookieless + cookie modes	Yes	Not listed
Server-side tag manager	Yes	Not listed
On-site activation	Yes	Not listed
EU storage (claimed)	Yes	Not listed
Swiss HQ	Yes	Not listed
SaaS (Shared/Owned)	Yes	Not listed
Opt-in only	Not listed	Yes
Browser E2E encryption	Not listed	Yes
Self-hosted	Not listed	Yes
Apache-2.0	Not listed	Yes
Visitor data access	Not listed	Yes
Berlin-based project	Not listed	Yes

fusedeck®

Configurable cookieless and cookie tracking modes
Full cookie tracking, cookieless user tracking (calculated ID, no device storage), and cookieless session tracking (session-level only, no cross-session recognition) so teams can match consent posture and geo rules. Limit: legal fit of each mode still depends on your counsel and implementation—not a blanket no-consent guarantee for every event design.
Server-side tag manager and event control
Define events, triggers, and selectors; gate which external tags and third parties receive data based on consent and configuration. Reduces reliance on brittle client-only pixels. Limit: marketers still need a clear data and tag taxonomy or complexity moves into fusedeck workspaces.
Reports, dashboards, and API exports
Ready-made reports (behaviour, campaigns, inbound, tag manager, visitors), report builder, dashboards, share links, raw or API export, and optional Looker Studio connectivity for deeper analysis without rebuilding every KPI in a spreadsheet.
On-site activation: scoring, modals, A/B tests
Score sessions, trigger call-to-action modals, run A/B tests, and inject dynamic content so analytics can drive conversion work inside the same product—not only offline reporting.
Server-side transfers to ad and CRM systems
Export audiences and conversion signals server-side toward platforms such as Meta, LinkedIn, and TikTok, plus API hooks to CRM or other systems, while keeping more tag logic off the browser. Limit: those destinations introduce their own processors and transfer assessments.
Shared Stack vs Owned Stack infrastructure
Shared multi-tenant cloud for standard deployments; Owned Stack with vendor-described physically separated infrastructure, white-label domain option, and higher scale for stricter security or traffic needs—still SaaS, not self-hosted open source.

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.

Assurance & compliance: fusedeck® vs Offen Fair Web Analytics
Assurance & compliance	fusedeck®	Offen Fair Web Analytics
Independent security / no-logs audit	Not found TOMs and legal opinions on cookieless tracking exist; no independent third-party security audit PDF found on primary trust pages.	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.
ISO 27001	Not found No public ISO 27001 certificate located on imprint, privacy, TOM, or subprocessor pages.	Not found No public ISO 27001 certification claim found on official site or docs.
SOC 2 / SOC 3	Not found No SOC 2/3 report referenced on primary trust pages.	Not found No public SOC 2/3 report found.
GDPR / EU data protection	Vendor claimed Swiss operator; product data-privacy page claims GDPR/ePrivacy-configurable setups; privacy policy cites FADP and GDPR legal bases. Confirm DPA and configuration for your properties.	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.
US CLOUD Act exposure (indicative)	Partial Swiss entity / no known US parent, but public subprocessors include AWS and ClickHouse, Inc. (US) with EU residency claims. Indicative medium exposure—not a clean bill of health and not legal advice.	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.
Data processing agreement (B2B)	Vendor claimed German GTC state processing under an Auftragsverarbeitung with customer as controller and cptr as processor. Obtain the signed DPA + annex for your contracting entity.	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.
EU AI Act	Not applicable Web analytics / marketing activation product; not positioned as an AI system under public materials.	Not applicable Web analytics metrics product; not an AI system product.

Considerations & known limitations: fusedeck® vs Offen Fair Web Analytics
Considerations & known limitations	fusedeck®	Offen Fair Web Analytics
AWS and US-domiciled database subprocessor	Medium Despite Swiss HQ and EU storage claims, compute and DB path use AWS and ClickHouse, Inc. (US company, data on AWS Ireland). Policies that ban US-group cloud providers entirely may fail even if data residency is EU.	Not listed
Capture Media AG vs cptr AG naming	Low Imprint still lists Capture Media AG while the privacy policy names cptr AG as controller. Confirm the exact contracting party, invoice entity, and DPA counterparty on the order form.	Not listed
No public independent security audit or ISO/SOC	Medium TOMs are published, but we found no independent audit report or ISO 27001 / SOC 2 certificate. Security questionnaires and NDA materials may still be required for enterprise purchase.	Not listed
Cookieless modes are not automatic legal clearance	Medium Cookieless session tracking is positioned for compliance without consent, but full cookie and cookieless user modes, identity features, and ad-platform exports can reintroduce consent and transfer questions. Legal review of your event design remains mandatory.	Not listed
No classical self-host option	Low Owned Stack is dedicated vendor-operated cloud, not buyer-operated self-hosting. Air-gapped or fully on-prem mandates need another product.	Not listed
Opt-in undercounts absolute traffic	Not listed	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.
You own uptime, backups, and secrets	Not listed	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.
E2E crypto is vendor-claimed architecture	Not listed	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.
Hosting choice reintroduces cloud jurisdiction	Not listed	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.
No public ISO/SOC or audit pack	Not listed	Low Procurement checklists that require vendor ISO 27001/SOC 2 will stall; evidence is open source and design docs, not cert registry entries.
Essential metrics only	Not listed	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.

Fit

fusedeck®

Best fit when

Marketing ops teams that want Track + Analyse + Activate in one stack, not only traffic charts
Organisations replacing or supplementing GA4 with cookieless-capable, consent-flexible collection modes
Teams that need server-side control over which third-party tags and ad platforms receive data
Buyers who want Swiss contracting and public EU hosting claims, and can accept AWS-based SaaS
Sites that benefit from scoring, modals, A/B tests, or server-side Meta/LinkedIn/TikTok transfers

Poor fit when

Teams that only need simple privacy-first pageview analytics without activation tooling
Requirements for open-source or classical self-hosted analytics under buyer-operated infrastructure
Procurement policies that forbid US-group cloud subprocessors (AWS / US-domiciled database vendors) entirely
Buyers seeking a free production tier or purely DIY setup without commercial SaaS onboarding

Consider instead when

When: You only need lightweight, privacy-oriented traffic metrics
Consider: Plausible Analytics, Simple Analytics, or Friendly Analytics
Smaller surface area; little or no activation / ad-export stack
When: You must self-host or prefer open-source analytics under your operators
Consider: Matomo-class deployments or Piwik PRO where self-host/on-prem options fit
fusedeck is SaaS Shared/Owned stack, not a public self-host product
When: You need global free-tier depth and Google ecosystem defaults
Consider: Google Analytics
Different jurisdiction and subprocessor story; still the default for many teams
When: You want a German enterprise analytics brand with strong packaging options
Consider: etracker or Piwik PRO
Compare residency, consent tooling, and activation depth side by side

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.

Open questions for due diligence

fusedeck®

Which legal entity will appear on the contract and DPA for our region (Capture Media AG, cptr AG, cptr Germany GmbH, or another affiliate)?
Can the vendor provide the current subprocessor annex, SCCs if any, and confirmation of all AWS regions used for our data?
Is an independent security audit, pen-test summary, or ISO/SOC roadmap available under NDA?
Which tracking mode and event schema does fusedeck recommend for our CMP and target markets, and what remains after ad-blocker impact?
What are Shared vs Owned stack operational differences (isolation, custom domain, support SLAs) for our traffic volume?

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?