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 Site Reliability Engineer

Weighted verdict

Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Site Reliability Engineer

Panel median The Site Reliability Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Site Reliability Engineer
Error capture, grouping & triage 2 of 5 2 of 5
APM, tracing & profiling 1 of 5 1 of 5
Alerting, integrations & developer workflow 2 of 5 2 of 5
Data scrubbing, retention & volume control 2 of 5 2 of 5
Access control, security & the vendor's reliability 2 of 5 2 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 2 of 5 2 of 5

Error capture, grouping & triage

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

APM, tracing & profiling

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

Alerting, integrations & developer workflow

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

Data scrubbing, retention & volume control

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

Access control, security & the vendor's reliability

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

European sovereignty

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

Pricing transparency

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

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 →