Macroscope
Macroscope declares 28 subprocessors in its subprocessor list, which we last checked on Nov 20, 2026 (evidence). They include Amazon Web Services, Google Cloud and OpenAI. The list last changed on Nov 5, 2026: 1 added, 0 removed.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors CSV of Macroscope's subprocessors · Atom feed of Macroscope's subprocessors DORA draft CSV of Macroscope's subprocessors as declared by Macroscope what's this? ·
28 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Anthropic AI | Large Language Model (LLM) processing to generate summaries and code reviews; Note: None of our customer data is ever used to train any of the Anthropic models. Transfers are safeguarded by Standard Contractual Clauses. Customers have the option to limit data and inference to US only for an extra cost. No data is retained for all models except Fable, where data may be retained for 30 days for security purposes, and this data may be stored globally. | Global | |
| AWS AI | LLM Inference Processing for the product; We occasionally use AWS Bedrock as a backup provider to run inference for other provider LLMs. We also sometimes use AWS for compute services. Customers have the option to limit LLM data and inference to US only for an extra cost. | Global | |
| Baseten AI | LLM inference and training; We occasionally use Baseten to provide LLM inference and training. We never use customer data to train LLMs. | Global | |
| Cloudflare | Generating artifacts as part of Murmur; We use Cloudflare to hose generated artifacts from Murmur agents Effective Nov 14 | Global | |
| Fireworks AI AI | Inference; We use Fireworks to process inference for certain LLM calls. Models are never trained on any customer data. | Global | |
| Google Cloud Platform | Cloud provider; Our infrastructure is primarily hosted on GCP. | United States | |
| Google Gemini AI | Large Language Model (LLM) processing; We occasionally use Gemini models through Google's Vertex API to generate summaries and do code review. Models are never trained on any customer data. | Global | |
| Linear | Collaboration; We use Linear as our internal project management system. When issues relate to the experience of a specific customer, there may be minimal customer information as part of the created ticket. | United States | |
| Meta | For running AI inference of Meta models; We use Meta for inference of their proprietary models. Effective November 9 | Globally | |
| Microsoft Azure Cloud | Inference and Cloud Services; We will occasionally use Azure to handle inference for LLMs from other providers. We also occasionally use Azure services for cloud processing as a backup to GCP. Customers have the option to limit data and inference to US only for an extra cost. | Global | |
| Modal | Compute Sandboxes; We use modal to create sandboxes where we can perform secure computing. We also occasionally us them to process inference for LLMs. | Global | |
| OpenAI AI | Large Language Model (LLM) processing to generate summaries and code reviews; Note: None of our customer data is ever used to train any of the OpenAI models. Transfers are safeguarded by Standard Contractual Clauses. Customers have the option to limit data and inference to US only for an extra cost. | Global | |
| Parallel | AI powered web searches; Allows Macroscope to browse and search the web. | United States | |
| Posthog | We use Posthog for analytics and error tracking of our web application and corporate website. Effective date: November 5, 2025; Web analytics and error reporting | United States and EU | |
| Prime Intellect | LLM Inference and Training; We occasionally use Prime Intellect to provide LLM inference and training. We never use customer data to train LLMs. Effective date: August 7, 2026 | USA | |
| Pylon | Customer Support; We use Pylon as our unified customer support platform, to facilitate support via Email, Slack and other mediums. | United States | |
| Sail | LLM Inference and Training; We occasionally use Sail to provide LLM inference and training. We never use customer data to train LLMs. | Global | |
| SendGrid | Email delivery; SendGrid powers email delivery for some of our reporting functionally. This functionally is optional but when configured by customers, allows you to receive summaries via email. | United States | |
| Sentry | Error tracking; We use Sentry to track client side errors, which sometimes include minimal customer information to track the source of the issue. | United States | |
| Slack | Collaboration; We use Slack for internal collaboration, including debugging customer-reported issues which occasionally include customer information. | United States | |
| SpaceXAI AI | LLM Inference and Training; We occasionally use SpaceXAI to provide LLM inference and training. We never use customer data to train LLMs. | Global | |
| Stripe Inc | Payment processing; Stripe stores customer payment information and processes payments for us. | Multi-region | |
| Temporal | Distributed software workflows; Temporal is an integral part of our infrastructure. Any customer data processed via Temporal is encrypted, and Temporal does not have decryption keys. | United States | |
| Terminal | We occasionally use Terminal to provide LLM inference and training. We never use customer data to train LLMs. Effective date: September 8, 2026 | LLM Inference and Training | |
| Together AI | LLM Inference and Training; We occasionally use Together to provide LLM inference and training. We never use customer data to train LLMs. | Global | |
| TypeSafe AI | AI Inference; Direct use of AI models for inference. Effective November 12 | Global | |
| WorkOS | In some cases, for Enterprise customers, we leverage WorkOS to integrate with your Identity Provider systems to better improve our summaries.; Integration with Identity Providers | United States | |
| Zapier | We use Zapier to automate internal workflows and triage customer support requests.; Workflow automation | United States |
Web TechnologiesCSV of Macroscope's web technologies · Atom feed of Macroscope's web technologies
Macroscope's homepage made 116 requests to 13 domains, and 6 services controlled by another company.
6 third parties by category: Advertising 3Analytics 3
2 tracked companies loaded by the homepage are not in Macroscope's subprocessor list. A website can use a service without it processing customer data.
ComplianceCSV of Macroscope's compliance · Atom feed of Macroscope's compliance
- Certified
Certifications as Macroscope's trust center lists them; reports are usually shared on request (evidence)
Service statusCSV of Macroscope's status page incidents · Atom feed of Macroscope's status page incidents
90 days agotoday
- 49 incidents in 90 days
- 4 major or critical
- 47 min typical time to resolve
- 1 h 15 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Incident with Pull Requests | no impact stated | 4 h 26 min | |
| Impact across multiple GitHub products including Actions, Pages, and Copilot products. | no impact stated | 33 min | |
| Incident with Git Operations and Pull Requests | no impact stated | 1 h 44 min | |
| Incident with Actions and Checks API | no impact stated | 46 min | |
| Incident with Webhooks and Actions | no impact stated | 1 h 50 min | |
| Increase in timeouts for some unauthenticated users | no impact stated | 1 h 56 min | |
| Degraded performance for multiple GitHub services | no impact stated | 44 min | |
| Incident with Actions | no impact stated | 52 min |
Incidents per month
critical major minor no impact stated before or partly before our history
Components affected
| Component | Incidents | Bar |
|---|---|---|
| GitHub Actions | 26 | |
| API | 9 | |
| GitHub API Requests | 7 | |
| Agent | 1 | |
| CLI Code Review | 1 | |
| Code Review | 1 | |
| Status | 1 |
As Macroscope's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Macroscope's subprocessorsCSV of incidents reported by vendors Macroscope lists · Atom feed of incidents reported by vendors Macroscope lists
384 reported incidents in the last 30 days, by 16 of the vendors Macroscope lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Macroscope was involved.
And 359 more. All of them: CSV · Who is around them.
ChangesCSV of Macroscope's changes · Atom feed of Macroscope's changes
See the list as we read it on any date: Time machine
- Added subprocessor: Cloudflare evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare