Matomo by Stackhero vs nilly

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

Both listed as alternatives to: Fathom Analytics, Google Analytics

Logo: Matomo by Stackhero

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
Logo: nilly

nilly

Switzerland· Web Analytics

Needs review

Shortlist nilly when you want Swiss-entity, cookieless, ultra-light site analytics with realtime dashboards, city geo, custom events, unlimited sites, and an API—without GA4 consent weight. Skip when you need self-host/open source, enterprise audit packs, or deep marketing-suite analytics; consider Plausible Analytics, Simple Analytics, or etracker instead.

Cookieless trackingSwiss-hosted (claimed)Swiss entitySub-1 kB scriptREST APISaaS only
Matomo by Stackhero vs nilly: Snapshot
FeatureLogo: Matomo by StackheroMatomo by StackheroLogo: nillynilly
Country of originFranceSwitzerland
CategoryWeb AnalyticsWeb Analytics
Open sourceYesNo
Self-hostedNoNo
HeadquartersFranceSwitzerland
Legal entityStackhero (RCS Paris 512 366 378, VAT FR92512366378), 1 rue de Stockholm, 75008 Paris, FranceLyo GmbH, Europaallee 41, 8004 Zürich (CHE-417.675.763)
Governing lawFrench law; courts at registered head office (per Terms of service)Switzerland (terms)
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)MediumMedium
Hosting / residencyPrimary 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.Vendor FAQ: analytics servers in Switzerland (multiple locations). Public site reverse-DNS: KreativMedia/METANET Zürich. Customer-account subprocessors named in privacy policy: Stripe (US payments), Mailerlite (email). Avatars via Gravatar. No full public subprocessor list for backups/monitoring/CDN.
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.

Swiss privacy-first web analytics (Lyo GmbH): cookieless, sub-1kB tracking with realtime dashboards, city-level geo, custom events, unlimited sites, and a REST API as a lightweight Google Analytics alternative.

