Rootly Subprocessors
Rootly is an incident response and reliability platform that helps teams manage incidents, alerts, on-call scheduling, and post-incident retrospectives.
- Subprocessors
- 28
- Locations
- 3
- Categories
- 14
- Last scanned
| Name | Category | Purpose | Location | Data processed |
|---|---|---|---|---|
| Amazon Web Services ↗ | Cloud Infrastructure | Hosting. Rootly’s primary cloud infrastructure: compute, application databases, object storage, queuing, and event routing. |
 United States
|
All customer data stored in Rootly, encrypted at rest |
| Google Cloud ↗ | Cloud Infrastructure | Hosting |
United States
|
Customer data processed by the hosted services |
| Microsoft Azure ↗ | Cloud Infrastructure | Hosting |
United States
|
Customer data processed by the hosted services |
| Cloudflare ↗ | Cloud Infrastructure | Content delivery network, edge networking, and web application firewall |
United States
|
HTTP request data and tenant identifiers |
| ClickHouse Cloud ↗ | Database | Columnar analytics database for AI evaluation and product analytics | – | AI evaluation datasets and product usage metrics |
| QuotaGuard ↗ | Cloud Infrastructure | Static IP proxy for outbound integration traffic | – | HTTP request payloads transiting to customer-connected integrations |
| OpenAI ↗ | AI | AI functionality: LLM inference for summarization, catchup, and generative features |
United States
|
Incident content submitted for AI processing |
| Anthropic ↗ | AI | AI functionality: LLM inference for summarization, catchup, and generative features |
United States
|
Incident content submitted for AI processing |
| Braintrust ↗ | AI | AI functionality: LLM request routing, tracing, and evaluation |
United States
|
Incident content and other data submitted for AI processing |
| Recall.ai ↗ | AI | Meeting transcription: meeting orchestration, recording capture, and platform connectivity for AI Meeting Scribe |
United States
|
Meeting audio/video streams, bot lifecycle events |
| Twilio ↗ | Communications | In-app calling and SMS for on-call paging and live call routing |
United States
|
Phone numbers, alert and notification content |
| SendGrid ↗ | Email delivery for transactional and notification email |
United States
|
Email addresses, notification content | |
| Mailgun ↗ | Transactional email delivery |
United States
|
Email addresses, notification content | |
| Datadog ↗ | Monitoring | Monitoring: application performance, logging, and infrastructure observability |
United States
|
Application logs and telemetry, which may include user and team identifiers |
| Sentry ↗ | Error Tracking | Monitoring: application error and exception tracking |
United States
|
Error traces and request context, which may include user and team identifiers |
| pganalyze ↗ | Monitoring | Monitoring: database performance and query analytics |
United States
|
Database query patterns and telemetry, which may include user and team identifiers |
| LaunchDarkly ↗ | Developer Tools | Feature management: feature flag evaluation and progressive rollout targeting |
United States
|
Team and user identifiers used as targeting keys |
| Segment ↗ | Analytics | Analytics: customer data platform for product analytics event routing | US (Oregon) | User profile data, product usage events |
| PostHog ↗ | Analytics | Analytics: product analytics and user behavior tracking |
United States
|
User and team identifiers, product usage events |
| Oliv.ai ↗ | Analytics | Analytics: product and customer analytics |
United States
|
User profile data and product usage metrics |
| HubSpot ↗ | CRM | Emails: CRM and customer communication |
United States
|
User profile data and account metadata |
| Pylon ↗ | Customer Support | Customer support platform |
United States
|
User profile data, support ticket content |
| Linear ↗ | Productivity | Support ticket tracking |
United States
|
User profile data, support ticket content |
| Metabase ↗ | Analytics | Business intelligence. Rootly personnel run read-only queries against production application data to support customer accounts, troubleshoot issues, and analyze product usage. |
United States
|
User profile data (names, email addresses, phone numbers), incident and alert records, and associated metadata |
| Snowflake ↗ | Data Warehouse | Data warehouse for aggregated product usage and account health analytics |
United States
|
Product usage metrics and account metadata |
| Stripe ↗ | Payment Processing | Payment processing and subscription billing |
United States
|
Billing contact details and payment metadata |
| Slack ↗ | Communications | Communication: internal team communication and incident coordination |
United States
|
User identifiers, message content |
| Intercom ↗ | Customer Support | Live chat and customer support | AWS us-east-1 | User profile data, support conversation content |
No subprocessors match your filters.
No changes recorded yet. Changes will appear here after the next scan detects updates.
Summary
28
Total Subprocessors
3
Locations
14
Categories
86%
in United States
Subprocessors by Country
Subprocessors by Category
Biggest overlap with
Other companies using the most of the same subprocessors