Analyzati vs Offen Fair Web Analytics

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

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

Logo: Analyzati

Analyzati

Spain· Web Analytics

Needs review

Shortlist when you want Spanish/EU-legal SaaS web analytics with cookie-free daily uniques, city geo, AI referral views, and a public DPA—without self-hosting. Skip when you need open source, on-prem, multi-day retention/cohorts, or certified ISO/SOC evidence; consider Plausible Analytics or Matomo instead.

Cookie-free trackingEU entity (Spain)App on AWS ParisPublic DPAAI referral insightsSaaS only
Logo: Offen Fair Web Analytics

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
Analyzati vs Offen Fair Web Analytics: Snapshot
FeatureLogo: AnalyzatiAnalyzatiLogo: Offen Fair Web AnalyticsOffen Fair Web Analytics
Country of originSpainGermany
CategoryWeb AnalyticsWeb Analytics
Open sourceNoYes
Self-hostedNoYes
HeadquartersSpainGermany
Legal entityIncorporated in Barcelona, Spain (exact legal name not published on pages reviewed)Public legal notice lists Frederik Ring, Berlin (offen.software); product authors Frederik Ring and Hendrik Niefeld—no separate GmbH name verified on imprint
Governing lawSpain / EU (GDPR referenced; confirm governing law clause in Terms)Germany (indicative from Berlin imprint)
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)MediumLow
Hosting / residencyVisitor/app data: AWS in Paris (vendor). Marketing site: Namecheap in Amsterdam. Backups described as EU. Other subprocessors named in privacy materials: Stripe (payments), AWS (email), Freshworks (support), hCaptcha (registration).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

Spanish cookie-free web analytics SaaS: real-time traffic, city-level geo, AI referral sources, and event tracking without cookies, stored IPs, or fingerprints.

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
At a glance: Analyzati vs Offen Fair Web Analytics
At a glanceLogo: AnalyzatiAnalyzatiLogo: Offen Fair Web AnalyticsOffen Fair Web Analytics
HQ / entityBarcelona, Spain (EU entity claimed; exact registry name not on public pages reviewed)Not listed
Product typeHosted web analytics SaaSNot listed
Open sourceNoNot listed
Self-hostNoNot listed
App hostingAWS, Paris (vendor claim)Not listed
Commercial modelFreemium + pageview / site-count tiersNot listed
DPAPublic; accepted via Terms of ServiceNot listed
HQ / authorsNot listedBerlin, Germany (Frederik Ring & Hendrik Niefeld)
LicenseNot listedApache-2.0 (code/docs); logo CC-BY-NC-ND-4.0
DeliveryNot listedSelf-host only (binary, Docker, community deploys)
Consent modelNot listedOpt-in only; first-party cookies
Default retentionNot listed6 months (configurable shorter)
Funding noteNot listedNLnet NGI support (project-stated)
Key capabilities: Analyzati vs Offen Fair Web Analytics
Key capabilitiesLogo: AnalyzatiAnalyzatiLogo: Offen Fair Web AnalyticsOffen Fair Web Analytics
Cookie-free trackingYesNot listed
EU entity (Spain)YesNot listed
App on AWS ParisYesNot listed
Public DPAYesNot listed
AI referral insightsYesNot listed
SaaS onlyYesNot listed
Opt-in onlyNot listedYes
Browser E2E encryptionNot listedYes
Self-hostedNot listedYes
Apache-2.0Not listedYes
Visitor data accessNot listedYes
Berlin-based projectNot listedYes

Analyzati

  • Cookie-free uniques with daily rotating salt

    Counts daily unique visitors by hashing IP + User-Agent + domain with a salt that is destroyed every 24 hours. No cookies, localStorage, or device-persistent IDs; raw IP and full UA are not stored. Trade-off: no multi-day retention or new-vs-returning series.

  • City-level geo without retained IPs

    Derives continent, country, region, and city for maps and rankings from the request IP, then discards the IP. Useful for market mix reporting when you do not need ISP- or coordinate-level precision.

  • AI referral and channel acquisition views

    Breaks down how visitors arrive—search, referring sites, and AI assistants such as ChatGPT, Perplexity, Gemini, and Claude—so content teams can see discovery outside classic SEO referrers.

  • Real-time dashboard, events, export, and API

    Live visitor activity, page performance, device/browser/OS stats, custom events and campaigns, weekly email reports, data export, and API access on published plans. Integrations include a WordPress plugin and Google Tag Manager snippet placement.

  • Public B2B DPA with processor role

    A published Data Processing Agreement (effective August 2022) treats Analyzati as processor and the customer as controller for visitor measurement. Acceptance is tied to product use under the Terms of Service rather than a bespoke countersignature workflow.

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: Analyzati vs Offen Fair Web Analytics
Assurance & complianceLogo: AnalyzatiAnalyzatiLogo: Offen Fair Web AnalyticsOffen Fair Web Analytics
Independent security / no-logs audit
Not found

