Pirsch Analytics vs Stormly

Compare Pirsch Analytics and Stormly on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics

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

Stormly

Netherlands· Web Analytics

Needs review

Shortlist Stormly when you need Dutch-contracted, e-commerce-first product analytics: SKU-aware report packs, Shopify/Adobe-oriented setup, inbox-style AI anomaly narratives, and a public DPA. Skip when you need cookieless privacy web stats only (consider Plausible, Simple Analytics, or Pirsch), open-source self-hosting, verified ISO/SOC on a public cert page, or a subprocessor chain free of US-group cloud and Azure OpenAI.

E-commerce product analyticsSKU-aware reportsAI anomaly insightsShopify / Adobe CommerceNL entity + public DPASaaS (not self-host)

View listing Visit Website

Highlighted rows differ between the two products.

Pirsch Analytics vs Stormly: Snapshot
Feature	Pirsch Analytics	Stormly
Country of origin	Germany	Netherlands
Category	Web Analytics	Web Analytics
Open source	Yes	No
Self-hosted	No	No
Headquarters	Germany	Netherlands
Legal entity	Emvi Software GmbH (Nickelstraße 1b, 33378 Rheda-Wiedenbrück; HRB 11575, AG Gütersloh)	Monon B.V. (Lutmastraat 1-3, 1072 JL Amsterdam; KvK 76248747 per Terms)
Governing law	Germany / EU GDPR	Netherlands (Dutch law; Amsterdam courts)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Medium
Hosting / residency	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).	Client analytics subprocessors (Security Architecture): Hetzner (EU); Amazon AWS (US company, vendor states EU regions only for encrypted analytics backups); Vultr (US company); Microsoft Azure OpenAI (US company, vendor states EU Azure region). Plans market EU data residency. Controller privacy policy also references Vultr/AWS for account data, AuthSMTP EU + Amazon SES USA for email, Stripe for payments; marketing site uses Google Analytics and Hotjar.
Summary	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.	Dutch SaaS product analytics for e-commerce teams: SKU-aware reports, AI-assisted anomaly and root-cause insights, and Shopify/Adobe Commerce/Segment/GTM-oriented connections under Monon B.V. (Amsterdam).
Tags	analytics gdpr web-analytics cookie-free privacy open-source saas germany server-side-tracking	analytics gdpr e-commerce product-analytics ai shopify

At a glance: Pirsch Analytics vs Stormly
At a glance	Pirsch Analytics	Stormly
HQ	Rheda-Wiedenbrück, Germany	Not listed
Legal entity	Emvi Software GmbH	Not listed
Category	Web analytics (SaaS)	E-commerce product analytics (SaaS)
Open source	Core library AGPL-3.0; full SaaS commercial	No
Self-host	Enterprise on-prem option; not free CE	No
Commercial model	Usage-based (monthly page views); trial available	Free tier + monthly plan + custom; trial path on paid
Primary hosting (claimed)	Hetzner Germany (Nuremberg/Falkenstein)	Not listed
HQ / entity	Not listed	Monon B.V., Amsterdam, Netherlands
Hosting (public)	Not listed	Hetzner; AWS EU-region backups; Vultr; Azure OpenAI EU region (vendor docs)
Governing law	Not listed	Dutch law; Amsterdam courts

Key capabilities: Pirsch Analytics vs Stormly
Key capabilities	Pirsch Analytics	Stormly
Cookie-free hashing	Yes	Not listed
Open-source core (AGPL)	Yes	Not listed
Hetzner DE hosting (claimed)	Yes	Not listed
Server-side tracking	Yes	Not listed
Agency white-label	Yes	Not listed
Public DPA/AVV	Yes	Not listed
E-commerce product analytics	Not listed	Yes
SKU-aware reports	Not listed	Yes
AI anomaly insights	Not listed	Yes
Shopify / Adobe Commerce	Not listed	Yes
NL entity + public DPA	Not listed	Yes
SaaS (not self-host)	Not listed	Yes

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.

Stormly

