Matomo by Stackhero vs Stormly

Compare Matomo by Stackhero and Stormly on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics

Matomo by Stackhero

France· Web Analytics

Needs review

Shortlist when you want full Matomo on a dedicated French-operated bare-metal instance with one-click updates and hourly billing—especially if you prefer unlimited site/seat product framing over hit-metered multi-tenant SaaS. Skip when you need EU-only with no US region option, root/SSH access, or a minimal cookieless counter—consider self-hosted Matomo, Friendly Analytics, or Plausible instead.

Managed MatomoDedicated instanceFrench PaaS operatorISO 27001 (claimed)Automatic DPAEU or US region

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.

Matomo by Stackhero vs Stormly: Snapshot
Feature	Matomo by Stackhero	Stormly
Country of origin	France	Netherlands
Category	Web Analytics	Web Analytics
Open source	Yes	No
Self-hosted	No	No
Headquarters	France	Netherlands
Legal entity	Stackhero (RCS Paris 512 366 378, VAT FR92512366378), 1 rue de Stockholm, 75008 Paris, France	Monon B.V. (Lutmastraat 1-3, 1072 JL Amsterdam; KvK 76248747 per Terms)
Governing law	French law; courts at registered head office (per Terms of service)	Netherlands (Dutch law; Amsterdam courts)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Medium
Hosting / residency	Primary compute: Stackhero bare-metal cloud, customer-chosen region EU (France) or USA. Backups: stored in the EU per Matomo FAQ; encrypted atomic images retained up to ~3 months. Not built on AWS/GCP/Azure as the stated compute substrate. Payment processor (unnamed) handles card data; privacy policy mentions third-party messaging/stats tools without a full named subprocessor table.	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	French PaaS-managed Matomo on dedicated bare-metal instances: unlimited sites until capacity, one-click updates, EU or US region choice, with hourly billing and an automatic DPA.	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 matomo privacy open-source saas france managed-hosting iso-27001	analytics gdpr e-commerce product-analytics ai shopify

