# Matomo vs Userpilot (slim)

> Userpilot scores 64.4 (B) to Matomo's 61.7 (C) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/matomo-vs-userpilot.md (~4,350 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/matomo-vs-userpilot.json · canonical https://www.anchorterminal.com/compare/matomo-vs-userpilot
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Userpilot scores 64.4 (B) on agent readiness against Matomo's 61.7 (C), and leads in 1 of 7 scored categories. Matomo leads on agent ergonomics, security & auth and transparency & trust. Both do analytics queries.

- Matomo: C 61.7, rank #594 of 1486 · https://www.anchorterminal.com/tools/matomo.min.md
- Userpilot: B 64.4, rank #471 of 1486 · https://www.anchorterminal.com/tools/userpilot.min.md
- Matomo, good for Teams that want web and product analytics with data kept in the EU or on their own servers, queried by report, segment, funnel or cohort. Ahead on Agent ergonomics, 78 against 60; Security & auth, 71 against 62; Transparency & trust, 74 against 59. Also Open source.
- Userpilot, good for SaaS teams already using Userpilot for onboarding who want an agent to answer analytics questions and draft segments and surveys. Ahead on Reliability, 82 against 38. Also A hosted endpoint, with nothing to install.

| Category | Matomo | Userpilot |
| --- | --- | --- |
| Reliability (16%) | 38 | 82 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 71 |
| Agent ergonomics (13%) | 78 | 60 |
| Security & auth (14%) | 71 | 62 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 79 |
| Transparency & trust (7%) | 74 | 59 |

