Panel 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 TrackJS, LLC · trackjs.com

Report an error on this page Is this your product? →

Link to this page

TrackJS: AI-assisted analysis on whats-best.ai TrackJS: AI-assisted analysis on whats-best.ai (dark)

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.

TrackJS at a glance

Vendor
TrackJS, LLC
Headquarters
Incorporated in the United States source, captured 17 Nov 2026
Data hosting
Outside the EU by default source, captured 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Starting price
“Starter Great for small businesses and sites that need essential error tracking. Annualized price shown. $ 45 /month” (vendor’s words) source, captured 17 Nov 2026
Panel verdict
The AI panel rates TrackJS 2/5, the mean of 6 judges. TrackJS is a JavaScript error monitoring product whose documented agents cover the browser and Node.js. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

TrackJS alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

TrackJS is a JavaScript error monitoring product whose documented agents cover the browser and Node.js. Scoring is consistent: error tracking, workflow and integrations, security and reliability, sovereignty and pricing transparency all sit at 4, with data controls at 4 to 5. The weak point is performance tracing at 1 to 2, where the captured pages document the agent's own overhead — an 8kb script, roughly 10ms of error gathering, a non-blocking send — rather than the monitored application; we found no public information on distributed tracing, slow queries, profiling or Web Vitals, and the 1-versus-2 split turns on how much the page-view counts are worth. The Starter plan is published at $45/month, annualized price shown, with 100K monthly page views, 800K+ monthly errors, 10 days retention and unlimited users, priced on traffic rather than errors — the 15- and 30-day tiers, overage behaviour and VAT are not stated. Servers are documented in Canada and the United States under TrackJS LLC of Minneapolis; every subprocessor is named, and we found no public information on an EU data region or self-hosted edition.

Report an error

Speaks for it

  • Error tracking scores sit at 4 on browser and Node agents with source maps (TypeScript included), automatic formatting of the code behind stack traces, and a chronological telemetry timeline of network requests, console logs, user actions and navigation before each error
  • Alerting offers new-error, error-rate-increase (20 percent) and trending notifications under four statistical strategies with configurable lookback and volume settings, delivered per application to email, Slack or Microsoft Teams, with saved-filter alerts and daily email summaries
  • SAML 2.0 single sign-on covers SP- and IdP-initiated flows with five named identity providers, auto-provisioning that grants no administrator rights by default, and no additional fee — alongside a public status page and a bug bounty for pre-approved researchers
  • Data controls score 4 to 5 on retention stated per plan (10, 15 or 30 days), configurable IP anonymisation, unlimited server-side ignore rules on every plan, deletion during the term, destruction at term end, and export through the API
  • Every subprocessor is named with its country, a pre-signed data processing agreement offers EU Standard Contractual Clauses (modules 2 and 3), and the optional AI Debugger names OpenAI, ships disabled by default and strips IP addresses and usernames before transmission

Report an error

Held against it

  • Performance tracing scores sit at 1 to 2 — the captured pages document the agent's own overhead (an 8kb script, roughly 10ms of gathering) rather than application timings, and we found no public information on distributed tracing, slow queries, profiling or Web Vitals
  • Notification channels are documented as email, Slack and Microsoft Teams, and we found no public information on on-call routing such as PagerDuty or Opsgenie, issue tracker sync, webhooks, deploy hooks or a command line interface
  • We found no public information on scrubbing of passwords, tokens or card numbers in request data, on sampling, or on what happens when the volume limit is reached
  • Only the Starter plan is priced on the captured pages — the 15- and 30-day retention tiers, overage behaviour at the quota, and VAT and billing terms are not stated
  • We found no public information on two-factor authentication, audit logs, ISO 27001 or SOC 2 certification, or an SLA, and the security policy page was last modified January 19, 2019

Report an error

