Matomo by Stackhero vs Trackboxx

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

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

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

Trackboxx

Germany· Web Analytics

Needs review

Shortlist Trackboxx when you want German-operated, cookie-free hosted analytics with ecommerce and agency-friendly public dashboards. Skip when you need self-host/open-source control or GA-class product analytics—consider Plausible (self-host option) or Matomo instead.

Cookie-free trackingGermany-operatedFrankfurt analytics hostingE-commerce analyticsB2B DPA availableManaged SaaS

View listing Visit Website

Highlighted rows differ between the two products.

Matomo by Stackhero vs Trackboxx: Snapshot
Feature	Matomo by Stackhero	Trackboxx
Country of origin	France	Germany
Category	Web Analytics	Web Analytics
Open source	Yes	No
Self-hosted	No	No
Headquarters	France	Germany
Legal entity	Stackhero (RCS Paris 512 366 378, VAT FR92512366378), 1 rue de Stockholm, 75008 Paris, France	Trackboxx / Christian Pust (sole trader imprint; Halberstadt seat, Grönwohld branch)
Governing law	French law; courts at registered head office (per Terms of service)	Not listed
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.	Visitor analytics: TK Enterprises Ltd infrastructure in First Colo Frankfurt. CDN: BunnyWay d.o.o. (Slovenia). Payments: Paddle.com Market Ltd (UK). Email/newsletters: Amazon SES (AWS; EU regions primary, possible US). Chat on marketing site: Userlike UG (Germany).
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.	German cookie-free web analytics SaaS: day-rotating hash tracking, ecommerce and UTM dashboards, hosted analytics in Frankfurt with a published B2B DPA.
Tags	analytics privacy saas gdpr matomo open-source france managed-hosting iso-27001	analytics privacy saas gdpr cookie-free ecommerce