| Fact (where they differ) | Matomo | Userpilot |
| --- | --- | --- |
| Vendor | InnoCraft Limited | Userpilot, Inc. |
| Hosted endpoint | no (local only) | `https://mcp.userpilot.io/mcp` |
| Licence | Matomo core is GPL-3.0-or-later and the MCP server plugin is GPL v3 or later. Matomo Cloud is a hosted service under InnoCraft's terms. Paid On-Premise plugins fall under the InnoCraft EULA | none |
| Tools exposed | 19 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.userpilot/mcp` |
| Last release | 2026-10-22 | 2026-10-11 |
| Terms last updated | 2025-04-10 | 2024-04-23 |
| Privacy policy last updated | 2026-05-05 | 2025-03-11 |
| Terms restrict automated access | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 236k npm/wk |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Reliability, Userpilot +44: Matomo 38 (Graded on the hosted lines, for a Matomo Cloud instance reached through the Reporting HTTP API and the MCP server included with Cloud. status.matomo.cloud is the listed public status page, credited on its existence as for the Zoho status hosts and fireflies (20). On 4 November its robots.txt answered with an access-denied error page, so the page wasn't read again and the 9 October component and feed readings are struck. No 90-day incident record could be read then or now (5). No API rate limit numbers were found. The terms reserve suspension for excessively frequent requests, and `API.getBulkRequest` is capped at 50 URLs for anonymous callers (3 of 15). No 429 or retry guidance and no idempotency keys were found (0). No SLA for Cloud was found, and the terms supply the service as is (0). The Reporting API and MCP plugin 5.1.1 are stable releases (10).); Userpilot 82 (Graded on the hosted service with the hosted lines. Better Stack status page at status.userpilot.io with components for ingestion in three regions, the SDKs, the web application APIs and the website (20). From August to November 2026 the page shows only scheduled maintenance windows of two to four hours, with no incidents; the MCP server isn't a component (30). 600 requests a minute per token for the real-time APIs, but no numbers for MCP or export (12 of 15). 429 documented with exponential backoff guidance; no Retry-After or idempotency guidance (10 of 15). The SLA is a custom Enterprise contract term, not published (0). The MCP server is 1.0.0 in the registry with no beta label (10). 20+30+12+10+0+10 = 82.)
- Agent ergonomics, Matomo +18: Matomo 78 (The MCP server has 19 tools, 12 of them visible by default (15), plus 6 because the seven raw API tools stay hidden until an administrator allows them by read, create, update or delete class (21). `filter_limit`, `filter_offset`, sorting, pattern filters, `showColumns` and segments on the API, and cursors with a 250-row cap on the MCP report tool (20). Errors are HTTP codes with a message and an optional integer code, with no code catalogue. The MCP server separates schema failures (-32602) from tool result errors that name the arguments involved (14). Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint. API writes have no idempotency keys and the OpenAPI descriptions declare delete methods as GET (13). Report calls need only `idSite`, `period` and `date`. The official clients for JavaScript, PHP and Java cover tracking, not the Reporting API (10).); Userpilot 60 (The tool count isn't published; the docs say the assistant can search hundreds of extra read-only operations on demand, which reads as dynamic loading. Without the list we give the middle band (15 of 25). Export jobs filter by date range, users, events and segments, and job lists paginate (14 of 20). A documented error reference (13 of 20). No deletes or admin through MCP by design; annotations weren't readable and no idempotency keys were found (10 of 20). The HTTP APIs have no official server-side SDK; client SDKs for web and six mobile frameworks (8 of 15). 15+14+13+10+8 = 60.)
- Transparency & trust, Matomo +15: Matomo 74 (The core and the MCP plugin are GPL v3 or later. Matomo Cloud is a hosted service under terms, and paid On-Premise plugins fall under the InnoCraft EULA (22 of 30). The Cloud terms, DPA and privacy policy agree. Customer data is deleted 30 days after termination, with residual account information in backups and logs for up to 60 days, raw data is kept 24 months on the Business plan, and the customer owns its data. The privacy policy gives no period for account data (25). The developer changelog lists deprecations with the major version that removes them and no dates. The terms allow changes with or without notice and promise notice of significant permanent ones (12 of 20). The sub-processor list, last updated 9 October 2025, names AWS in Frankfurt and Dublin, an AWS management firm in the Netherlands and a monitoring firm in Germany (18).); Userpilot 59 (A closed service with terms dated 23 April 2024 (15 of 30). The privacy policy of 11 March 2025 names a DPO and two sub-processors (AWS and Cloudflare), while the security page names AWS, Google Cloud and Stripe. The DPA is on request and no customer-data retention period is stated (14 of 30). No deprecation policy or dated API notices found (3 of 20). Sub-processors are named with addresses but not data locations, though an EU ingestion endpoint exists (10 of 20). 15+14+3+10 = 42.)
- Security & auth, Matomo +9: Matomo 71 (OAuth 2.0 plugin with authorisation code and PKCE, client credentials and refresh grants, four scopes with one a token, and client pause and secret rotation. `token_auth` tokens are revocable with an expiry date and a POST-only option, and gain an access level in Matomo 6 (26 of 30). Less 10 because the API docs present `token_auth` as a URL parameter (16). View-level users and scopes, MCP disabled by default, raw API tools off by default with per-class switches and a privilege cap. No confirmation step in the server (16 of 20). Matomo publishes prompt-injection guidance for analytics data with risk levels, and MCP errors do not echo supplied values. No filtering of tool output was found (11 of 15). Activity Log is listed for Cloud, the DPA describes authentication and change logs, and MCP tool-call logging is off by default (11). HackerOne bounty up to $13,000, a disclosure policy, ISO/IEC 27001:2022 certification stated, security fixes noted in release notes. No security.txt (17).); Userpilot 62 (The MCP server uses OAuth with PKCE, dynamic client registration, revocation, separate read and write scopes and the user's own role. The HTTP API key is one per environment with many privileges and is regenerated through support. Averaged over both surfaces (22 of 30). Write scopes are optional, profile and replay data need their own scopes, and deletes and administration are unavailable through MCP (19 of 20). Profiles, survey answers and event properties come from end users, and no prompt-injection guidance was found beyond a note that the AI provider processes the data (3 of 15). Access and Activity Logs exist, on Enterprise per the pricing page (9 of 15). SOC 2 Type II with the report on request and penetration tests by certified auditors. No security.txt, disclosure policy or bug bounty (9 of 20). 22+19+3+9+9 = 62.)