Best for

  • You run a JavaScript-heavy web frontend (HTML, React, Angular, Next) and need error capture with source maps and a pre-error telemetry timeline
  • You need configurable alerting to email, Slack or Microsoft Teams plus a REST data API with an official Node client for exporting errors and page views
  • You need SAML 2.0 single sign-on at no additional fee with unlimited users on the published Starter plan
  • Your governance favours short stated retention (10, 15 or 30 days), customer-controlled collection with IP anonymisation, unlimited server-side ignore rules, and a pre-signed DPA with EU Standard Contractual Clauses

Report an error

Avoid if

  • Your primary need is diagnosing application latency — performance tracing scored 1 to 2 and the captured performance pages cover the agent's own overhead rather than the application's
  • You need to standardise error tracking across backend languages or native mobile apps — the documented agents cover the browser and Node
  • You must keep error data within the EU — hosting is documented in Canada and the United States under TrackJS LLC of Minneapolis, and we found no public information on an EU data region or a self-hosted edition
  • You need a predictable full-year cost for growing traffic — only the Starter plan is priced, and we found no public information on overage rates or the behaviour at the quota

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Error capture, grouping & triage

Show 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.

Report an error

The Agency Tech Lead

This is a browser-and-Node product, not a full-stack tracker: the documented agent installs on HTML, React, Angular, Node and Next with source maps, automatic formatting of the code behind stack traces, and a chronological telemetry timeline of network requests, console logs and user interactions before each error. The pages describe one-click filtering and search without a query language, but I found no public information on SDKs for PHP or other backend platforms, custom fingerprints, issue states or release tracking. 1 4 8 9

Report an error

The SaaS CTO

The browser and Node.js agents are documented in real depth: sourcemaps showing the original commented source, a chronological timeline of network requests, user interactions, console logs and navigation before each error, and one-click search and filtering. We found no public information on grouping mechanics, resolved or regressed issue states, releases and suspect commits, or agents for backend languages like Go or Python — solid frontend triage, thin backend coverage. 1 8 9

Report an error

The Mobile Team Lead

For my shop this is a web-and-Node product: the documented agents cover the browser and Node.js with source maps (TypeScript included), a chronological telemetry timeline of network requests, user interactions, console logs and navigation events, one-click filtering and unlimited server-side ignore rules. We found no public information on native iOS, Android or Flutter SDKs, and nothing on issue states like resolved or regressed, release and deploy tracking, or crash-free users and sessions. Solid for a web storefront, but nothing in the captured pages covers the native side of my apps. 1 4 8 9

Report an error

The Site Reliability Engineer

The browser and Node agents deliver stack traces with source maps, automatic retrieval and formatting of the referenced code, a telemetry timeline of network requests, console logs and user actions, plus unlimited server-side ignore rules — a good fit for a JavaScript-heavy frontend. The captured pages cover JavaScript platforms only, and I found no public information on SDKs for Java, Python,.NET or mobile, on issue states such as resolved or regressed, or on release and deploy tracking. Fine for our web team; not something I would standardise the whole platform on. 1 8 9

Report an error

The Data Protection Officer

A browser agent and a Node agent are documented, with stack traces automatically formatted, source maps including TypeScript sources, and a telemetry timeline of network requests, console logs and navigation events before each error; error filtering and searching without a query language is also described. We found no public information on SDKs beyond web and Node, on issue states such as resolved or regressed, on custom grouping fingerprints, or on release and deploy tracking. 1 8 9

Report an error

The Skeptic

Browser and Node agents are documented with source maps (TypeScript included), automatic formatting of the code behind each stack trace, a telemetry timeline of network requests, user actions, console logs and navigation, custom context and error manipulation at install, and search and one-click filters over errors. What the captured pages do not show: issue states, regression handling, release and deploy tracking, custom fingerprints, or any platform beyond JavaScript in the browser and Node — fine if your estate is the browser, thin otherwise. 1 7 8 9

Report an error

APM, tracing & profiling

Show 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.

Report an error

The Agency Tech Lead

