Commanders Act vs Offen Fair Web Analytics

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

Both listed as alternatives to: Google Analytics

Commanders Act

France· Web Analytics

Needs review

Shortlist when you need an EU-headquartered enterprise stack combining server-side tag management, consent, real-time CDP activation, and independent media attribution (Adloop). Skip when you only need lightweight privacy analytics or open-source self-hosting—consider etracker or fusedeck for narrower EU measurement/tagging scopes, or Matomo-class tools for self-host analytics.

EU-operated (FR)Server-side TMSReal-time CDPIntegrated CMPAdloop attributionSaaS only

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.

Commanders Act vs Offen Fair Web Analytics: Snapshot
Feature	Commanders Act	Offen Fair Web Analytics
Country of origin	France	Germany
Category	Web Analytics	Web Analytics
Open source	No	Yes
Self-hosted	No	Yes
Headquarters	France	Germany
Legal entity	Fjord Technologies SAS (trading name Commanders Act), SIREN 527 730 782, Paris	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	Not listed	Germany (indicative from Berlin imprint)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Low
Hosting / residency	Vendor: EU/France data centers for platform hosting; privacy policy: site data stored in EU. Public DNS: app/platform behind Cloudflare CDN. Hosting provider certs (ISO 27001, SOC 1/2, etc.) claimed on Security product sheet. Full customer-data subprocessor list not published on marketing site.	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	French PlatformX MarTech suite from Fjord Technologies: enterprise server-side tag management, integrated consent, real-time CDP, and Adloop media attribution for multi-channel marketing teams.	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	gdpr martech tag-management cdp server-side-tracking consent-management france first-party-data	gdpr analytics open-source privacy self-hosted opt-in e2e-encryption

At a glance: Commanders Act vs Offen Fair Web Analytics
At a glance	Commanders Act	Offen Fair Web Analytics
HQ	Paris, France (Fjord Technologies SAS)	Not listed
SIREN	527 730 782	Not listed
Founded	2010 (as TagCommander / Fjord Technologies)	Not listed
Deployment	Managed SaaS (not self-hosted)	Not listed
Core suite	TMS + CMP + CDP + Adloop	Not listed
Commercial model	Demo / enterprise quote (no public list price)	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: Commanders Act vs Offen Fair Web Analytics
Key capabilities	Commanders Act	Offen Fair Web Analytics
EU-operated (FR)	Yes	Yes
Server-side TMS	Yes	Not listed
Real-time CDP	Yes	Not listed
Integrated CMP	Yes	Not listed
Adloop attribution	Yes	Not listed
SaaS only	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

Commanders Act

Enterprise Tag Manager with server-side destinations and CAPIs
Collect first-party and omnichannel events, transform/enrich without code, and deliver to 1,200+ destinations including 100+ server-side paths and major CAPIs (Google, Meta, Amazon, TikTok, Snapchat per vendor). GTM-ready server-side integration supports hybrid Google Tag Manager workflows.
Integrated consent and privacy governance tooling
Native CMP/consent features (TrustCommander lineage) with Google Consent Mode support and Google CMP partner listing. Privacy monitoring, data-quality dashboards, filters before partner delivery, and cookie-related scanners help marketing ops control what leaves the property.
Real-time CDP: identity resolution, segments, activation
Unify profiles across sources (including CRM enrichment), build no-code audiences with many filter criteria, push dynamic segment updates into ad and personalization destinations, and support cross-device experience consistency under consent rules.
Adloop media optimization and data-driven attribution
After the 2023 Adloop acquisition, centralize campaign data via API connectors, run behaviour-based attribution as an independent measurement layer versus ad-platform KPIs, set spend/anomaly alerts, and use AI-assisted ad-level recommendations.
Operational QA for tagging teams
No-code QA tooling (live event inspector, debug mode), continuous data-quality monitoring, and role/IP-restricted platform access claims reduce reliance on pure developer debugging when tags and server-side pipelines change.

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: Commanders Act vs Offen Fair Web Analytics
Assurance & compliance	Commanders Act	Offen Fair Web Analytics
Independent security / no-logs audit	Not applicable Not a no-logs VPN/analytics product; marketing data platform processes customer event/profile data by design.	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.
Independent security / pentest program	Vendor claimed Security product sheet claims external pentests (black/grey box) every six months and customer audit rights; no public audit PDF reviewed.	Not listed
ISO 27001	Partial Security sheet attributes ISO 27001 (and related) compliance to the hosting provider in France; not verified as Commanders Act's own current certificate.	Not found No public ISO 27001 certification claim found on official site or docs.
SOC 2 / SOC 3	Partial Security sheet states hosting provider complies with SOC Type 1 and 2; not verified as vendor-owned SOC 2 report.	Not found No public SOC 2/3 report found.
GDPR / EU data protection	Vendor claimed French controller/processor entity; public privacy policy, named DPO, EU storage claim for site data, integrated consent tooling. Customer DPA terms not fully public on marketing pages.	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 EU entity / no known US parent, but Cloudflare CDN on public app/platform hostnames and incomplete public subprocessor list for customer data path. 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)	Unknown Website privacy policy covers visitor/site processing; standard B2B DPA / Art. 28 package not located as a public self-serve download—request in procurement.	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 Includes AI-assisted ad recommendations; not assessed here as a high-risk AI system product category.	Not applicable Web analytics metrics product; not an AI system product.