AI agent for trends, anomalies, and root-cause style digs
Stormly positions an AI agent that watches connected e-commerce data for trends and anomalies (for example conversion drops or product spikes), then delivers plain-language findings—often to the inbox—with root-cause style exploration for questions like mobile conversion drops or regional return spikes. AI assistant access is plan-dependent; the public DPA documents Azure OpenAI (Microsoft) handling of assistant queries with a 30-day retention window and property stripping rules. Best for merchandising and growth leads who want narrative answers without waiting on a data team.
SKU-aware e-commerce report library (plus custom builds)
Ready reports target commerce questions: New Arrivals Performance (early SKU winners/laggards), Unviewed & Unsold Products, cart abandonment and revenue contribution by product/category, Conversion Journey and funnels by device/region, A/B test insights, Aha Moment Discovery, cross-selling analysis, and broader library items (retention, CLV, forecasting, SQL report, and more). Vendor materials state custom reports are included without a separate fee when a needed view is missing—useful for mid-market retailers that outgrow generic event charts.
Shopify, Adobe Commerce, Segment, and GTM-oriented connections
Homepage setup emphasizes linking Shopify, Adobe Commerce, or Segment quickly, with Google Tag Manager also listed among integrations. The DPA describes additional programmatic paths (JS library, import, custom endpoints, third-party sources). Fits stores already on common commerce stacks; teams on exotic storefronts should validate event coverage and product-feed depth in a pilot before replacing an existing analytics stack.
End-user tracking with IP anonymization defaults
Per the DPA, IP addresses for end-user analytics are not stored in full: the last octet is removed and geo/timezone are derived from the anonymized value. Web integrations automatically capture first-party cookie user ids, page/referrer/UTM context, and device metadata; app properties depend on client or CDP configuration. This is still full product analytics (not cookieless aggregate-only web stats)—clients remain responsible for consent banners and lawful basis for shopper tracking.
Public DPA, security architecture, and Dutch contracting
B2B buyers can download a Data Processing Agreement (effective 2023-09-06) and a Security Architecture page listing subprocessors, encryption expectations, backup retention (analytics backups up to six months), and logical tenant isolation. Contracts and DPA are governed by Dutch law with Amsterdam courts. Useful for EU procurement packages—but US-group subprocessors (AWS, Vultr, Azure OpenAI) still require transfer and CLOUD Act diligence.

Assurance & compliance: Pirsch Analytics vs Stormly
Assurance & compliance	Pirsch Analytics	Stormly
Independent security / privacy audit	Not found Open-source core allows code review; no public third-party audit PDF located in this research pass.	Not found Security Architecture describes encryption, monitoring, isolation, and vulnerability contact (security@stormly.com); no public third-party audit PDF found.
ISO 27001	Not found No ISO 27001 certificate or registry entry found on official trust pages reviewed.	Not found No public ISO 27001 certificate located on official legal/security pages reviewed.
SOC 2 / SOC 3	Not found No public SOC 2/3 report referenced on official pages reviewed.	Not found No public SOC 2/3 report located on official pages reviewed.
GDPR / EU data protection	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.	Vendor claimed NL entity; public privacy policy and DPA (GDPR-oriented); IP last-octet anonymization for end-user analytics; SCCs language for restricted transfers in DPA.
US CLOUD Act exposure (indicative)	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.	Partial EU entity / no known US parent, but public client subprocessors include AWS, Vultr, and Microsoft Azure OpenAI (US-group companies). Account path historically also lists Amazon SES and Stripe. Residency claims do not remove US-group legal exposure. Indicative only—not legal advice.
Data processing agreement (B2B)	Vendor claimed Downloadable English DPA and German AVV PDFs linked from docs.pirsch.io/privacy.	Vendor claimed Downloadable DPA PDF linked from stormly.com/dpa (effective 6 September 2023); audit rights and subprocessor notice described; Security Architecture lists subprocessors.
EU AI Act	Not applicable Classical web analytics product; not marketed as an AI system.	Partial Product includes an AI assistant via Azure OpenAI; not positioned as a high-risk AI system marketing claim. Buyers should map AI assistant use to their own AI Act / internal AI policy—vendor does not publish a full AI Act conformity package on the pages reviewed.