The performance documentation I read covers the agent's own overhead — roughly an 8kb script, about 10ms of telemetry gathering and a non-blocking ~100ms transmission — plus a page-view beacon and page-view counts by day. I found no public information on endpoint timings, percentiles, slow-query or N+1 detection, distributed tracing, profiling or Web Vitals. 5 7

Report an error

The SaaS CTO

The performance documentation covers the agent's own cost — roughly 8kb of script, about 10ms of telemetry gathering, a non-blocking transmission of around 100ms — plus a page-view beacon for traffic counts. We found no public information on transaction timings, distributed tracing, slow query detection, profiling or OpenTelemetry ingestion, so there is no trace from a browser click to a slow database call three services down. 5 7

Report an error

The Mobile Team Lead

The performance pages describe the agent's own cost to my page — an eight-kilobyte script, roughly ten milliseconds of error gathering, non-blocking transmission — not a product capability that shows where time goes in the application. Beyond errors, the documented data are page view counts and error counts by day, hour and URL. We found no public information on transaction timings, distributed tracing, slow query analysis, profiling or real-user Web Vitals. 5 7 1

Report an error

The Site Reliability Engineer

Every performance fact I could find concerns the agent's own footprint — an 8kb script, roughly 10ms of telemetry gathering and a non-blocking send — or page-view counts exposed through the data API. I found no public information on endpoint timings, percentiles, slow queries, distributed tracing, profiling or real-user Web Vitals. When checkout latency climbs at 3am, these pages would tell me nothing about where the time went. 5 7 1

Report an error

The Data Protection Officer

The captured performance pages describe the agent's own overhead — roughly 8kb of script, about 10ms of error gathering, a non-blocking transmission of up to about 100ms — rather than the monitored application's performance, and the only application-side signal documented is page-view counting that feeds the error rate. We found no public information on response times, distributed tracing, slow queries, profiling or web vitals. 5 7 1

Report an error

The Skeptic

The captured performance documentation is about the agent's own overhead — roughly 8kb of script, up to about 10 milliseconds to gather telemetry, non-blocking transmission, a page-view beacon — not about where your application's time goes. We found no public information on endpoint timings, distributed tracing, slow queries, profiling or Web Vitals; performance monitoring appears to live in a separate product the vendor lists among its other tools (Request Metrics). 5 1 4

Report an error

Alerting, integrations & developer workflow

Show 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.

Report an error

The Agency Tech Lead

Alerting is the strong suit: four trigger strategies including an ML detector at 99.9% confidence, configurable lookback and thresholds, new-error, trending and error-rate notifications per application to email, Slack and Teams, plus a documented REST data API with a Node client and an AI Debugger whose provider (OpenAI) is named. The captured pages name no issue-tracker integration, no on-call routing beyond chat, no deploy hooks and no webhooks, and daily summaries go to email only. 1 2 6 7

Report an error

The SaaS CTO

The alerting engine is genuinely thoughtful: four strategies including an ML detector at 99.9% confidence with two required to agree, configurable lookback and volume floors, saved-filter alerts, and new, trending and error-rate notifications to email, Slack and Teams. We found no public information on PagerDuty or Opsgenie, issue tracker integrations like Jira or GitHub, webhooks or a CLI; the REST data API is documented with a Node client, and the AI Debugger names OpenAI as its model, which I give credit for. 1 2 6 7

Report an error

The Mobile Team Lead

Notifications are genuinely configurable: new-error, trending and error-rate-increase alerts chosen by four detection strategies with configurable lookback windows and minimum volumes, delivered per application to email, Slack or Microsoft Teams, plus daily email summaries and custom alerts on saved filters. The AI Debugger explains what went wrong and how to fix it, with OpenAI named as the processor and the feature disabled by default, and a REST data API with an official Node client lets us export errors and page views. We found no public information on on-call paging, issue tracker sync with Jira or GitHub, webhooks, a CLI or deploy hooks from CI. 6 7 1 2