No public third-party audit PDF or no-logs attestation found on official pages reviewed.

Not found

No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.

ISO 27001
Not found

No ISO 27001 certificate claim located on homepage, privacy, or DPA 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 claim found on public trust materials.

Not found

No public SOC 2/3 report found.

GDPR / EU data protection
Vendor claimed

EU entity (Barcelona); public GDPR/PECR/CCPA compliance pages; anonymisation design documented; controller/processor roles in DPA.

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

Spanish/EU vendor with no known US parent, but application hosting on AWS (Paris) and US-group subprocessors (Stripe, Freshworks, AWS email, hCaptcha). Residency ≠ ownership. 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

Public DPA effective 18 Aug 2022; vendor says acceptance is automatic via product use / ToS—no separate signature required.

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

Product reports AI *referral traffic*; it is not marketed as a high-risk AI system provider.

Not applicable

Web analytics metrics product; not an AI system product.

Considerations & known limitations: Analyzati vs Offen Fair Web Analytics
Considerations & known limitationsLogo: AnalyzatiAnalyzatiLogo: Offen Fair Web AnalyticsOffen Fair Web Analytics
AWS and US-group subprocessors
Medium

Measurement app is on AWS Paris; account path also uses Stripe, Freshworks, AWS email, and hCaptcha. EU regions reduce some transfer friction but do not erase US-group provider diligence for many public-sector and bank questionnaires.

Not listed
No public ISO/SOC or independent audit
Medium

Security claims rely on vendor documentation (HTTPS, hashing, firewalls, backups). Organisations with mandatory cert evidence will need vendor outreach or a different shortlist.

Not listed
No multi-day visitor identity
Low

Daily salt rotation blocks persistent uniques. Expect gaps vs Google Analytics for returning users, frequency, and retention—by design.

Not listed
SaaS lock-in / no self-host
Low

No self-host edition found. Exit requires export/API migration to another tool; confirm export completeness in a trial.

Not listed
Exact registry name not on marketing pages
Low

Vendor states Barcelona incorporation but public pages reviewed did not display a full Spanish company registration string—collect CIF/NIF and full legal name during contracting.

Not listed
Opt-in undercounts absolute trafficNot 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 secretsNot 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 architectureNot 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 jurisdictionNot 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 packNot 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 onlyNot 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

Analyzati

Best fit when

  • Marketing sites and content properties that need page views, referrers, device mix, and city-level geo without analytics cookies
  • Teams replacing Google Analytics primarily for privacy/consent simplification rather than advanced product analytics
  • Agencies or freelancers who want multi-site hosted analytics with a freemium entry path
  • Buyers who want a published DPA and Spanish/EU legal entity on the order form
  • Content teams tracking discovery from AI assistants alongside classic channels

Poor fit when

  • Product or growth teams that require funnels, multi-day retention, cohorts, or cross-device identity
  • Organisations that mandate open-source code or self-hosted deployment
  • Procurement that will not accept AWS (US-group) or other US SaaS subprocessors even in EU regions
  • Security questionnaires that demand public ISO 27001 / SOC 2 reports or independent no-logs audits
  • Use cases needing session replay, heatmaps, or advertising audience export

Consider instead when

  • When: You need open-source analytics you can self-host and audit

    Consider: Plausible Analytics (self-host option) or Matomo

    Analyzati is SaaS-only with no public source release found.

  • When: You want a comparable cookie-free European SaaS peer for side-by-side trials

    Consider: Plausible Analytics or Simple Analytics

    Compare AI-referrer and geo depth, DPA wording, and hosting/subprocessor lists in each trial.

  • When: You need full-stack product analytics and advertising linkage

    Consider: Google Analytics (incumbent) or a dedicated product analytics suite

    Analyzati deliberately collects a minimal metric set and does not sell ad-tech profiles.

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

Analyzati

  • What is the full Spanish legal entity name and company registry identifier for the order form?
  • Is a current written subprocessor list available beyond privacy-policy mentions (including backup regions and any CDN)?
  • Can the vendor provide ISO/SOC evidence or a third-party penetration test under NDA?
  • What is the analytics data retention window per plan, and what does the API export include?
  • Which governing law and venue apply under the current Terms of Service?

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?