At a glance: Matomo by Stackhero vs Stormly
At a glance	Matomo by Stackhero	Stormly
HQ	Paris, France (1 rue de Stockholm, 75008)	Not listed
Legal entity	Stackhero — RCS Paris 512 366 378	Not listed
Stack	Open-source Matomo on dedicated Stackhero VM	Not listed
Hosting regions	EU (France) or USA; backups in EU (vendor FAQ)	Not listed
Commercial model	Hourly instance billing; free trial; no standard commitment	Free tier + monthly plan + custom; trial path on paid
Certifications	ISO 27001:2022 claimed (BAB #254338)	Not listed
HQ / entity	Not listed	Monon B.V., Amsterdam, Netherlands
Category	Not listed	E-commerce product analytics (SaaS)
Hosting (public)	Not listed	Hetzner; AWS EU-region backups; Vultr; Azure OpenAI EU region (vendor docs)
Open source	Not listed	No
Self-host	Not listed	No
Governing law	Not listed	Dutch law; Amsterdam courts

Key capabilities: Matomo by Stackhero vs Stormly
Key capabilities	Matomo by Stackhero	Stormly
Managed Matomo	Yes	Not listed
Dedicated instance	Yes	Not listed
French PaaS operator	Yes	Not listed
ISO 27001 (claimed)	Yes	Not listed
Automatic DPA	Yes	Not listed
EU or US region	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

Matomo by Stackhero

Dedicated bare-metal Matomo instance
Each customer gets an isolated VM on Stackhero’s own bare-metal cloud (Stackhero DC OS), not shared multi-tenant Matomo. Local disks and included Redis are positioned for high IOPS and heavy traffic—fit teams that outgrow noisy-neighbor shared analytics clouds.
Unlimited sites, members, segments, and goals until capacity
Stackhero does not meter websites, team seats, segments, or goals as product SKUs; you scale by instance size (published up to 16 vCPUs / 64 GB RAM). Retention is limited by disk, not a fixed product TTL—plan storage for long history.
One-click Matomo updates and managed ops (no SSH)
Stackhero delivers Matomo updates for dashboard application; firewall IP rules are customer-configurable. SSH is intentionally unavailable on the managed service—good for reduced surface area, poor fit if you need custom OS packages.
Custom domain, GeoIP2, and dedicated notification email
Point matomo.yourdomain.com with TLS 1.3/ECDSA, ship visitor location via bundled GeoIP2, and send unlimited Matomo reports/alerts through a per-instance email path—reduces glue work after first deploy.
Atomic encrypted daily backups (EU vault)
24-hour atomic image backups (plus event-driven backups on upgrades) are validated, then encrypted (OpenPGP ECDH/Curve25519) and retained up to three months. Vendor FAQ states backups are stored in the EU even when regions differ—confirm dual-region implications for US instances.
Hourly billing with EU or US region choice
Spin services up/down with hourly charging and a single monthly invoice; free trial without payment method. Choose European (France) or USA placement at create time—region is a first-class control for residency, not a hidden default.

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: Matomo by Stackhero vs Stormly
Assurance & compliance	Matomo by Stackhero	Stormly
Independent security / no-logs audit	Not found ISO 27001 and bug-bounty openness claimed; no public independent no-logs audit report specific to analytics found.	Not found Security Architecture describes encryption, monitoring, isolation, and vulnerability contact (security@stormly.com); no public third-party audit PDF found.
ISO 27001	Vendor claimed Vendor publishes ISO/IEC 27001:2022 certificate #254338 from the British Assessment Bureau (PDF). Not re-verified against the issuer’s public register in this draft.	Not found No public ISO 27001 certificate located on official legal/security pages reviewed.
SOC 2 / SOC 3	Not found No SOC 2/3 claim found on certifications/privacy/GDPR pages reviewed.	Not found No public SOC 2/3 report located on official pages reviewed.
GDPR / EU data protection	Vendor claimed French entity; public GDPR & DPA page; customer controller / Stackhero processor model; EU region option for service data.	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 French entity, no known US parent, non-hyperscaler bare-metal hosting claimed. Medium/partial because USA is a first-class hosting region; EU-only only when the customer creates the service in Europe. Backups stated as EU-stored. 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 DPA applies automatically with Terms of service; PDF downloadable from the GDPR & DPA page.	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 Web analytics hosting; not positioned as an AI system product.	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: Matomo by Stackhero vs Stormly
Considerations & known limitations	Matomo by Stackhero	Stormly
Optional US hosting region	Medium Platform offers USA placement alongside France/EU. Mis-selected region or unclear contract language can put visitor analytics outside the EU. Procurements that require EU-only must pin region at create time and in the order form.	Not listed
EU backups when primary is US	Medium FAQ states backups are stored in the EU. If an instance runs in the USA, confirm whether visitor data is dual-homed (US primary + EU backup) and how that affects DPIA and transfer tools.	Not listed
No SSH / managed-only host	Low Cannot install arbitrary system software or agents; support hours stated as CET office hours for basic platform support—not full Matomo application consulting.	Not listed
Limited named subprocessor list	Medium Privacy policy mentions third-party tools and a payment processor without a detailed public subprocessor register. Request the annex in diligence if procurement requires named processors.	Not listed
ISO certificate vendor-published	Low ISO 27001:2022 is claimed with a public PDF and BAB certificate number; validate scope, sites, and validity dates with the certification body before treating it as verified.	Not listed
Matomo privacy configuration is yours	Low Hosting in the EU does not auto-configure consent, IP anonymization, or cookieless modes. Controllers remain responsible for Matomo GDPR tooling and site policy.	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.
No public ISO/SOC or independent audit	Not listed	Medium Enterprise security questionnaires may stall without ISO 27001/SOC 2 packs. DPA offers information/audit rights—plan time for NDA evidence requests.
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

Matomo by Stackhero

Best fit when

Teams that want Matomo’s full analytics/admin surface without running OS or Matomo upgrades themselves
Buyers who prefer a dedicated VM and capacity-based limits over multi-tenant hit metering
Orgs consolidating Matomo with other Stackhero-managed open-source services under one French operator
Projects that need hourly elasticity and the ability to stop billing with one click
Controllers who will configure Matomo privacy features themselves and want a signed/automatic DPA plus ISO 27001 claims

Poor fit when

Requirements that forbid any US hosting option or dual-region backup stories—platform publicly offers USA regions
Teams that need SSH, custom kernels, or non-Matomo system agents on the host
Buyers seeking only a lightweight cookieless pageview product (Plausible-class tools are simpler)
Organizations that must self-host inside their own cloud account with no third-party PaaS operator
Use cases needing a named public subprocessor register beyond Stackhero’s high-level privacy/GDPR pages

Consider instead when

When: You want Swiss Matomo-as-a-Service with cookieless defaults and CH product hosts
Consider: Friendly Analytics
Different operator, residency story, and privacy defaults; still Matomo-based.
When: You need enterprise analytics packaging beyond plain managed Matomo
Consider: Piwik PRO
Compare modules, contracts, and hosting regions independently.
When: You only need a minimal open-source-friendly counter with simple SaaS UX
Consider: Plausible Analytics
Far less Matomo depth; different product surface.
When: You require full root control and in-house residency guarantees
Consider: Self-hosted Matomo on your own EU IaaS
Maximum control; you own updates, backups, and hardening.

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

Matomo by Stackhero

Will the order form and DPA annex permanently pin the Matomo instance to the EU (France) region with no US failover?
For US-region instances, what exact data is copied to EU backup vaults and under which transfer mechanism?
Who is the unnamed parent company referenced on the About page, and is there any US ownership or PE?
Can ISO 27001 certificate 254338 be validated on the British Assessment Bureau (or successor) public register for current scope/dates?
Which payment, support, and website analytics providers process Stackhero account data (named subprocessor list)?

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?