Report an error

The Site Reliability Engineer

Alerting is genuinely considered: new errors, a 20 percent error-rate jump, trending errors and daily summaries, driven by four statistical strategies with configurable lookback windows and minimum error counts, sent to email, Slack or Microsoft Teams per application. The REST data API is well documented with a Node client, and the AI Debugger names OpenAI as its provider, off by default, with IPs and usernames stripped and a statement that OpenAI does not use the data for model training. But I found no public information on PagerDuty or Opsgenie routing, issue tracker sync, deploy hooks from CI, or webhooks — the pieces that make an on-call rotation work. 6 7 1 2

Report an error

The Data Protection Officer

Alerting is documented in depth: new-error, error-rate-increase and trending notifications governed by four statistical strategies with configurable lookback and minimum-error settings, delivered by email, Slack and Microsoft Teams per application, plus daily summary emails, and a REST data API with an official Node client. The AI Debugger is disclosed to my satisfaction, with OpenAI named, the feature off by default, and IP addresses and usernames stripped before transmission. We found no public information on issue tracker integrations, on-call routing such as PagerDuty or Opsgenie, webhooks, or a command line interface. 6 7 2

Report an error

The Skeptic

Alerting is the strong suit: new, trending and error-rate-increase notifications, four detection strategies with configurable lookback and volume settings, saved-filter notifications, per-application channel choice among Email, Slack and Microsoft Teams, a documented REST data API with a Node client, and an AI Debugger whose model provider (OpenAI) is named. We found no public information on PagerDuty, Opsgenie or other on-call routing, issue tracker integrations, webhooks, deploy hooks from CI or a CLI, and daily summaries go to email only. 6 7 1 2

Report an error

Data scrubbing, retention & volume control

Show 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.

Report an error

The Agency Tech Lead

Collection is customer-controlled end to end: IP addresses can be ignored or anonymised, onError lets you manipulate data before it is sent, unlimited server-side ignore rules drop known noise, retention is tiered at 10, 15 or 30 days, and in-term deletion, destruction at term end and export through the API are all documented. I found no public information on default scrubbing of passwords or card numbers, sampling, per-project rate limits, spike protection or a self-hosted edition. 1 2 3 7

Report an error

The SaaS CTO

Retention is stated plainly — 10, 15 or 30 days by subscription tier — IP addresses can be ignored or anonymised, unlimited server-side ignore rules ship on every plan, data is destroyed at term end, and an export API exists. We found no public information on server-side scrubbing of secrets like passwords or tokens, on sampling, or on what happens when the page-view allowance runs out — for a traffic-priced product that last one matters to the invoice. 1 2 3 7

Report an error

The Mobile Team Lead

Retention is published per tier — 10, 15 or 30 days of visitor error data — collection is customer-controlled with IP addresses ignored or anonymised on request, no cookies are placed on end users, agent options let us manipulate errors before reporting, and server-side ignore rules are unlimited on every plan. The data processing agreement covers deletion during the term and destruction when it ends, and the data API gives us export. We found no public information on sampling, rate limits, spike protection at the quota, or a self-hosted edition. 1 2 3 8

Report an error

The Site Reliability Engineer

Retention is stated per plan at 10, 15 or 30 days, IP addresses can be ignored or anonymised, data can be deleted during the term and is destroyed at expiry, and unlimited server-side ignore rules plus an onError hook let me shape what gets reported. I found no public information on scrubbing of passwords, tokens or card numbers, on sampling, rate limits, or spike protection and how a burst is billed. For a payments platform, an error flood on Black Friday with undocumented overage handling is exactly the invoice surprise I need to rule out before buying. 2 3 1 8

Report an error

The Data Protection Officer

