Lago
Lago declares 9 subprocessors in its subprocessor list, which we last checked on Nov 12, 2026 (evidence). They include Amazon Web Services, Sentry and ClickHouse. No published changes since we first read it on Sep 28, 2026. 6 tracked vendors name Lago as a subprocessor, including Groq, Mistral and Gladia.
Subprocessors CSV of Lago's subprocessors · Atom feed of Lago's subprocessors DORA draft CSV of Lago's subprocessors as declared by Lago what's this? ·
9 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Cloud hosting, compute, storage, database, caching, and networking infrastructure, and delivery of emails sent on behalf of customers (such as invoices, credit notes and payment receipts) through Amazon SES. Processes customer account data, billing events, usage records, and email recipient addresses and message content. | United States or EU, depending on customer datacenter election | |
| ClickHouse, Inc. | Analytics database for usage metering and event aggregation. Processes usage events and metering data. | United States or EU, depending on customer datacenter election | |
| Functional Software, Inc. (Sentry) | Application error tracking and performance monitoring. May process user identifiers and IP addresses in error traces. | United States or EU, depending on customer datacenter election | |
| incident.io Ltd | Incident management, alerting, and on-call scheduling. Processes internal operational data only. | EU (Belgium) | |
| Mistral AI AI | AI model inference for platform features. May process customer billing data and usage patterns. | France | |
| Nango, Inc. | Integration platform — Lago builds connectors on top of the Nango API to sync customer account data, invoice data, and CRM records with third-party systems (e.g., HubSpot, Xero, NetSuite, Avalara, Anrok). Only activated if the customer uses a supported integration. | United States | |
| Peaberry Software, Inc. (Customer.io) | Delivery of Lago's own product and lifecycle communications to its customers. Does not deliver emails sent on behalf of customers. Processes email addresses and customer identifiers. | United States | |
| Pylon Labs, Inc. | Customer support ticketing and communication. Processes customer contact information and support request content. | United States | |
| RisingWave Labs, Inc. | Managed stream processing (RisingWave Cloud) for real-time usage and wallet balance computation. Processes usage events and replicated billing data such as customer, subscription, plan, and wallet records. | EU |
Web TechnologiesCSV of Lago's web technologies · Atom feed of Lago's web technologies
Lago's homepage made 83 requests to 1 domain.
Subprocessor of (6)CSV of the companies listing Lago · Atom feed of the companies listing Lago
Cerebrium cerebrium.ai Billing and metering; Usage records, invoices, customer billing details
Gladia gladia.io Payments
Groq groq.com GroqCloud Billing & Invoicing
Laravel laravel.com Billing provider
Mistral mistral.ai Billing; Products: All Products under a paid subscription
SurrealDB surrealdb.com Metering and Usage-Based Billing Provider
ComplianceCSV of Lago's compliance · Atom feed of Lago's compliance
- Certified
- Says it complies with
Certifications as Lago's trust center lists them; reports are usually shared on request (evidence)
Service statusCSV of Lago's status page incidents · Atom feed of Lago's status page incidents
90 days agotoday
- 8 incidents in 90 days
- 0 major or critical
- 10 min typical time to resolve
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Degraded performance on our API | minor | 6 min | |
| Degraded performance on our API | minor | 6 min | |
| Degraded performance on our API | minor | 5 min | |
| Degraded performance on our API | minor | 11 min | |
| Degraded performance on our API | minor | 10 min | |
| Degraded performance on our API | minor | 3 h 28 min | |
| Degraded performance on our API | minor | 57 min | |
| Degraded performance on our API | minor | 5 min |
Incidents per month
critical major minor no impact stated before or partly before our history
As Lago's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Lago's subprocessorsCSV of incidents reported by vendors Lago lists · Atom feed of incidents reported by vendors Lago lists
25 reported incidents in the last 30 days, by 5 of the vendors Lago lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Lago was involved.
ChangesCSV of Lago's changes · Atom feed of Lago's changes
See the list as we read it on any date: Time machine
None since tracking began.