Offen Fair Web Analytics vs SEAL Metrics

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

Both listed as alternatives to: Google Analytics, 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

SEAL Metrics

Spain· Web Analytics

Needs review

Shortlist when European eCommerce or hospitality teams need cookieless full-traffic capture and last-click ROAS they can align with finance—without GA4 Consent Mode as the measurement backbone. Skip when you need self-host or open source, session replay and product analytics depth, or a certified ISO/SOC package today—consider Plausible, Simple Analytics, Pirsch, or Matomo-based hosts instead.

Cookieless first-party pixelEU-hosted (Dublin)Revenue / ROAS focusReal-time dashboardsDPA includedSaaS only

View listing Visit Website

Highlighted rows differ between the two products.

Offen Fair Web Analytics vs SEAL Metrics: Snapshot
Feature	Offen Fair Web Analytics	SEAL Metrics
Country of origin	Germany	Spain
Category	Web Analytics	Web Analytics
Open source	Yes	No
Self-hosted	Yes	No
Headquarters	Germany	Spain
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	SealMetrics (Spain; exact registered company name not found on public imprint)
Governing law	Germany (indicative from Berlin imprint)	Spain (Terms of Service; courts of Barcelona)
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).	Customer analytics app, DB, and backups: Dublin, Ireland (EU data center, provider not named publicly). Subprocessor: Cloudflare for CDN/DDoS on encrypted transit at EU edge locations; vendor states no analytics data at rest on Cloudflare and no US cloud storage of customer analytics.
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.	Spanish cookieless web analytics for European eCommerce: first-party capture, Dublin EU storage, last-click revenue and ROAS without consent-dependent tags.
Tags	analytics privacy gdpr open-source self-hosted opt-in e2e-encryption	analytics privacy gdpr cookieless ecommerce attribution saas

At a glance: Offen Fair Web Analytics vs SEAL Metrics
At a glance	Offen Fair Web Analytics	SEAL Metrics
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	Spain (Spanish law; Barcelona courts per Terms)
Founded	Not listed	2020 (vendor how-it-works page)
Hosting	Not listed	Dublin, Ireland — EU data center; Cloudflare edge transit
Model	Not listed	SaaS; event-volume plans; free agentic tier + trial
Open source	Not listed	No
Self-host	Not listed	No

Key capabilities: Offen Fair Web Analytics vs SEAL Metrics
Key capabilities	Offen Fair Web Analytics	SEAL Metrics
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 first-party pixel	Not listed	Yes
EU-hosted (Dublin)	Not listed	Yes
Revenue / ROAS focus	Not listed	Yes
Real-time dashboards	Not listed	Yes
DPA included	Not listed	Yes
SaaS only	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.

SEAL Metrics

846-byte first-party cookieless pixel
Install a tiny first-party script on your domain that logs pageviews without cookies, localStorage, or fingerprinting. Designed so ad blockers that target third-party analytics domains hit less often. Benefit: fuller traffic capture for teams stuck with consent-gated tags; trade-off: aggregate and channel metrics rather than person-level journey stitching.
Last-click revenue and ROAS attribution
Attributes conversions and revenue to channels, campaigns, and landing pages with last-click models the vendor positions as CRM-alignable. Built for eCommerce and hospitality media decisions—not generic pageview vanity charts. Limits: not a full multi-touch marketing mix model out of the box; validate against your CRM as the case studies do.
Real-time promo and campaign dashboards
Live views of revenue, channels, campaigns, and products during Promo Days so media teams can reallocate spend the same day. Suited to peak-load retail calendars. Constraint: value depends on tagging microconversions and keeping UTM hygiene; not a substitute for warehouse-grade BI alone.
LENS private AI on full capture
Optional LENS layer answers growth, risk, and wasted-spend questions in plain language against SealMetrics data (vendor states exclusive private AI on Enterprise tiers). Useful when analysts are scarce. Caveat: AI outputs are assistive—confirm high-stakes budget cuts against raw reports and offline finance data.
MCP and AI-assisted provisioning
Hosted MCP endpoint and docs let teams spin up accounts, pixels, and reports from AI coding assistants instead of a pure UI-only onboarding path. Speeds evaluation for engineering-heavy stacks. Still SaaS-only—there is no self-hosted SEAL Metrics server to run in your VPC.
EU Dublin storage with exports
Vendor documents processing and backups in Dublin, Ireland, with TLS 1.3, AES-256 at rest, and roughly 24-month analytics retention. API and BigQuery-style exports support dual-running with GA4. Hosting operator is described generically as an EU data center; Cloudflare sits on the transit path only.