Retention is short and stated per plan — 10, 15 or 30 days depending on subscription level — with configurable IP anonymisation, unlimited server-side ignore rules, deletion during the term, destruction at contract end, and data export through the API; the privacy policy also states that all data collection is completely controlled by the customer, which leaves payload minimisation on our side of the table. For us the decisive question is what an error body carries, and we found no public information on default scrubbing of passwords, tokens or card numbers in request data, on sampling, or on spike protection and what happens when the volume limit is reached. 2 1 3 7

Report an error

The Skeptic

Retention is short and stated per plan — 10, 15 or 30 days by subscription level — with deletion during the term and at expiry (export before it), configurable IP anonymisation, customer-controlled collection levels, no cookies on end users, unlimited server-side ignore rules on every plan, and data export through the API. What I could not find: how secrets and request bodies are scrubbed beyond IP addresses and usernames, sampling or rate limits, what happens at the quota, or a self-hosted edition. 2 3 1 7

Report an error

Access control, security & the vendor's reliability

Show 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.

Report an error

The Agency Tech Lead

SAML 2.0 single sign-on is well documented — SP and IdP initiated, Okta, OneLogin, Azure AD, Google and Auth0, auto-provisioning, explicitly no additional fee — alongside a public status page, a vulnerability disclosure address with a bounty for pre-approved researchers, and prompt breach notification. The captured pages give no two-factor authentication, no encryption-in-transit or at-rest statement, no ISO 27001 or SOC 2, no audit logs and no SLA, and the security policy text was last modified in January 2019. 4 7 10 11

Report an error

The SaaS CTO

SAML 2.0 single sign-on is properly documented — SP and IdP initiated, Okta, Azure AD and Auth0 among others, auto-provisioning with no admin rights by default and no additional fee — alongside a status page, a vulnerability disclosure channel and a bug bounty for pre-approved researchers. We found no public information on two-factor authentication, SCIM, audit logs, ISO 27001 or SOC 2, or an SLA; the security policy page we captured was last modified January 2019. 4 10 11

Report an error

The Mobile Team Lead

SAML 2.0 single sign-on is properly documented — Okta, OneLogin, Azure AD, Google and Auth0, auto-provisioning, both login flows, and explicitly no additional fee — and there is a system status page plus a security page with vulnerability disclosure and a bug bounty for pre-approved researchers. The data processing agreement grants an independent audit at most once per rolling twelve months at the customer's cost. We found no public information on two-factor authentication, organisation roles and audit logs, ISO 27001 or SOC 2 certification, an SLA or a public incident history. 10 11 3 4

Report an error

The Site Reliability Engineer

SAML 2.0 single sign-on is properly documented — Okta, OneLogin, Azure AD, Google and Auth0, both provider- and service-initiated flows, provisioning defaults, no additional fee — and there is a public status page, a vulnerability disclosure address with bounties for pre-approved researchers, Standard Contractual Clauses and audit rights in the DPA. I found no public information on two-factor authentication, audit logs, SCIM, ISO 27001 or SOC 2 certifications, or a published SLA. The security policy page carries a last-modified date of January 2019, which for my auditors would raise questions. 11 10 4 3

Report an error

The Data Protection Officer

Single sign-on is properly documented — SAML 2.0 with both SP- and IdP-initiated flows, five named identity providers, automatic provisioning and no additional fee — alongside a security page with a vulnerability disclosure contact and a bounty for pre-approved researchers, and a system status link. We found no public information on two-factor authentication, audit logs, ISO 27001 or SOC 2 certification, encryption commitments for service data, or an SLA. The security policy we read was last modified in January 2019, which for a statutory insurer's review file is a fact in itself. 11 10 4 7

Report an error

The Skeptic

SAML 2.0 single sign-on with no additional fee, auto-provisioning that defaults to non-admin, a public status page, and a security page with a vulnerability disclosure contact plus a bug bounty for pre-approved researchers are all documented, alongside breach notification commitments and API keys visible to account owners only. We found no public information on two-factor authentication, ISO 27001 or SOC 2, audit logs, an SLA or published incident history — and the security policy page carries a last-modified date of January 19, 2019, a long shelf life for a document you lean on in an audit. 10 11 4

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Agency Tech Lead