Tags
At a glance: Matomo by Stackhero vs nilly
At a glanceLogo: Matomo by StackheroMatomo by StackheroLogo: nillynilly
HQParis, France (1 rue de Stockholm, 75008)Zürich, Switzerland (Lyo GmbH)
Legal entityStackhero — RCS Paris 512 366 378Lyo GmbH (CHE-417.675.763)
StackOpen-source Matomo on dedicated Stackhero VMNot listed
Hosting regionsEU (France) or USA; backups in EU (vendor FAQ)Not listed
Commercial modelHourly instance billing; free trial; no standard commitmentTraffic-based plans; trial; no permanent free tier
CertificationsISO 27001:2022 claimed (BAB #254338)Not listed
Product modelNot listedSaaS web analytics (not self-hosted)
TrackingNot listedCookieless; no IP/fingerprint claims
Hosting (claimed)Not listedSwitzerland (multi-site)
Live site noteNot listedkandur.one (nilly branding; nilly.io DNS failed at research)
Key capabilities: Matomo by Stackhero vs nilly
Key capabilitiesLogo: Matomo by StackheroMatomo by StackheroLogo: nillynilly
Managed MatomoYesNot listed
Dedicated instanceYesNot listed
French PaaS operatorYesNot listed
ISO 27001 (claimed)YesNot listed
Automatic DPAYesNot listed
EU or US regionYesNot listed
Cookieless trackingNot listedYes
Swiss-hosted (claimed)Not listedYes
Swiss entityNot listedYes
Sub-1 kB scriptNot listedYes
REST APINot listedYes
SaaS onlyNot listedYes

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.

nilly

  • Sub-1 kB cookieless tracking script

    Vendor documents a client script under 1 kB with no cookies, no IP tracking, and no fingerprinting for site visitors. Suited to teams that want aggregate traffic metrics without analytics cookie banners; still get counsel for your jurisdiction and CMP setup.

  • Realtime dashboard with geo, tech, and campaigns

    Dashboards cover live visitors, overview metrics, top pages, referrers, UTM campaigns, geography from continent to city, and device/browser/OS breakdowns—enough for content and acquisition decisions without a full product-analytics suite.

  • Custom events, CSV export, and email reports

    Define custom events for conversion-style actions, export statistics as CSV, and receive email reports. Fits operators who need lightweight conversion signals and offline analysis rather than session replay or multi-step funnels.

  • REST API for stats, websites, and account

    Documented API endpoints (Bearer API key) manage stats queries (pageviews, visitors, referrers, events, geo, devices, and more), websites, and account objects—useful for internal dashboards or automations on traffic-based plans that include API access.

  • Unlimited websites on traffic-based plans

    Public pricing model is pageview-tier SaaS with unlimited websites per account and a short free trial—not a permanent free tier. Good for agencies or multi-brand operators who outgrow per-site free plans elsewhere; confirm current tiers on the vendor site.

Assurance & compliance: Matomo by Stackhero vs nilly
Assurance & complianceLogo: Matomo by StackheroMatomo by StackheroLogo: nillynilly
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

No public third-party audit report found for tracking claims.

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 vendor ISO 27001 certificate published on product site (underlying Swiss host DCs may be certified separately).

SOC 2 / SOC 3
Not found

No SOC 2/3 claim found on certifications/privacy/GDPR pages reviewed.

Not found
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

Swiss entity; privacy policy includes GDPR rights language; cookieless visitor tracking claimed. Confirm DPA for B2B.

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

Swiss operator, no known US parent, Swiss-claimed analytics hosting; US SaaS subprocessors Stripe (payments) and Gravatar (avatars) on customer path. Not legal advice.

Data processing agreement (B2B)
Vendor claimed

DPA applies automatically with Terms of service; PDF downloadable from the GDPR & DPA page.

Not found

No public DPA download found; request from vendor.

EU AI Act
Not applicable

Web analytics hosting; not positioned as an AI system product.

Not applicable

Web analytics product; not marketed as an AI system.

Swiss Made Software / Swiss Web labelsNot listed
Vendor claimed

Cited on About and Swiss Union member page as recognition/labels—not a security audit.

Considerations & known limitations: Matomo by Stackhero vs nilly
Considerations & known limitationsLogo: Matomo by StackheroMatomo by StackheroLogo: nillynilly
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
Brand/domain transition (nilly.io vs kandur.one)Not listed
Medium

Product still branded nilly, but the live marketing/API host is kandur.one; nilly.io did not resolve in DNS during research. Verify tracking domains, docs, and status before production cutover.

US SaaS on customer account pathNot listed
Medium

Stripe (payments) and Gravatar (avatars) are US-group services. Visitor metrics are claimed Swiss-hosted and non-personal, but account/billing data is not Switzerland-only end-to-end.

Thin public assurance packNot listed
Medium

No public ISO 27001/SOC 2, independent security audit, or DPA page found. Fine for many SMB shortlists; friction for regulated enterprise questionnaires.

No self-host or open-source editionNot listed
Low

Cannot run on your own infra or audit server code from a public repo. Hard limit for sovereignty programs that require self-host.

Small independent operatorNot listed
Low

Founder-owned Swiss GmbH without VC narrative—positive for independence, but buyers should assess support SLAs, roadmap continuity, and single-vendor concentration.

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.

nilly

Best fit when

  • Privacy-conscious SMBs and indie sites replacing GA4 with aggregate metrics only
  • Teams that want Swiss legal entity and Swiss-located analytics servers
  • Operators running many sites who benefit from unlimited websites on traffic tiers
  • Builders who need a simple REST API for pageviews, referrers, geo, and events
  • Sites prioritizing minimal JS weight and fewer analytics consent prompts

Poor fit when

  • Organizations that must self-host or review open-source analytics code
  • Buyers needing published ISO 27001/SOC 2 or a full public DPA/subprocessor pack
  • Marketing teams requiring session replay, heatmaps, or advanced e-commerce/ad sync suites
  • Enterprises that need SSO/SCIM, formal SLAs, and large-vendor assurance paperwork as table stakes

Consider instead when

  • When: You want open-source and/or self-host privacy analytics with a larger community

    Consider: Plausible Analytics or Pirsch Analytics

    nilly is proprietary SaaS only.

  • When: You want another European cookieless SaaS with a simple product story

    Consider: Simple Analytics

    Dutch peer; compare geo depth, API, and residency claims side by side.

  • When: You need deeper marketing, shop, and tag/consent analytics for EU enterprises

    Consider: etracker

    German suite-oriented alternative; heavier than nilly's lightweight dashboard.

  • When: You depend on free unlimited scale and Google ads/ecosystem integration

    Consider: Google Analytics (GA4)

    Different privacy and residency tradeoffs; not a sovereignty shortlist.

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)?

nilly

  • Will Lyo GmbH sign a B2B DPA and provide a current full subprocessor list (including backups, monitoring, CDN)?
  • Is analytics data retained only on Swiss hosts, or are any DR/replicas outside Switzerland?
  • What is the durable public domain for tracking scripts and API (kandur.one vs nilly.io) for the next 12 months?
  • Are there enterprise features (SSO, roles, retention controls, MSA/SLA) beyond self-serve traffic plans?
  • Can the vendor provide any independent security assessment under NDA?