Considerations & known limitations: Pirsch Analytics vs Stormly
Considerations & known limitations	Pirsch Analytics	Stormly
US-group account/ops subprocessors	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.	Not listed
No public ISO/SOC or third-party audit	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.	Medium Enterprise security questionnaires may stall without ISO 27001/SOC 2 packs. DPA offers information/audit rights—plan time for NDA evidence requests.
Open-source core ≠ free full self-host	Low Teams assuming AGPL means free on-prem of the entire product may be surprised; full on-prem is positioned as Enterprise.	Not listed
Fingerprinting still needs legal fit review	Low Cookie-free hashing is not automatically lawful everywhere without information/consent analysis. Banner removal should be validated for your jurisdiction and tag stack.	Not listed
Page-view usage limits	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.	Not listed
US-group cloud and AI subprocessors	Not listed	Medium Despite Dutch HQ and EU residency marketing, client data paths publicly include AWS, Vultr, and Microsoft Azure OpenAI. Transfer tooling (SCCs) and encryption of backups are documented, but CLOUD Act / US legal process risk remains a diligence item for sovereignty-sensitive buyers.
Azure OpenAI retains assistant context 30 days	Not listed	Medium AI queries and aggregate report results are stored on Microsoft Azure OpenAI for 30 days per DPA. Property stripping reduces some identifiers, but misconfigured event properties could still expose sensitive content—govern AI use and property hygiene.
Controller privacy policy vs security architecture drift	Not listed	Low Privacy policy (controller, effective 2019) still emphasizes Vultr USA wording in places, while Security Architecture (client data) lists Hetzner/AWS/Vultr/Azure. Ask for a single current subprocessor and region matrix at contract time.
Not a privacy web-analytics substitute	Not listed	Low Full product analytics with cookies/identifiers for web integrations—not a cookieless aggregate counter. Consent UX remains on the client.

Fit

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.

Stormly

Best fit when

Merchandising, product, UX, and growth teams on Shopify or Adobe Commerce who need SKU, cart, and assortment analytics without a dedicated data science org
Retail brands that want ready e-commerce report templates (new arrivals, unviewed/unsold, funnels, A/B, aha moments) plus vendor-built custom reports
EU buyers who want a Dutch legal entity, Amsterdam courts, and a downloadable DPA/Security Architecture package
Teams that value AI-generated trend/anomaly narratives delivered to the inbox more than building every chart from a blank event schema
Stacks already using Segment or Google Tag Manager as the event pipe into analytics

Poor fit when

Publishers or marketing sites that only need lightweight privacy-friendly page analytics (not product/SKU depth)
Orgs that require open-source self-hosting or full control of a private analytics warehouse as the default
Procurement policies that forbid US-group subprocessors (AWS, Vultr, Microsoft Azure OpenAI) even when EU regions are claimed
Assurance programs that require public ISO 27001/SOC 2 evidence before pilot (not found on vendor pages reviewed)
Companies operating blockchain products/services—restricted by Stormly’s terms

Consider instead when

When: You only need privacy-oriented website metrics (pageviews, sources) rather than SKU-level product analytics
Consider: Plausible Analytics, Simple Analytics, or Pirsch Analytics
EU web-analytics peers; different category from e-commerce product analytics
When: You need deep general-purpose product analytics, large ecosystem, and mature multi-product SaaS event modeling
Consider: Mixpanel or Amplitude
US incumbents; stronger breadth, different jurisdiction and commercial model
When: You primarily need free/universal marketing acquisition reporting already embedded in the stack
Consider: Google Analytics (incumbent) or dual-run GA for marketing + Stormly for product/merch
GA is not SKU-first product analytics; Stormly is not a GA replacement for every report

Open questions for due diligence

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?

Stormly

Can Stormly provide a current region map (which data classes live on Hetzner vs Vultr vs AWS) under NDA for our DPIA?
Are ISO 27001, SOC 2, or penetration-test summaries available on request for enterprise security review?
Which event properties from our Shopify/Adobe feed are excluded from Azure OpenAI prompts by default in our tenant?
Do custom report builds and SQL access sit only on the custom tier, and what SLAs apply?
Has the 2019 controller privacy policy been superseded for hosting wording relative to the Security Architecture list?