The chain is transparent but entirely North American: TrackJS LLC of Minneapolis under Minnesota law, servers in Canada and the United States, and named subprocessors — OVH, AWS, Mailgun, OpenAI, Stripe, PostHog — every one of them in Canada or the US. A pre-signed data processing agreement with EU Standard Contractual Clauses, audit rights and OpenAI confined to an explicitly enabled feature is published, but the captured pages show no EU data region and no self-hosted edition. 2 3

Report an error

The SaaS CTO

The legal apparatus is real — a pre-signed data processing agreement with EU Standard Contractual Clauses, a DPO reachable by email, and every subprocessor named with its location — but the answer to my enterprise customers' question is Canada and the United States: OVH in Canada for hosting, AWS, Mailgun, OpenAI, Stripe and PostHog all in the US, a Minnesota LLC under Minnesota law. We found no public information on an EU data region or self-hosted option anywhere in the chain. 1 2 3

Report an error

The Mobile Team Lead

The chain is transparent: subprocessors are listed with their countries — OVH in Canada for hosting, and Amazon Web Services, Mailgun, OpenAI, Stripe and PostHog in the United States — under a pre-signed data processing agreement that applies the EU Standard Contractual Clauses, with a data protection officer reachable by email. But the contracting entity is TrackJS LLC in Minneapolis under Minnesota law, servers run in Canada and the United States, and we found no public information on a European data region or a self-hosted edition. For our Hamburg team that means every error event, and the optional OpenAI debugging flow, is processed outside the EU. 2 3 1

Report an error

The Site Reliability Engineer

TrackJS LLC of Minneapolis contracts under Minnesota law, and the captured pages place hosting in Canada and the United States — OVH in Canada, with AWS backup, Mailgun, Stripe, PostHog and the optional OpenAI processor in the US — and I found no public information on an EU data region option. To its credit, the DPA is published and pre-signed on the EU Standard Contractual Clauses with modules two and three, every subprocessor is listed with its location, and the OpenAI step is optional, disabled by default, and strips IP addresses and usernames before transmission. A carefully documented American chain, not a European one. 1 2 3

Report an error

The Data Protection Officer

TrackJS LLC contracts under Minnesota law with servers in Canada and the United States, and every subprocessor is named with its country — OVH (Canada) for hosting, AWS (US) for backups, Mailgun, Stripe, PostHog and OpenAI (US) for the optional AI feature — but the chain runs entirely through North America. We found no public information on an EU data region, an EU representative, or a self-hosted edition. The data processing agreement is pre-signed, offers Standard Contractual Clauses in modules 2 and 3 with sensitive-data safeguards in Annex I and once-yearly independent audit rights at the customer's cost — real safeguards, but accepting it means printing, signing and emailing a copy. 2 3 1

Report an error

The Skeptic

The chain is transparent but entirely North American: TrackJS LLC of Minneapolis under Minnesota law, servers in Canada and the United States, and named subprocessors — OVH in Canada for hosting, then AWS, Mailgun, OpenAI, Stripe and PostHog all in the United States. A pre-signed data processing agreement with EU Standard Contractual Clauses is published, and the AI Debugger sends sanitized data to OpenAI only when explicitly enabled — but the safeguards are paperwork, not geography; we found no public information on an EU hosting option. 2 3 1

Report an error

Pricing transparency

Show 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.

Report an error

The Agency Tech Lead

The Starter plan is concrete: $ 45 /month annualized for 100K monthly page views, 800K+ monthly errors, 10 days retention and unlimited users, with SSO explicitly carrying no additional fee and a billing model "Priced on your traffic, not your errors". But only this one plan is priced on the captured pages; the 15- and 30-day retention tiers, overage behaviour, VAT and monthly-versus-annual terms are not stated, so I cannot compute a full annual cost for a forty-site portfolio. 1 2 11

