Tideways
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Tideways GmbH · tideways.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Tideways at a glance
- Vendor
- Tideways GmbH
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- In the EU; pages mention Germany source, captured 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates Tideways 3/5, the mean of 6 judges. Tideways is a PHP-focused application monitoring, profiling and error tracking service from Tideways GmbH in Bonn. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tideways is a PHP-focused application monitoring, profiling and error tracking service from Tideways GmbH in Bonn. It scores highest on data controls at 7-8, sovereignty at 8 and pricing transparency at 8. A daemon on the customer's own infrastructure filters personal data before transmission, cookies, IP addresses and user agents are never stored, and monitoring data is hosted with SysEleven in Berlin under a published German-law data processing agreement. Tier tables in euros and dollars price Team at 109€ /month and Business at 219€ /month at 15 million requests, with a soft quota, no overage pricing and a 14-day trial requiring no credit card. The lowest cluster is error tracking at 4, because the vendor states its focus is PHP applications only. Performance tracing spans 6-7 and workflow and integrations 5-6: deep code-level profiling, but no public information on OpenTelemetry, real user monitoring or issue tracker integrations. Security and reliability spans 5-6 around a public status page and a 99 percent annual availability warranty; the judges find no public information on vendor-level certification, audit logs or encryption at rest.
Speaks for it
- A daemon on the customer's own infrastructure filters personal data before transmission, and cookies, IP addresses and user agents are never stored.
- Monitoring and profiling data is hosted with SysEleven in Berlin under a published data processing agreement governed by German law, with subprocessors listed.
- Published tier tables in euros and dollars run from 5 million to 1 billion requests, with no overage pricing and an automatic upgrade only after two consecutive months over.
- Code-level profiling reaches per-function duration and memory metrics, with slow-SQL stacktraces pointing to the PHP file and line.
- A 14-day trial is offered with no credit card or phone number required.
Held against it
- Error tracking is documented for PHP only, and we found no public information on SDKs for other languages or mobile platforms.
- We found no public information on issue tracker integrations such as Jira, GitHub or GitLab.
- We found no public information on OpenTelemetry ingestion, real user monitoring or Web Vitals.
- We found no public information on audit logs, encryption at rest or a vendor-level certification, as the ISO 27001 named covers the datacenter.
- Single sign-on with Azure Active Directory sits in the Enterprise plan, which is priced as custom.
Best for
- You run PHP applications such as Laravel or Shopware and want backend error tracking with deep code-level profiling.
- Your compliance review values data minimisation before transmission, a German-law data processing agreement and named hosting in Berlin.
- You want a predictable bill from published tier prices, with a soft quota and no overage pricing.
- You manage several client projects and want per-team separation, with additional teams at 25€.
Avoid if
- You run JavaScript, Python, Java, Go or mobile services — the vendor states its focus is on PHP applications only.
- You need single sign-on and unlimited historical data at a published price — both sit in the custom-priced Enterprise plan.
- You need tighter availability terms than the warranted 99 percent annual availability with maintenance windows of up to three hours a month.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 2 of 5 |
| APM, tracing & profiling | 3 of 5 |
| Alerting, integrations & developer workflow | 2.5 of 5 |
| Data scrubbing, retention & volume control | 4 of 5 |
| Access control, security & the vendor's reliability | 3 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 4 of 5 |
Error capture, grouping & triage
Show reasoningHide reasoning
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The Agency Tech Lead
PHP exceptions are collected automatically with full stack traces, grouped by stack trace, worked through a resolve-or-ignore workflow, and notified when new, re-opened or re-appeared after a release, with optional anonymised code context around frames. The stated focus is PHP applications only, and we found no public information on SDKs for JavaScript or other platforms, on issue search and filters, or on custom fingerprints. For our Laravel and Shopware servers this covers the backend well, but browser errors would need a second tool. 4 15 5
The SaaS CTO
Automatic grouping by stack trace, resolve/ignore states, notifications when an error re-appears after a release, and anonymized code context around frames are all documented — a real issue lifecycle, but for PHP only, and the vendor states that focus itself. Issue search and filters, custom fingerprints and commit attribution are not described, so for my Go, Python and TypeScript services this stays narrow. 4 5 15
The Mobile Team Lead
For a team like mine the first question is mobile, and the vendor states its focus is PHP applications only — we found no public information on iOS, Android or Flutter SDKs, symbolication, or crash-free users per release. Within PHP the workflow is real: errors arrive with full stack traces and optional anonymized code context, are grouped by stack trace into aggregates with a resolve-or-ignore workflow, and notifications fire for errors that are new, re-opened or re-appeared after a release. 4 5 15
The Site Reliability Engineer
Errors and exceptions arrive with full stack traces, are grouped by stack trace into aggregates, and carry a resolve-or-ignore workflow with notifications when an error is new, re-opened or re-appeared after a release; optional code context around traces is collected with comments and strings anonymized. All of this is documented for PHP only — the vendor states its focus is PHP applications — and we found no public information on issue search and filters, custom fingerprints, or user context and breadcrumbs. 4 5 15
The Data Protection Officer
Error tracking is documented for a single platform: the vendor states its focus is on PHP applications only. Within that scope, errors arrive with full stacktraces and optional code context whose comments and strings are automatically anonymized, are grouped into aggregates by identical stacktrace, carry a resolve-or-ignore workflow, and trigger notifications on new, re-opened and re-appeared-after-release errors, with before-and-after deployment comparison. We found no public information on SDKs for other languages, custom fingerprinting, or search over issues. 4 5 15
The Skeptic
Errors arrive with full stack traces, automatic grouping into aggregates, a resolve/ignore workflow and notifications for new, re-opened and re-appeared-after-release cases, plus optional code context around traces — but the captured pages state "Tideways focus is on PHP applications only", so a team running JavaScript, Python, Java or mobile gets none of this. We found no public information on breadcrumbs, per-user context, custom fingerprinting or search over issues. 4 15 5
APM, tracing & profiling
Show reasoningHide reasoning
How this is scored
How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
0 — No performance data of any kind; errors only.
3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.
5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.
8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.
10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.
The Agency Tech Lead
Per-minute graphs with 95th percentile response times per transaction, slow SQL logged with stack traces pointing to the PHP file and line plus the visited URL and controller, N+1 detection, background worker and cronjob coverage, and a callgraph profiler with per-function duration and memory metrics give me the slow-page picture before a client calls. Trace collection is controllable through traces-per-minute limits, tracepoint quotas and manual triggers from the Chrome extension or CLI, with an overhead of 1-5% stated. We found no public information on OpenTelemetry ingestion, real user monitoring or Core Web Vitals, or host and container metrics beside the traces. 5 3 2 7
The SaaS CTO
Percentile response times with full histograms, slow SQL with N+1 detection, background workers and cronjobs, distributed profiling on the Business plan, and genuinely deep code-level profiling with timeline, call graph and flame graph views are documented. I found no public information on OpenTelemetry ingestion, real user monitoring or Web Vitals, and the link from a slow trace to its error is not described — that is the trace I want from browser click to database call, so it caps the level for me. 2 3 5 7
The Mobile Team Lead
Transaction response times are stored as full histograms with the 95% response time shown per minute, slow SQL queries are logged with stack traces pointing to file and line, N+1 patterns are detected, cronjobs and background workers are monitored, and the callgraph, timeline and flame graph profilers give function-level profiling with distributed profiling on the Business plan. We found no public information on OpenTelemetry ingestion, real-user monitoring or Web Vitals, or host metrics beside the traces. 2 3 5 7
The Site Reliability Engineer
Transaction timings come with 95% response time and full histograms, slow SQL queries with stack traces pointing to the PHP file and line, repeated-query detection, background workers and cronjobs, and three code-level visualisations (Timeline, Flame Graph, Call Graph) with per-function duration and memory metrics — profiling well beyond a basic response-time view, with an overhead of just 1-5% claimed. Distributed profiling sits in the Business plan, and we found no public information on OpenTelemetry ingestion, real user monitoring or Web Vitals, or host and container metrics beside the traces. 2 3 5 7
The Data Protection Officer
Transaction timings with 95th percentile per minute, slow SQL logging with stacktraces pointing to file and line, N+1 detection, background worker and cronjob analysis, automatic layer detection across PHP, SQL, HTTP and Redis, and code-level callgraph profiling with duration and memory per function are all documented, with distributed profiling in the Business plan and tracepoints plus per-minute trace quotas controlling collection. We found no public information on OpenTelemetry ingestion, real user monitoring or Web Vitals, or host and container metrics beside the traces. 2 3 5 7
The Skeptic
Per-minute response times with the 95th percentile per transaction, slow-SQL logging with stack traces to the PHP file and line, N+1 detection, cronjob and background-worker monitoring, and genuine code-level callgraph profiling with function-level self and total times are all documented, with distributed profiling in the Business plan. We found no public information on OpenTelemetry ingestion, real user monitoring or Web Vitals, host and container metrics, or anomaly detection — so the signal set stops short of the top levels. 3 5 2 7
Alerting, integrations & developer workflow
Show reasoningHide reasoning
How this is scored
How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.
0 — No notifications and no integrations; errors are only visible by logging in.
3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.
5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.
8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.
10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.
The Agency Tech Lead
Alerts reach email, Slack, Microsoft Teams, webhooks and the on-call tools PagerDuty, Opsgenie and Splunk On-Call, triggered by new, re-opened and re-appeared errors and by response times or error rates exceeding normal levels, plus a weekly performance report, an API, and multi-team structures with extra teams at a stated price — per-team separation is exactly how an agency wants alert routing. The Chrome extension and CLI round out the developer tooling. We found no public information on issue tracker integrations such as Jira, GitHub or GitLab, and the coding-agent analysis of shared traces names no model or data handling. 7 4 5 1 3
The SaaS CTO
Alerting on response times and error rates, notifications through email, Slack, Teams, PagerDuty, Opsgenie and webhooks, a weekly report, a CLI wired into build scripts and deployments, and a documented API cover the daily loop well. I found no public information on two-way issue tracker sync with Jira or Linear, commit links that route an error to the owning team, or any named model behind the coding-agent trace analysis. 1 3 4 5 7
The Mobile Team Lead
Alerts cover response times, error rates and error states, notifications reach email, Slack, Microsoft Teams, webhooks, PagerDuty and Opsgenie, and a weekly performance report plus a CLI and Chrome extension round out the workflow; release regressions surface through before-and-after deployment comparison. We found no public information on issue tracker integrations with Jira, GitLab or Linear, and the AI angle is limited to sharing traces with coding agents without any model named. 3 4 5 7 12
The Site Reliability Engineer
Notifications reach email, Slack and Microsoft Teams, with PagerDuty, Opsgenie, Splunk On-Call and webhooks as advanced integrations, and alerts fire on response times and error rates as well as new, re-opened and post-release errors; an API, a CLI and Chrome extension for triggering traces, and a weekly performance report round it out. We found no public information on issue tracker integrations such as Jira, GitHub or GitLab, so the loop into where the fix gets tracked is not evidenced. 3 4 5 7 12
The Data Protection Officer
Notifications reach email, Slack, Microsoft Teams, PagerDuty, Opsgenie, Splunk On-Call and webhooks, triggered by new, re-opened and re-appeared errors and by response-time and error-rate levels, alongside a weekly performance report, a documented API, and a CLI and Chrome extension for triggering traces manually. We found no public information on issue tracker integrations such as Jira, GitHub or GitLab, and the only AI-adjacent capability — sharing traces so coding agents can analyse them — names no model and documents no data handling. 1 3 4 5 7 12
The Skeptic
Notifications reach email, Slack, Microsoft Teams, PagerDuty, Opsgenie, Splunk On-Call and webhooks, with alerts on response times and error rates, a weekly report, an API and a CLI — a broad routing surface. We found no public information on issue tracker integrations such as Jira, GitHub or GitLab, and single sign-on with Azure Active Directory sits in the Enterprise plan, which is priced as custom. 7 4 5 12
Data scrubbing, retention & volume control
Show reasoningHide reasoning
How this is scored
What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.
0 — No control over what is captured, no retention period stated, no limit on volume.
3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.
5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.
8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.
10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.
The Agency Tech Lead
A daemon on our own infrastructure filters before anything leaves — SQL literals removed, sensitive URL parameters such as email, name, access token and API key stripped, cookies, IP addresses and user agents never stored — and a lockdown mode reduces error messages and SQL or HTTP spans to whitelisted summaries, with personal data off by default. Retention and lookback are stated per plan with automatic purging, requests can be excluded via UI or API so they never count toward the limit, and the request limit is a soft quota with no overage pricing and automatic upgrade only after two consecutive months over — a cron storm throwing the same exception a million times will not blow up the invoice. We found no public information on custom scrubbing rules, per-project retention settings, or deletion of individual events. 9 7 12 13
The SaaS CTO
This is the strongest part: a daemon on the customer's own infrastructure strips SQL literals and sensitive URL parameters, lockdown mode removes error messages entirely unless whitelisted, no cookies, IP addresses or user agents are stored, and personal data stays off by default with privacy features opt-in. The request quota is soft with no overage pricing and a stated auto-upgrade after two consecutive months over, retention per plan with automatic purging, deletion after termination, request exclusion before events count, and export via API are all stated; I found no public information on a self-hosted edition. 7 9 12 14
The Mobile Team Lead
Personal data is off by default: a daemon on the customer's own servers strips SQL literals and sensitive URL parameters, never stores cookies, IP addresses or user agents, and a lockdown mode removes error messages entirely and reduces SQL and HTTP spans to whitelisted summaries. Retention is stated per plan with automatic purge, the request quota is soft with no overage pricing and an automatic upgrade only after two consecutive months over, and Data Act export and deletion terms are published — we found no public information on a self-hosted edition. 7 9 12 13
The Site Reliability Engineer
A filtering daemon runs on the customer's own infrastructure and strips personal data before anything leaves: SQL literals are removed, named sensitive URL parameters such as access token and API key are dropped, lockdown mode aggressively filters trace and error payloads, and cookies, IP addresses and user agents are never stored by default. Retention is stated per plan with automatic purging, the request limit is a soft quota with no overage pricing and an automatic plan upgrade only after two consecutive months above it, individual requests can be excluded from the count through the UI or API, and export comes as machine-readable CSV, JSON or XML. We found no public information on a self-hosted edition. 7 9 12 13
The Data Protection Officer
Data minimisation is by design: the daemon runs on the customer's own infrastructure and filters before transmission, personal data is not stored by default, cookies, IP addresses and user agents are never stored from users triggering errors, SQL literals are parsed out, sensitive URL parameters such as email and access tokens are removed, and a lockdown mode strips error messages and span details to whitelisted summaries. Retention is stated per plan with automatic purging, the request limit is a soft quota with no overage pricing and automatic upgrade only after two consecutive months over, requests can be excluded before they count, and export arrives via API and machine-readable archives. We found no public information on deletion of individual events, configurable custom scrubbing rule sets, or a self-hosted edition. 4 7 9 12
The Skeptic
This part they got right: a daemon on the customer's own servers filters personal data before anything leaves, sensitive URL parameters like email, ip and access token are removed, SQL literals are scrubbed, and a lockdown mode strips error messages and span details entirely, with no cookies, IP addresses or user agents stored by default. Volume is a soft request quota — recording continues past it with "no overage pricing", and auto-upgrade only after two consecutive months over — with plan retention published and machine-readable export by API documented. We found no public information on a self-hosted edition or on deleting individual events or users. 9 7 12 13 14
Access control, security & the vendor's reliability
Show reasoningHide reasoning
How this is scored
Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).
0 — Nothing on access control, security or the vendor's own availability.
3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.
5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.
8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.
10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.
The Agency Tech Lead
Projects and multi-team structures with invited users exist, SSO with Azure Active Directory comes with the Enterprise plan, transmission is encrypted, the datacenter is certified ISO 27001 with BSI Basic Protection, and there is a public status page with incident history, a 90-day ingest uptime of 99.94 percent and a warranted annual availability of 99 percent. We found no public information on two-factor authentication for user accounts, audit logs, encryption at rest, SLA credits, or a vulnerability disclosure programme — the two-factor statement in the agreement covers Tideways' internal systems — and no statement of how ingestion behaves during a vendor outage. 7 8 10 12 14
The SaaS CTO
SSO with Azure AD on the Enterprise plan, multi-team support, encryption in transit, a published DPA with technical and organisational measures in an annex, a public status page with incident history and 99.9x percent uptime figures, and a 99% annual availability warranty give me most of an audit file. I found no public information on SAML or SCIM more broadly, audit logs, an ISO 27001 or SOC 2 certificate for Tideways itself rather than its datacenter, or how the SDK behaves during a vendor outage. 8 10 12 14
The Mobile Team Lead
There is a public status page on Atlassian Statuspage showing 100% ecosystem uptime and 99.94% ingest uptime over ninety days with incident history, a warranted availability of 99% on an annual basis, and a production datacenter certified ISO 27001 with BSI Basic Protection. Single sign-on with Azure Active Directory is an Enterprise feature and multi-team support exists, but we found no public information on audit logs, SCIM provisioning, a vulnerability disclosure programme, or SDK behaviour during a vendor outage. 7 10 12 14
The Site Reliability Engineer
There is a public status page with a 90-day window showing 100% uptime for the ecosystem and 99.94% uptime on ingest plus incident history, a 99% annual availability warranty with a maintenance window capped at three hours a month, encryption in transit, a security page, and a published data processing agreement with technical and organisational measures in an annex. Single sign-on with Azure Active Directory comes with Enterprise and multi-team support with Business, but we found no public information on customer-side two-factor authentication, audit logs, SCIM provisioning, an SLA with credits, or how the agent behaves when Tideways itself is down. 7 8 10 12 14
The Data Protection Officer
A public status page shows 90-day uptime per component with an incident history, the terms warrant 99% availability on an annual basis with defined maintenance windows, the data processing agreement documents technical and organisational measures in an annex, the datacenter is certified ISO 27001 with BSI Basic Protection, and single sign-on arrives with Azure Active Directory on the Enterprise plan. We found no public information on encryption at rest for stored monitoring data, two-factor authentication and roles for product accounts, audit logs, SCIM, a vendor-level certification with its scope, or a vulnerability disclosure policy. 7 8 10 12 14
The Skeptic
A public status page shows 99.94% ingest uptime over 90 days with incident history, and the terms warrant 99% annual availability alongside a nightly possible maintenance window of up to three hours a month. But the only ISO 27001 named covers the external datacenter rather than the vendor itself, the documented two-factor authentication covers the vendor's own systems rather than customer accounts, and we found no public information on audit logs, SOC 2, SLA credits or a vulnerability disclosure policy. 10 12 14 8 7
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Tech Lead
The contracting entity is Tideways GmbH registered at the court in Bonn, all monitoring, profiling and account data sits with SysEleven in Berlin, and the published data processing agreement states processing in the EU or EEA as a matter of principle under German law, with monitoring and profiling data only ever processed by the hosting company SysEleven. Subprocessors are listed with addresses and transfer bases, and the US ones for support, email and payment carry standard contractual clauses or the Data Privacy Framework. That is a sovereign core chain; we found no public information on a certification for Tideways itself beyond the datacenter's, and several support and payment subprocessors sit in the USA with safeguards rather than in Europe. 7 14 13 11
The SaaS CTO
German GmbH registered in Bonn, all account, monitoring and profiling data hosted at SysEleven in Berlin, a published Article 28 DPA under German law, and a subprocessor list with full addresses and stated transfer bases for the US ones — this is exactly the chain my enterprise customers ask about. The US subprocessors for support, email delivery and payment carry standard contractual clauses or the Data Privacy Framework; I found no public information on a self-hosted edition, which is the only step beyond this level. 7 11 13 14
The Mobile Team Lead
The contracting entity is Tideways GmbH in Bonn registered at the Amtsgericht Bonn, and all account, monitoring and profiling data is hosted with SysEleven in Berlin, with monitoring data processed only by that hosting company. A GDPR Article 28 data processing agreement under German law is published, subcontractors are listed with locations and transfer bases, and third-country transfers require adequacy, standard contractual clauses or certifications — though several administrative subprocessors for support, email and payment sit in the US behind such safeguards. 7 9 11 13 14
The Site Reliability Engineer
Tideways GmbH of Bonn is the contracting entity, all account, monitoring and profiling data is hosted in SysEleven's data centres in Berlin, and profiling, monitoring and exception tracking data is stated to be processed only by the hosting company SysEleven; the published Article 28 data processing agreement is governed by German law, and the subprocessor list names each processor with its location and transfer safeguard (standard contractual clauses, the Data Privacy Framework or adequacy decisions). The stated ISO 27001 with BSI Basic Protection belongs to the data centre rather than the vendor, and we found no vendor-level certification claim. 7 9 11 14 15
The Data Protection Officer
The contracting entity is Tideways GmbH in Bonn with a German register number and VAT identification, all account, monitoring and profiling data is hosted by SysEleven GmbH in Berlin, and monitoring data is stated to be processed only with that hosting company, with processing as a principle in the EU or EEA. A GDPR Article 28 data processing agreement governed by German law is published, listing subprocessors with their locations and transfer bases — Google Ireland and Stripe Ireland, ChartMogul in Berlin and Plausible in Estonia alongside the US providers HelpScout, Postmark, Recurly, Zoom and Notion under standard contractual clauses or the Data Privacy Framework. The stated certifications cover the datacenter rather than the vendor itself, and parts of the support, email and payment chain run through US providers, which keeps this short of sovereign end to end. 7 9 11 13 14
The Skeptic
German entity and contracting party (Tideways GmbH, Bonn, Amtsgericht Bonn HRB 22127), hosting on named infrastructure in SysEleven's Berlin data centers where all account, monitoring and profiling data is stored, a published data processing agreement under German law, and a subprocessor list with locations and transfer safeguards. Profiling and monitoring data is "only ever processed with our hosting company SysEleven GmbH"; the US subprocessors in the list touch help-desk, email delivery, payment and video calls, each with standard contractual clauses or the EU-U.S. Data Privacy Framework named, and the ISO 27001 stated is the datacenter's certification rather than the vendor's own. 7 9 11 14 13
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.
5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".
8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.
10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.
The Agency Tech Lead
The pricing page publishes a tier table in euros and dollars from 5 million up to a billion requests per month, per-plan limits for traces per minute, spans per trace, lookback and historical data, a definition of what counts as a request, prices excluding VAT, 10% off for yearly payment, extra teams at 25€, and a 14-day trial without credit card. Quota behaviour is explicit: a soft limit, recording continues, no overage pricing, automatic upgrade only after two consecutive months over, plus one-day termination notice to the end of the billing period. Enterprise is priced as custom, and we found no public information on per-seat costs, so the exact annual price for my fourteen developers is not fully computable. 7 12 2
The SaaS CTO
Full tier tables in euros and dollars from 5 million to a billion requests, each plan's limits spelled out, no overage pricing at all, a soft quota with the auto-upgrade rule after two consecutive months over, 10% off yearly, VAT stated as excluded, 25€ per additional team, a priced onboarding workshop and one-day termination notice make the annual cost computable from public pages. The Enterprise plan with SSO and unlimited history is custom, so the top end stays a quote, and I found no public information on per-seat pricing. 7 12
The Mobile Team Lead
The pricing page publishes Team and Business prices in euros and dollars across request volumes from 5 million to 1 billion, states there is no overage pricing because the request limit is a soft quota, prices add-ons such as the onboarding workshop at 249€ / $249 and additional teams at 25€, and states all prices exclude VAT with 10% off for yearly payment. Termination terms, the early termination fee and the auto-upgrade rule are in the published terms, while Enterprise pricing is custom and we found no public information on per-seat user pricing. 7 12
The Site Reliability Engineer
The tier table prices every volume from 5 million to 1 billion monthly requests in euros and dollars for Team and Business — 109€ /month for Team and 219€ /month for Business at 15 million requests — with per-plan trace, span and lookback limits, a definition of what counts as a request, extra teams at 25€ per team, 10% off yearly payment, VAT excluded, and termination on one day's notice. The quota is a soft limit with no overage pricing and an automatic upgrade only after two consecutive months above it, so an incident spike will not inflate the invoice; only the Enterprise tier above 1 billion requests is custom-priced. 7 12
The Data Protection Officer
A public tier table prices Team and Business from 5 million up to 1 billion monthly requests in both euros and dollars, defines what counts as a request, states per-plan limits for traces per minute, spans per trace, lookback and historical data, and prices add-ons — 25€ per additional team and a 249€ onboarding workshop — with 10% off yearly payment, prices excluding VAT, and one-day termination notice to the end of the billing period. There is no overage: the request limit is a soft quota, recording continues past it, and an automatic upgrade follows only after two consecutive months above the booked scope, so the annual cost is computable for every published tier; only the Enterprise tier, where single sign-on and unlimited historical data sit, is custom-priced. 7 12
The Skeptic
A public table prices Team and Business from 5 million to 1 billion monthly requests in euros and dollars, the request unit is defined precisely (every web request, API call, background script or job), quota behaviour is stated — soft limit, recording continues, auto-upgrade after two consecutive months, "no surprise invoices" with no overage pricing — and VAT excluded, an extra team at 25€, 10% off yearly payment and the early-termination-fee formula are all public. The Enterprise plan, which gates single sign-on with Azure Active Directory, unlimited historical data and priority support, is priced as custom, so the annual cost for those needs is not computable from public pages alone. 7 12
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The privacy policy discloses that system and service emails are sent via the US provider Postmark, so some customer personal data is transferred outside the EU. |
4/4 pts | 7 Report an error |
| Hosting options |
Cloud service only
unverified
Why unverified?Local collector components (Tideways Daemon, PHP Extension) do run on the customer's infrastructure, and no page explicitly states that no self-hosted/on-premises option exists. |
0/1 pts | 12 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 14 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Tideways
Is Tideways European?
Yes. whats-best.ai classifies Tideways as EU-Made.
Where does Tideways store data?
Tideways stores customer data in the EU, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 6 Nov 2026.
Does Tideways have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to Tideways?
As of 18 Nov 2026, the panel rates Sentry (3.5/5), Datadog APM & Error Tracking (3.5/5) and Dynatrace (3/5) highest among the other 19 Error Tracking & APM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is AppSignal (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Tideways alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The privacy policy discloses that system and service emails are sent via the US provider Postmark, so some customer personal data is transferred outside the EU.
- Weak sourcing — Hosting options. Local collector components (Tideways Daemon, PHP Extension) do run on the customer's infrastructure, and no page explicitly states that no self-hosted/on-premises option exists.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage tideways.com Checked 6 Nov 2026 Details →
- 2 Features page tideways.com Checked 6 Nov 2026 Details →
- 3 Features page (profiling and tracing) tideways.com Checked 6 Nov 2026 Details →
- 4 Features page (error tracking) tideways.com Checked 6 Nov 2026 Details →
- 5 Features page (monitoring and alerting) tideways.com Checked 6 Nov 2026 Details →
- 6 Documentation support.tideways.com Checked 6 Nov 2026 Details →
- 7 Pricing page tideways.com Checked 6 Nov 2026 Details →
- 8 Security / trust page tideways.com Checked 6 Nov 2026 Details →
- 9 GDPR page support.tideways.com Checked 6 Nov 2026 Details →
- 10 Public status page status.tideways.io Checked 6 Nov 2026 Details →
- 11 Legal notice tideways.com Checked 6 Nov 2026 Details →
- 12 Terms of service tideways.com Checked 6 Nov 2026 Details →
- 13 Privacy policy tideways.com Checked 6 Nov 2026 Details →
- 14 Data processing agreement (dpa) tideways.com Checked 6 Nov 2026 Details →
- 15 APM, tracing & profiling — found from sitemap tideways.com Checked 6 Nov 2026 Details →
- 16 APM, tracing & profiling — found from sitemap tideways.com Checked 6 Nov 2026 Details →