At a glance: Matomo by Stackhero vs Trackboxx
At a glance	Matomo by Stackhero	Trackboxx
HQ	Paris, France (1 rue de Stockholm, 75008)	Halberstadt / Grönwohld, Germany
Legal entity	Stackhero — RCS Paris 512 366 378	Trackboxx / Christian Pust (imprint)
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	Pageview packages; free tier + trial; Paddle checkout
Certifications	ISO 27001:2022 claimed (BAB #254338)	Not listed
Product type	Not listed	Managed web analytics SaaS
Open source	Not listed	No
Self-host	Not listed	No
Analytics hosting	Not listed	First Colo, Frankfurt (via TK Enterprises Ltd)

Key capabilities: Matomo by Stackhero vs Trackboxx
Key capabilities	Matomo by Stackhero	Trackboxx
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
Cookie-free tracking	Not listed	Yes
Germany-operated	Not listed	Yes
Frankfurt analytics hosting	Not listed	Yes
E-commerce analytics	Not listed	Yes
B2B DPA available	Not listed	Yes
Managed SaaS	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.

Trackboxx

Cookie-free day-hash session tracking
No analytics cookies. Same-day visitor correlation uses hashes of IP, user agent, site ID, and a daily rotating signature (page hashes also include host/path). Hashes expire within 24 hours so multi-day visitor histories and IP recovery are not available by design.
Traffic, channel, and live visitor dashboards
Dashboards cover visits, pageviews, bounce rate, dwell time, devices/browsers, geo down to city, channel mix including AI traffic, outbound link clicks, live visitors on a short refresh interval, and period-over-period comparisons without a heavy analyst UI.
E-commerce funnels and revenue breakdowns
Shop metrics include products sold, cart abandonment, add-to-cart style signals, checkout funnel visibility, and revenue by channel and location—aimed at operators who need store KPIs without a full GA4 ecommerce implementation.
UTM, goals, GSC keywords, and public reports
Campaign UTMs, conversion goals (including auto goals), optional Google Search Console keyword views, shareable public dashboards (URL or iframe), and PDF reports support marketers and agencies who need client-facing summaries.
CMS and shop plugins plus GA import
Documented integrations include WordPress, Shopware, Shopify, JTL, and ePages. Help center also covers script install, excluding own IP/paths, ads tracking patterns, and importing historical Google Analytics data when migrating.

Assurance & compliance: Matomo by Stackhero vs Trackboxx
Assurance & compliance	Matomo by Stackhero	Trackboxx
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 PDF or cert registry entry found on primary pages.
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 ISO 27001 claim found on imprint, help center, or DPA materials reviewed.
SOC 2 / SOC 3	Not found No SOC 2/3 claim found on certifications/privacy/GDPR pages reviewed.	Not found No SOC 2/3 report referenced on public trust materials 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 German controller imprint; cookie-free hash model; public DPA; processing described as EU/EEA. Vendor asserts DSGVO fitness—confirm with counsel for your site stack.
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 sole-trader operator, no known US parent; analytics hosting claimed in Frankfurt. Partial/medium because privacy policy names Amazon SES (AWS) for email with possible US transfers; payments via UK Paddle. 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 Free AV/DPA offered at order and as PDF; annex lists hosting, Paddle, BunnyWay.
EU AI Act	Not applicable Web analytics hosting; not positioned as an AI system product.	Not applicable Web analytics SaaS; not an AI system product for AI Act high-risk classification purposes.

Considerations & known limitations: Matomo by Stackhero vs Trackboxx
Considerations & known limitations	Matomo by Stackhero	Trackboxx
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
Consent banner claim is vendor legal opinion	Not listed	Medium Trackboxx argues legitimate interest and no opt-in for its cookie-free tracker alone, while noting some DPOs disagree. Other tags on the site can still force banners. Treat as diligence input, not a legal certificate.
Amazon SES on email path	Not listed	Medium Privacy policy discloses AWS SES for system/newsletter email with possible US transfers. Distinct from Frankfurt analytics storage, but raises residual US-group process exposure for account communications.
No self-host edition	Not listed	Low Managed SaaS only. Policies that mandate customer-operated infrastructure need a different product.
No public ISO/SOC/independent audit	Not listed	Medium Procurement teams that require cert packs will need questionnaires, DPA annex review, and possibly NDA materials beyond the public site.
Same-day hash limits multi-day user journeys	Not listed	Low By design you cannot rebuild long-lived individual visitor histories across days. Teams needing identity-resolution analytics will find this a hard product limit.

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.

Trackboxx

Best fit when

German/EU SMEs and agencies replacing cookie-heavy GA for simpler privacy-oriented traffic stats
Online shops that need cart abandonment and revenue-by-channel without a full GA4 ecommerce stack
Teams that want public dashboards or PDF reports for clients and partners
Sites prioritizing fuller capture when consent banners and blockers suppress third-party analytics
Operators who accept managed SaaS and pageview-based packaging over self-hosting

Poor fit when

Organizations that must self-host or run open-source analytics under their own keys
Product/growth teams needing session replay, heatmaps, or advanced funnel/experiment suites
Enterprises requiring published ISO/SOC audit packs and extensive SSO/export documentation before shortlist
Buyers who need multi-year individual visitor identity graphs rather than same-day hash sessions

Consider instead when

When: You need cookieless EU analytics with an official self-host path
Consider: Plausible Analytics (Cloud or Community Edition)
Trade Trackboxx ecommerce/plugin depth for open-source deployability.
When: You want maximal privacy minimalism and a very small surface area
Consider: Simple Analytics
Simpler feature set; less ecommerce and shop-plugin emphasis than Trackboxx.
When: You need deep self-hosted analytics or on-prem control
Consider: Matomo or Piwik PRO-class platforms
Heavier ops and UI; stronger fit for full data residency under your infrastructure.
When: You depend on Google Ads identity graphs, Audiences, and free unlimited scale
Consider: Google Analytics
Keep GA only with full consent/transfer diligence; not a privacy substitute for Trackboxx.

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

Trackboxx

Is the DPA annex (subprocessors, TOMs) current relative to Amazon SES and any other processors used in production today?
What backup/DR locations and encryption practices apply beyond the First Colo Frankfurt statement?
Are enterprise SSO, data export APIs, or retention controls documented for larger buyers?
Has any independent penetration test or privacy audit been completed under NDA?