Considerations & known limitations: Commanders Act vs Offen Fair Web Analytics
Considerations & known limitations	Commanders Act	Offen Fair Web Analytics
Limited public subprocessor inventory	Medium Marketing site does not publish a clear list of subprocessors for customer event/CDP data. Cloudflare is observable on public hostnames; backend host is described generically as a French data center. Request written subprocessors, regions, and SCCs before relying on 'EU-only' narratives.	Not listed
ISO/SOC claims tied to hosting provider	Medium Security sheet language credits the data-center provider for ISO 27001 and SOC Type 1/2. Do not treat footer logos as proof of Commanders Act's own certifications without certificate IDs.	Not listed
Enterprise SaaS scope and switching cost	Medium PlatformX spans TMS, CMP, CDP, and media optimization. Implementation (server-side migration, consent redesign, CAPI mapping) is non-trivial; not a drop-in free GTM replacement for all teams.	Not listed
No self-host option	Low Fully managed SaaS only. Organizations with hard on-prem or open-source requirements need different tools.	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

Commanders Act

Best fit when

Marketing ops teams replacing or complementing GTM with governed server-side destinations and CAPIs
Enterprises that want tag management, consent, CDP segments, and activation under one French SaaS contract
Performance teams needing independent multi-channel attribution and campaign data hub after Adloop
Organizations prioritizing an EU legal entity and EU data-center marketing claims for MarTech collection tooling
Teams that need no-code QA, data-quality monitoring, and consent-aware partner delivery controls

Poor fit when

Solo sites or SMBs that only need free/client-side GTM or lightweight privacy page analytics
Buyers requiring open-source or fully self-hosted tag/CDP infrastructure
Procurement that must prove vendor-owned ISO 27001/SOC 2 from public certificate registries before RFP (provider-level claims need clarification)
Use cases limited to pure product analytics without marketing destination/CAPI complexity

Consider instead when

When: You mainly need EU web analytics with lighter tag/consent tooling, not a full CDP + media stack
Consider: etracker
German analytics + tag/consent oriented stack; smaller surface than PlatformX
When: You want Swiss cookieless analytics plus server-side tagging/activation without a French enterprise CDP suite
Consider: fusedeck
Narrower product; different jurisdiction (CH)
When: You need free client-side tagging and Google-native defaults, and can accept US hyperscaler jurisdiction
Consider: Google Tag Manager (and Google marketing stack)
Often retained in hybrid with Commanders Act server-side
When: Self-host open analytics is a hard requirement
Consider: Matomo (self-host or EU Matomo hosting peers such as Friendly Analytics)
Not a CDP/CAPI replacement

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

Commanders Act

Will Fjord Technologies provide a current Art. 28 DPA, subprocessor list, and data-flow diagram for PlatformX customer event data?
Which legal entity and cloud region process production customer data today, and are backups/DR in the same jurisdiction?
Does Commanders Act hold its own ISO 27001 or SOC 2 (certificate number/date), or only rely on hosting-provider attestations?
What is the minimum commercial package if the buyer only needs TMS + CMP versus full CDP + Adloop?
How are US ad-platform CAPIs and optional Google/Meta connections handled for transfer impact assessments?

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?