Assurance & compliance: Offen Fair Web Analytics vs SEAL Metrics
Assurance & compliance	Offen Fair Web Analytics	SEAL Metrics
Independent security / architecture audit	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.	Not found Vendor mentions regular security audits and independent legal audits; no public third-party audit PDF found on site/docs.
ISO 27001	Not found No public ISO 27001 certification claim found on official site or docs.	Not found Data location docs list ISO 27001 as planned, not certified.
SOC 2 / SOC 3	Not found No public SOC 2/3 report found.	Partial Vendor docs list SOC 2 Type II as in progress — not a completed public report.
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 Spanish entity; cookieless architecture; EEA processing claims; DPA published. Legal conclusion remains for 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; analytics at rest in Dublin. Cloudflare (US group) processes TLS transit at EU edge. 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 Public DPA page; vendor states standard DPA with every plan, custom on Enterprise.
EU AI Act	Not applicable Web analytics metrics product; not an AI system product.	Not applicable Core product is measurement analytics; optional LENS private AI is a feature—confirm classification if heavily relied on for automated decisions.

Considerations & known limitations: Offen Fair Web Analytics vs SEAL Metrics
Considerations & known limitations	Offen Fair Web Analytics	SEAL Metrics
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 SOC 2 in progress and ISO planned per vendor docs. Enterprise security questionnaires may block until reports are available under NDA.
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 edge subprocessor (Cloudflare)	Not listed	Medium Even with Dublin storage, Cloudflare sits on encrypted traffic. Procurement that bans any US-group vendor in the path will need a written exception or alternative edge posture.
Consentless claim is architectural, not a warranty	Not listed	Medium Vendor argues no personal data / no cookies so analytics need no banner. Other scripts on the same site and national guidance still matter—get DPO sign-off.
SaaS-only, proprietary pipeline	Not listed	Low No self-host path. Mitigate with API/BigQuery export and dual-running with GA4 during evaluation.
Hosting operator not named	Not listed	Low Docs say EU data center in Dublin without naming the cloud or colo operator. Ask for the concrete provider in the TPSR pack.

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.

SEAL Metrics

Best fit when

European eCommerce, DTC, and hospitality brands measuring paid media ROAS against incomplete consent-gated analytics
Marketing ops and agencies that need a single channel revenue source of truth finance can challenge less often
Teams that want side-by-side GA4 calibration without migrating off Google Ads tooling immediately
DPOs and CISOs evaluating analytics that claim no cookies, no fingerprinting, and EEA-only storage of analytics data
Stacks that prefer SaaS plus API/BigQuery export over running Matomo themselves

Poor fit when

Organizations that require self-hosted or open-source analytics under their own admin control
Product teams needing session replay, heatmaps, or deep multi-touch product analytics (Heap/FullStory class)
Buyers that will not accept SaaS until ISO 27001 or SOC 2 Type II is fully certified and publicly evidenced
Hobby sites and blogs that only need lightweight open-source pageview analytics

Consider instead when

When: You need open-source or self-hosted cookieless analytics
Consider: Plausible Analytics (self-host Community Edition) or Matomo
SEAL Metrics is SaaS-only with no public source license.
When: You want simple privacy-first page analytics without eCommerce ROAS tooling
Consider: Simple Analytics or Pirsch Analytics
Lighter EU privacy analytics peers; less paid-media attribution depth.
When: You need managed Matomo with Swiss hosting or enterprise on-prem options
Consider: Friendly Analytics
Matomo ecosystem plugins and heatmaps vs SealMetrics proprietary ROAS focus.
When: You need Google Ads-native reporting and free-tier product analytics breadth
Consider: Google Analytics 4
Different sovereignty and consent trade-offs; often kept alongside SealMetrics.

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?

SEAL Metrics

What is the exact legal entity name (e.g. S.L.) and registered address for contracts?
Which Dublin operator hosts app/DB/backups (name on the infrastructure questionnaire)?
Current status and availability date of SOC 2 Type II report and ISO 27001 certification?
Does any account data, billing, or support channel leave the EEA (email, payments, CRM)?
For LENS AI: training data isolation guarantees and EU AI Act role for customer use cases?