Rollbar
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Rollbar, Inc. · rollbar.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.
Rollbar at a glance
- Vendor
- Rollbar, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Outside the EU by default source, captured 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Starting price
- “Plans starting at $0. Get a 14-day free trial to see how Rollbar fits your workflow.” (vendor’s words) source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates Rollbar 2.5/5, the mean of 6 judges. Rollbar is an error monitoring suite, and that is where it is strongest: error tracking and workflow and integrations both score in the 6-7 band, on SDKs for JavaScript, Python, PHP, Ruby, Go, Apple and.NET, grouping with reversible merging, and two-way Jira sync. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 9 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Rollbar is an error monitoring suite, and that is where it is strongest: error tracking and workflow and integrations both score in the 6-7 band, on SDKs for JavaScript, Python, PHP, Ruby, Go, Apple and.NET, grouping with reversible merging, and two-way Jira sync. Security and reliability scores run 7-8, on SOC 2 Type I and II, ISO 27001 scoped to the production environment, and a public status page with per-component uptime. The weak point is performance tracing, scored 0-2 — we found no public information on distributed tracing, profiling or endpoint timings; the spread is one of degree, and no other criterion split by more than a point. Sovereignty scores 3-4: Rollbar, Inc. is the contracting entity, controlled from California, primary data center on Google Cloud in Iowa; the privacy policy allows storage in the United States and locations around the world, and we found no public information on an EU data region. Pricing transparency holds at 4: volumes and overage behaviour are public, but the captured pricing page gives no dollar figure for Essentials or Advanced.
Speaks for it
- Error tracking is well evidenced across server, client and mobile SDKs, with source maps, ProGuard and dSYM symbolication and stack traces carrying local variable values.
- Alerts reach Slack, Teams, email, PagerDuty and Opsgenie, and the Jira integration syncs both ways with rules like reopening a ticket on reactivation.
- Volume and retention control is concrete: stop-at-limit on by default, dollar-capped overage budgets, on-demand events billed at the standard plan rate, and retention configurable from 7 to 180 days on paid plans.
- The compliance trail is deep: SOC 2 Type I and II, ISO 27001 scoped to the production environment, annual third-party penetration tests, SAML SSO and SCIM provisioning.
- The Resolve agent applies a fix in an isolated environment, runs your tests and opens a pull request.
Held against it
- Performance tracing scores sit at 0-2; we found no public information on distributed tracing, OpenTelemetry ingestion, profiling or endpoint timings.
- The captured pricing page gives no dollar figure for the Essentials or Advanced plans, so a real annual cost cannot be computed from public pages.
- Scrubbing is documented only as client-side filtering; we found no public information on server-side scrubbing rules, IP anonymisation or sampling.
- Rollbar, Inc. is the contracting entity, controlled from California with the primary data center on Google Cloud in Iowa, and we found no public information on an EU data region or on self-hosting of the error platform itself.
- The documentation states items cannot be split apart through the web app or the API, and we found no public information on crash-free sessions or users.
Best for
- You need production error monitoring across web and mobile, with deploy tracking, telemetry and a stated occurrence-to-alert latency under three seconds.
- Your workflow runs through Jira, GitHub or PagerDuty and you want bidirectional ticket sync, commit-linked errors and deploy reporting from CI tools.
- You need tight control of event volume and cost: per-token rate limits that take effect immediately, stop-at-limit on by default, and events dropped by rate limits never billed.
- You must pass security reviews: SOC 2 Type I and II, ISO 27001 scoped to the production environment, and SAML SSO with SCIM provisioning are documented, with SAML on the Advanced and Enterprise plans.
Avoid if
- You need performance monitoring — transaction timings, distributed tracing, profiling or OpenTelemetry — rather than error tracking; the vendor's own description enumerates the suite as error monitoring, session replay, root-cause analysis, alerting and analytics.
- You require an EU data region or a European contracting chain; the privacy policy allows storage in the United States and locations around the world, and we found no public information on an EU data region.
- You must budget precisely before committing; the captured pricing page shows a dollar figure only for the $0 monthly free tier, Enterprise is custom pricing, and we found no public information on the per-event overage rate or VAT treatment.
- Your mobile team gates store rollouts on crash-free sessions or users per release; we found no public information on those metrics, and the documentation states items cannot be split apart once grouped.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3.5 of 5 |
| APM, tracing & profiling | 0.5 of 5 |
| Alerting, integrations & developer workflow | 3.5 of 5 |
| Data scrubbing, retention & volume control | 3 of 5 |
| Access control, security & the vendor's reliability | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2 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
For my stack the essentials are documented: PHP sits among the primary SDKs alongside JavaScript, Python, Ruby, Go and.NET, stack traces carry request params and local variable values, and symbolication covers source maps, ProGuard and dSYM. Grouping is unusually explicit — machine-learning automation plus custom fingerprinting rules that are always evaluated first, reversible merging, and RQL search over items and custom data — and each error links the commit, the deploy and the developer. The documentation itself states items cannot be split, and crash-free sessions and users are not described, which holds it below the top level. 2 5 7 13 14 17
The SaaS CTO
The documented SDK set covers my world — JavaScript, Python, PHP, Ruby, Go and.NET are named primary SDKs, with source maps, ProGuard, iOS dSYM and Flutter symbol files, local variable values in the traces, deploy tracking, and grouping that combines a machine-learning engine with custom fingerprints and reversible merges. The documentation itself states items cannot be split through the web app or the API, and we found no public information on crash-free users or sessions, which is what keeps this below the top tier. 2 5 7 13 14
The Mobile Team Lead
Grouping is genuinely strong for a release-driven team like mine: automatic machine-learning grouping, custom fingerprints evaluated first, reversible merging, local variable values in the trace context, and symbolication files for iOS dSYM, ProGuard and Flutter all documented, alongside version tracking and deploy analysis with blame showing who last touched the line. What I could not find anywhere is crash-free users or sessions per release, which is exactly what I use to halt a bad store rollout, and the documentation itself states items cannot be split apart once grouped, which makes an over-grouped release crash painful to untangle. 2 5 6 7 13
The Site Reliability Engineer
Server, client and mobile SDKs are documented with source maps, ProGuard and dSYM symbolication, grouping combines an automatic engine with custom fingerprinting and a reversible merge, and every error shows the code line, deploy, last committer, local variable values and telemetry. We found no public information on crash-free sessions and users, and the documentation itself states items cannot be split. 2 5 7 13 14
The Data Protection Officer
SDKs are documented for server, client and mobile (JavaScript, Python, PHP, Ruby, Go, Apple,.NET plus community SDKs), with stack traces, request and custom params, local variable values, source maps, symbolication and ProGuard support, machine-learning grouping with custom fingerprinting evaluated first, reversible merge, deploy and version tracking, people tracking and RQL search over items. Items cannot be split through the web app or the API, and we found no public information on crash-free sessions or users or the per-SDK configuration options. 2 5 7 13 14
The Skeptic
Error capture is well evidenced: SDKs for JavaScript, Python, PHP, Ruby, Go, Apple and.NET with source maps, ProGuard, dSYM and Flutter symbolication, stack traces with request context and local variable values, machine-learning grouping plus custom fingerprints, reversible merging, and the line of code, deploy and last committer shown per error. The gaps that keep it below the top: we found no public information on crash-free sessions or users for mobile, the documentation states items cannot be split apart through the web app or the API, and per-SDK configuration options are only shown for the JavaScript source-map setup. 2 5 7 13 14 17
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
The captured pages show an error platform: context graphs of errors across time, users and systems, deploy and version analysis, and an RQL-plus-metrics analysis add-on, but I found no public information on endpoint timings with percentiles, slow query or N+1 detection, background job monitoring, distributed tracing, OpenTelemetry or profiling. Without response times of any kind documented, I have no way to find a slow client page before the client calls. 2 3 7
The SaaS CTO
Everything documented points to error monitoring with session replay and a query and metrics API, and we found no public information on distributed tracing, OpenTelemetry ingestion, endpoint timings with percentiles, slow-query detection or profiling. I cannot run my browser-click-to-database-call trace on what is shown here. 7 10 11
The Mobile Team Lead
The captured pages describe a suite of error monitoring, session replay, root-cause analysis, alerting and analytics over error trends, and we found no public information on transaction timings, distributed tracing, profiling, OpenTelemetry ingestion or real-user performance monitoring. For my team that means no latency or slow-query view would sit next to the crash data. 2 10 11
The Site Reliability Engineer
The captured pages describe error monitoring, session replay, root cause analysis and deploy tracking, and we found no public information on transaction timings, latency percentiles, distributed tracing, OpenTelemetry ingestion or code profiling. For a checkout-latency page at 3 a.m., nothing documented here shows me where time goes. 2 7 10 11
The Data Protection Officer
The captured pages describe an error-monitoring suite with session replay, error trend graphs across time, users and systems, and a query and metrics add-on, but we found no public information on transaction or endpoint timings, distributed tracing, slow query analysis, profiling, OpenTelemetry ingestion or real-user performance monitoring. 1 2 7
The Skeptic
The vendor's own description enumerates the suite as error monitoring, session replay, root-cause analysis, alerting and analytics, and the documentation headings cover notifications, deploy tracking and telemetry — we found no public information on transaction timings, distributed tracing, profiling, OpenTelemetry ingestion or Web Vitals. The only traces documented are exception stack traces with context, which is error capture, not a view of where time goes. 7 10 11
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
This is the strongest area for a maintenance shop: alerts reach Slack, Teams, email, PagerDuty and Opsgenie with per-project notification settings, the Jira integration is two-way with rules like reopen-on-regression and create-after-ten-occurrences, deploys arrive from GitHub Actions, CircleCI, Jenkins or Capistrano, and the REST API, webhooks and a Terraform provider cover the automation side. The Resolve agent that applies a fix, runs tests and opens a pull request, plus the MCP server for AI access, are genuinely differentiating. The captured pages describe no CLI, no scheduled reports, and name no model or data handling behind the AI features, so I stop short of the top band. 1 3 4 5 7 15 16
The SaaS CTO
Notifications reach Slack, Teams, PagerDuty and Opsgenie, the REST API and webhooks are documented down to tokens and rate limits, Terraform manages projects, and the Jira integration does real bidirectional sync with automation rules like creating an issue after ten occurrences and reopening on regression. The Resolve agent that writes a tested pull request is the differentiator, but the pages do not name the model behind it, and we found no public information on a CLI or scheduled digest reports. 1 4 7 15 16
The Mobile Team Lead
Alerts reach my rotation through Slack, Teams, PagerDuty and Opsgenie with two-way status updates, and the Jira integration does real bidirectional syncing, reopening tickets on reactivation and resolving them when the fix ships — the kind of loop a biweekly-release team lives in. Deploy tracking is documented from GitHub Actions, CircleCI and Jenkins, with a REST API, configurable webhooks, a Terraform provider and an MCP server, plus the Resolve agent opening tested pull requests, though the model behind it is not named. We found no public information on a CLI or scheduled digest reports. 1 2 4 7 15 16
The Site Reliability Engineer
Alerts land in under three seconds via PagerDuty, Opsgenie and Slack with notification channels configurable through the API, the Jira integration syncs bidirectionally with occurrence-count and severity rules, deploys report from GitHub Actions, CircleCI and Jenkins, and Terraform plus the REST API cover configuration as code. We found no public information on a CLI, on scheduled digests, on alerts for latency thresholds, or on which model runs the fix-writing Resolve agent. 1 3 4 15 16
The Data Protection Officer
Alerts reach Slack, email, webhooks, PagerDuty, Opsgenie, Teams and other channels with an under-three-second occurrence-to-alert claim, Jira syncs both ways with automation rules (reopen, resolve, create after ten occurrences), GitHub, GitLab and Bitbucket give commit, blame and source links, deploys arrive from CI tools, and the REST API, webhooks, Terraform provider and an MCP server expose configuration. We found no public information on a CLI, scheduled digest reports, performance-threshold alerts, or which AI model runs the Resolve agent that writes pull requests. 2 3 4 7 15 16
The Skeptic
An error reaches the fixer through many doors — Slack, Teams, email, PagerDuty, Opsgenie with two-way status, webhooks configurable through the documented API — and Jira syncs both ways with rules like reopening a ticket on reactivation or creating one after ten occurrences, plus GitHub, GitLab and Bitbucket commit links, deploy hooks from CI, a Terraform provider, and an AI agent that applies a fix and opens a tested pull request. What holds it back: we found no public information naming the model that powers the AI agent or the MCP server, on a CLI, or on scheduled digest reports. 1 4 7 15 16
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
Volume control is the best I have seen: per-token rate limits in windows from a minute to thirty days with events beyond the limit not billed, stop-at-limit on by default, on-demand overage at the plan rate, and overage budgets that pause processing at a dollar cap; retention is equally concrete at thirty, ninety or one hundred eighty days by plan, configurable from seven to one hundred eighty, with occurrences, people and IP data deletable. But scrubbing is documented only as client-side filtering of what you send, and I found no public information on server-side scrubbing rules, IP anonymisation or sampling — for shops holding customer addresses that gap matters. 7 8 12 17 18
The SaaS CTO
Retention is transparent per plan — 30, 90 and 180 days, configurable between 7 and 180 on paid plans — and volume control is unusually good: stop-at-limit on by default, dollar-capped overage budgets, per-token rate limits, and events dropped by rate limits are not billed. Data filtering is documented for the client configuration and permanent per-occurrence deletion with optional IP and person purge exists, but we found no public information on server-side scrubbing rules, IP anonymisation or error sampling. 7 8 17 18
The Mobile Team Lead
Volume control is unusually honest: per-token rate limits with configurable windows take effect immediately and stop events before they count toward the bill, overage budgets set a dollar cap, stop-at-limit is on by default, and rate-limited events are explicitly never billed. Retention runs 7 to 180 days configurable on paid plans with occurrence-level redaction, optional people and IP deletion recommended for GDPR, key destruction on compliant plans and machine-readable export. We found no public information on server-side scrubbing rules or IP anonymisation; filtering is documented only in the client configuration. 7 8 17 18
The Site Reliability Engineer
This is the part I care about most and it holds up: stop-at-plan-limit is on by default, an overage budget pauses processing at a dollar ceiling, on-demand events bill at the standard plan rate, rate-limited events are never billed, and per-token rate limits take effect immediately. Retention is configurable 7 to 180 days on paid plans with deletion of occurrences, IP addresses and people-tracking data, plus client-side filtering; we found no public information on server-side scrubbing rules, sampling, or IP anonymisation. 7 8 17 18
The Data Protection Officer
Retention is stated per plan (30 days free, 90 Essentials, 180 Advanced, custom for Enterprise, configurable 7 to 180 days on paid plans) with weekly cleanup, deletion and permanent redaction of individual occurrences, optional people-tracking and IP deletion, deletion including backups within 30 days of a request, and key destruction on encrypted accounts; rate limits take effect immediately per access token, stop-at-limit is the default, overage budgets pause processing, on-demand events bill at the standard plan rate, and rate-limited events are excluded from the bill. Scrubbing is documented only as filtering in the client configuration, however, and we found no public information on server-side scrubbing rules, IP anonymisation or error sampling — the parts I look for first when a trace can carry a member number. 3 7 8 12 17 18
The Skeptic
Retention is stated per plan (30 days free, 90 and 180 on the paid tiers, custom for Enterprise, adjustable between 7 and 180 days on all paid plans) with weekly cleanup and optional deletion of people and IP data, and what happens at the quota is spelled out three ways — stop at the plan limit by default, a dollar-capped overage budget that pauses processing, or on-demand events billed at the same rate as your standard plan, with rate-limited events explicitly not billed. The weak side is scrubbing: only client-side filtering of what gets sent is described, and we found no public information on server-side scrubbing rules, IP anonymisation or sampling. 7 8 12 17 18
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
This holds up in an audit: SOC 2 Type I and II plus ISO 27001 with the production-environment scope stated, SOC 3 viewable, annual third-party penetration tests, quarterly external and monthly internal scans, a responsible disclosure policy, SAML with tested providers and SCIM provisioning, IP safelisting, and a public status page with per-component uptime and a pipeline metrics dashboard. What the pages do not show: an SLA with credits published (SLAs sit in the Enterprise tier as a custom item) and how the SDKs behave while Rollbar itself is down. 7 8 9 19 20
The SaaS CTO
SAML SSO on Advanced and Enterprise with SCIM provisioning, two-factor authentication, audit controls, SOC 2 Type I and II, SOC 3, ISO 27001 with the production-environment scope stated, annual third-party penetration tests and a responsible disclosure policy make this presentable to my enterprise customers. We found no public information on an SLA with credits for the standard plans, on how SDKs behave during a Rollbar outage, or on uptime history beyond the roughly three-month window the status page shows. 7 8 9 19 20
The Mobile Team Lead
SOC 2 Type I and II and ISO 27001 scoped to the production environment are stated, SAML is set up from documented steps with tested providers and SCIM provisioning exists, alongside two-factor authentication, enterprise access controls like IP safelisting and session timeout, a responsible disclosure policy, annual third-party penetration tests and a public status page with component uptime and a pipeline metrics dashboard. Custom SLAs appear only at the Enterprise support tier, and we found no public information on published SLA credits or on how the SDK behaves when the vendor itself is down. 7 8 9 20
The Site Reliability Engineer
SOC 2 Type I and II, an ISO 27001 scope stated as the production environment, SAML on the Advanced and Enterprise plans with SCIM provisioning, audit controls, IP safelisting, TLS and encryption at rest, a responsible disclosure policy and a public status page with per-component uptime give me most of what my auditors ask for. Two gaps decided the score: the service-level agreement appears only as custom terms on the Enterprise plan, and we found no public information on how the SDKs behave when Rollbar itself is down. 7 8 9 20
The Data Protection Officer
SOC 2 Type I and II, ISO 27001 scoped to the production environment, SOC 3 published, annual third-party penetration tests with a summary report for Enterprise customers, quarterly third-party vulnerability scans, a responsible disclosure policy, annually tested disaster recovery, SAML SSO on Advanced and Enterprise plans with SCIM provisioning, two-factor authentication, IP safelisting and a suite of audit controls. A public status page with per-component uptime and a pipeline metrics dashboard exists, though we found no public information on a published SLA with credits, export of audit logs to a SIEM, or how the SDKs behave while ingestion is down. 7 8 9 19 20
The Skeptic
The compliance trail is unusually deep: SOC 2 Type I and II, ISO 27001 with its scope stated as the production environment, SOC 3 viewable, quarterly third-party and monthly internal scans, annual third-party penetration tests, a responsible disclosure policy, per-account encryption keys on the compliant tier, SAML with tested providers, SCIM, two-factor authentication and a public status page with component uptime and a pipeline metrics dashboard. Two gaps keep it from the top: the SLA is a custom Enterprise support item rather than a published commitment with credits, and we found no public information on how the SDKs behave while ingestion is down. 7 8 9 20
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 chain is American end to end: Rollbar, Inc. is the contracting entity, the service is controlled from California, the primary data center is Iowa on Google Cloud, and the privacy policy allows storage in the United States and locations around the world — I found no public information on an EU data region, and self-hosting is documented only for the Lines product line, not the observability platform. A self-serve data processing addendum, a published subprocessor list, and standard contractual clauses plus Data Privacy Framework certification soften the transfer story, so this sits a notch above the baseline, but for my German clients there is no European chain. 1 5 8 11 12 19
The SaaS CTO
Rollbar, Inc. is the contracting entity, hosting runs on Google Cloud with the primary data center in Iowa, and the privacy policy allows storage in the United States and locations around the world; we found no public information on an EU data region, which is the first question my Berlin enterprise customers ask. A data processing addendum and a subprocessor page exist and Data Privacy Framework and contractual-clause safeguards are stated, and the only self-hosting described is the Rollbar Lines product line on the customer's own virtual machines rather than the observability platform itself. 8 11 12 19
The Mobile Team Lead
The contracting entity is Rollbar, Inc., controlled from California, hosted on Google Cloud with the primary data center in Iowa, and the privacy policy allows storage in the United States and locations around the world; we found no public information on an EU data region for the core error platform. Transfer safeguards are present — standard contractual clauses, Data Privacy Framework certification, a data processing addendum and a published subprocessor list — and the only self-hosted option described is the separate Rollbar Lines product rather than the error platform itself, so the chain a Hamburg retailer would depend on stays non-European end to end. 1 8 11 12 19
The Site Reliability Engineer
Rollbar, Inc. is the contracting entity, the service is controlled from California with data on Google Cloud in Iowa and processed "in the United States and locations around the world", and no EU data region is offered. A data processing addendum and a subprocessor list are published with Data Privacy Framework certification and standard contractual clauses as transfer safeguards, which is why this sits just above the floor, but the chain is US end to end. 5 8 11 12
The Data Protection Officer
Rollbar, Inc. is the contracting entity, the services are controlled and operated from California, the primary data center runs on Google Cloud Platform in Iowa, and the privacy policy allows storage and processing in the United States and locations around the world; a data processing addendum and a published subprocessors list exist, and transfers rely on the EU-U.S. Data Privacy Framework with standard contractual clauses as a fallback. We found no public information on an EU data region for the core platform or on where the AI agent that writes fixes runs, and the self-hosted option described applies to the separate Lines product line rather than the error platform itself. 1 5 8 11 12 19
The Skeptic
Rollbar, Inc. is the contracting entity, controlled from California, hosting the complete environment on Google Cloud Platform with the primary data center in Iowa, and the privacy policy allows storage and processing in the United States and locations around the world. Transfer safeguards exist on paper — a data processing addendum, a data subprocessors page, standard contractual clauses and Data Privacy Framework certification — but we found no public information on an EU data region or EU contracting entity, and the only self-hosted offer is the Rollbar Lines agent on the customer's own machines, not the error platform itself. 1 8 11 12 19
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 plan structure is unusually legible: included occurrences, replays and credits per tier, retention of thirty, ninety, one hundred eighty or custom days, service links gated per plan, an annual term stated as "Get 2 months free!", and three explicit overage behaviours including a pause at a dollar budget. But the captured pricing page shows a dollar figure only for the free tier — "Plans starting at $0" — with the Essentials and Advanced prices not stated, and the pages give no per-event overage rate or VAT statement, so I cannot compute the real annual cost for forty client sites from public pages. 7 11 18
The SaaS CTO
The plan structure is unusually well documented — occurrences, replays and credits per plan, retention from 30 to 180 days, and three overage behaviours including a dollar-capped budget and stop-at-limit on by default — but we found no public dollar price for the Essentials or Advanced plans on the pricing page, and no VAT or per-event overage rate to compute from. Without base prices, I cannot compute an annual cost from public pages alone. 7 11 18
The Mobile Team Lead
Plan volumes are public down to occurrences from 10K to 50M per month, replays and credits per tier, retention of 90 or 180 days or custom, and the overage behaviour is the clearest I have read: stop at the plan limit on by default, a dollar-capped overage budget that pauses processing, or on-demand billed at the same rate as the standard plan, with never-billed rate-limited events. But the captured pricing pages show no dollar figure for the Essentials and Advanced plans, so my team cannot compute a real annual cost, and we found no public information on VAT treatment; SAML being confined to Advanced and Enterprise is at least stated. 7 11 18 20
The Site Reliability Engineer
The free tier is concrete at "$0 monthly" for 5K occurrences and 1K replays with a 14-day trial, each plan's volume ranges and retention days are public, the three overage behaviours are stated clearly, and annual billing is advertised as "2 months free". But we found no public information on the dollar price of the Essentials and Advanced plans or on the per-event overage rate, and Enterprise is custom pricing, so I cannot compute a real annual bill from these pages. 7 11 18
The Data Protection Officer
Volume limits are public (5K occurrences + 1K replays free per month; 10K to 50M occurrences and up to 10M credits for the paid tiers), quota behaviour is documented (stop at your plan limit on by default, overage budgets that pause processing, on-demand billed at the same rate as your standard plan, rate-limited events not counted), retention per plan and the annual "2 months free" discount are stated, and SAML requires Advanced or Enterprise. The captured pricing page carries no dollar figure for Essentials or Advanced and Enterprise is "Custom", and VAT is not stated, so the real annual cost cannot be computed from the pages we read. 7 8 11 18 20
The Skeptic
Volume limits are unusually public — 5,000 occurrences and 1,000 replays free, 10K to 50M occurrences and 1K to 10M replays on the paid tiers, credits and retention per plan — and overage behaviour is documented three ways: stop at the limit by default, a dollar-capped budget that pauses processing, or on-demand events billed at the same rate as your standard plan, with a two-months-free annual term and a BAA at no additional cost from the Advanced 4M annual plan. But the captured pricing page gives no dollar figure for the Essentials or Advanced plans, so the per-event rate behind the overage wording cannot be computed, and we found no public information on VAT or a price calculator. 7 8 11 18
European sovereignty — proven facts
4 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 |
Outside the EU
unverified
Why unverified?The word "primary" implies other locations, and the privacy policy allows storage in "the United States and locations around the world", but no EU hosting option is mentioned anywhere. |
0/4 pts | 8 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Only the Rollbar Lines product line is stated to run on customers' own infrastructure (installed by a Rollbar team); the core Rollbar observability platform shows no self-hosting option in these excerpts. |
1/1 pts | 1 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The addendum is reachable from within account settings after login rather than openly posted on the excerpted pages; the docs navigation also lists a 'Data Processing Addendum' page whose content was not captured. |
1/1 pts | 11 Report an error |
| Transfer impact assessment |
Published
unverified
Why unverified?Only the public documentation navigation lists the page title; the assessment's full text was not captured, so publication is inferred from the docs menu. |
1/1 pts | 8 Report an error |
Questions about Rollbar
Is Rollbar European?
No. whats-best.ai classifies Rollbar as Rest of world.
Where does Rollbar store data?
Rollbar stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.
Does Rollbar have a free plan?
Yes. Rollbar has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to Rollbar?
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: Rollbar 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 — Data processing agreement. The addendum is reachable from within account settings after login rather than openly posted on the excerpted pages; the docs navigation also lists a 'Data Processing Addendum' page whose content was not captured.
- Weak sourcing — Transfer impact assessment. Only the public documentation navigation lists the page title; the assessment's full text was not captured, so publication is inferred from the docs menu.
- Weak sourcing — Hosting location. The word "primary" implies other locations, and the privacy policy allows storage in "the United States and locations around the world", but no EU hosting option is mentioned anywhere.
- Weak sourcing — Hosting options. Only the Rollbar Lines product line is stated to run on customers' own infrastructure (installed by a Rollbar team); the core Rollbar observability platform shows no self-hosting option in these excerpts.
- 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.
- 20 integrations 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
- 10 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
- 4 data 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
- 4 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
- 3 compliance 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
- 1 support 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
Sources (20)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage rollbar.com Checked 6 Nov 2026 Details →
- 2 Features page (error monitoring) rollbar.com Checked 6 Nov 2026 Details →
- 3 Features page rollbar.com Checked 6 Nov 2026 Details →
- 4 Integrations page rollbar.com Checked 6 Nov 2026 Details →
- 5 Documentation docs.rollbar.com Checked 6 Nov 2026 Details →
- 6 API documentation docs.rollbar.com Checked 6 Nov 2026 Details →
- 7 Pricing page rollbar.com Checked 6 Nov 2026 Details →
- 8 Security / trust page docs.rollbar.com Checked 6 Nov 2026 Details →
- 9 Public status page status.rollbar.com Checked 6 Nov 2026 Details →
- 10 About page rollbar.com Checked 6 Nov 2026 Details →
- 11 Terms of service (names the operating company) docs.rollbar.com Checked 6 Nov 2026 Details →
- 12 Privacy policy docs.rollbar.com Checked 6 Nov 2026 Details →
- 13 Error capture, grouping & triage — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 14 Error capture, grouping & triage — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 15 Alerting, integrations & developer workflow — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 16 Alerting, integrations & developer workflow — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 17 Data scrubbing, retention & volume control — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 18 Data scrubbing, retention & volume control — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 19 Access control, security & the vendor's reliability — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →
- 20 Access control, security & the vendor's reliability — found from sitemap docs.rollbar.com Checked 6 Nov 2026 Details →