Report an error

The SaaS CTO

The Starter plan is priced openly — $45/month annualized for 800K+ monthly errors, 100K monthly page views, 10-day retention and unlimited users — with the model explained as priced on traffic rather than errors and single sign-on carrying no additional fee. We found no public information on the price or volume limits of the higher tiers, on overage costs when the allowance is exceeded, or on VAT and billing terms, so a full annual cost for my traffic is not computable from what we captured. 1 2 11

Report an error

The Mobile Team Lead

The Starter plan is public at $ 45 /month with the annualized price shown, and its limits are stated: 800K+ monthly errors, 100K monthly page views, 10 days of retention and unlimited users, with single sign-on carrying no additional fee and retention rising to 15 or 30 days on higher tiers. The captured pages give no prices for those higher tiers, no overage rate, nothing on what happens when the traffic quota is hit, and no VAT terms. I can budget the entry tier but not compute a full year's cost for a growing site from these pages alone. 1 2 11

Report an error

The Site Reliability Engineer

The Starter plan is public at $45/month with the annualized price shown, covering 100K monthly page views, 800K+ monthly errors, 10 Days data retention and unlimited users, single sign-on carries no additional fee, and a free trial is offered. Only one plan appears on the captured pricing page, and I found no public information on higher tiers, per-unit overage, the behaviour at the volume limit, VAT, or annual-versus-monthly terms. I could not compute our real annual cost from these pages alone. 1 11 2

Report an error

The Data Protection Officer

The Starter plan is published at $ 45 /month (annualized) with its volumes stated — 100K monthly page views, 800K+ monthly errors, unlimited users and 10 days retention — billing is on traffic rather than errors, and SSO carries no additional fee. We found no public information on prices for the 15- and 30-day retention levels, on overage rates or the behaviour at the quota, or on VAT and billing terms. 1 2 11

Report an error

The Skeptic

The Starter plan is public at $ 45 /month (annualized price shown) with 100K monthly page views, 800K+ monthly errors, unlimited users and 10 days retention, pricing is on traffic rather than errors, SSO carries no additional fee, and a free trial exists. That is the only price captured: the tiers with 15 or 30 days retention are unpriced, and overage per page view, whether the quota caps or bills, VAT, and the difference between monthly and annual terms are not stated — so I cannot compute the second year, let alone the first busy Monday. 1 11 2

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Outside the EU 0/4 pts 2 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

Concluding the DPA requires printing, signing and emailing a copy rather than a fully automated online acceptance.

1/1 pts 3 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about TrackJS

Is TrackJS European?

Not determined: the vendor’s pages as captured do not say where TrackJS is based. Its vendor, TrackJS, LLC, is incorporated in the United States, per the vendor’s page captured 17 Nov 2026.

Where does TrackJS store data?

TrackJS stores customer data outside the EU by default, per the vendor’s page captured 17 Nov 2026.

Does TrackJS have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

What are the best alternatives to TrackJS?

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 Tideways (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: TrackJS alternatives.

Where this could be wrong

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.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page trackjs.com Checked 17 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage trackjs.com Checked 17 Nov 2026 Details →
  3. 3 Data processing agreement (dpa) — found from the homepage trackjs.com Checked 17 Nov 2026 Details →
  4. 4 Error capture, grouping & triage — found from sitemap trackjs.com Checked 17 Nov 2026 Details →
  5. 5 APM, tracing & profiling — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →
  6. 6 Alerting, integrations & developer workflow — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →
  7. 7 Alerting, integrations & developer workflow — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →
  8. 8 Data scrubbing, retention & volume control — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →
  9. 9 Data scrubbing, retention & volume control — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →
  10. 10 Access control, security & the vendor's reliability — found from sitemap trackjs.com Checked 17 Nov 2026 Details →
  11. 11 Access control, security & the vendor's reliability — found from sitemap docs.trackjs.com Checked 17 Nov 2026 Details →