Laminar

laminar.sh

Laminar declares 5 subprocessors in its subprocessor list, which we last checked on Nov 21, 2026 (evidence). They include Amazon Web Services, Google Cloud and posthog. No published changes since we first read it on Oct 5, 2026. 1 tracked vendor, Browser Use, names Laminar as a subprocessor.

Subprocessors CSV of Laminar's subprocessors · Atom feed of Laminar's subprocessors DORA draft CSV of Laminar's subprocessors as declared by Laminar what's this? · 

5 third parties.

NamePurposeLocationListed since
Amazon Web Services
ClickHouse customers' observability data with related metadata, customer's datasets created from observability data.
Google Cloud Platform
PostHog Opt-in customer analytics information
Supabase all platform metadata (user projects, workspaces, etc.)

Web TechnologiesCSV of Laminar's web technologies · Atom feed of Laminar's web technologies

Laminar's homepage made 70 requests to 3 domains, and 2 services controlled by another company.

Analytics (1): CloudflareOther (1): reviewed as Development: GitHub

2 third parties by category: Analytics 1Other 1

Third parties 2 · 3 requests
GitHub github.com 3% of the page's requests 2
Cloudflare Cloudflare Browser Insights 1% of the page's requests 1
First party 1 · 67 requests
Laminar Cloudflare Framer Motion HSTS HTTP/3 Lucide Next.js 16.4.3 Next.js App Router Open Graph Priority Hints React Recharts Webpack 96% of the page's requests 67

2 tracked companies loaded by the homepage are not in Laminar's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (1)CSV of the companies listing Laminar · Atom feed of the companies listing Laminar

1 company

Service statusCSV of Laminar's status page incidents · Atom feed of Laminar's status page incidents

Aug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reportedNov 13: no incident reportedNov 14: no incident reportedNov 15: no incident reportedNov 16: no incident reportedNov 17: no incident reportedNov 18: no incident reportedNov 19: no incident reportedNov 20: no incident reportedNov 21: no incident reported

90 days agotoday

No incidents reported since Oct 5, 2026

As Laminar's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by Laminar's subprocessorsCSV of incidents reported by vendors Laminar lists · Atom feed of incidents reported by vendors Laminar lists

25 reported incidents in the last 30 days, by 2 of the vendors Laminar lists as subprocessors.

A subprocessor list names a company, not the service an incident touched. This does not show that Laminar was involved.

DateCompanyIncidentImpactLasted
SupabaseGateway availability disruption minor—
ClickHouseLightweight updates (beta) can cause undesired effects minor18 h 58 min
SupabaseEdge Function Issues in ap-northeast-1 minor3 h 7 min
Supabase‘Project not specified’ errors reported for users in ap-northeast-2 minor3 h 11 min
SupabaseProjects in sa-east-1 experiencing delayed event ingestion no impact stated8 h 43 min
ClickHouseProvisioning may be degraded minor48 min
SupabaseElevated Error rates for All Supabase project APIs minor1 h 17 min
SupabaseDatabase Connection Errors minor3 h 4 min
SupabaseStorage request degradation in eu-west-1 minor7 min
SupabaseProject Lifecycle Issues in ap-northeast-1 minor4 h 48 min
ClickHouseProvisioning and scaling operations may take longer in AWS ap-northeast-1 Tokyo minor7 h 38 min
SupabaseInterruption in connections to Supavisor in eu-west-2 no impact stated1 h 41 min
SupabaseIncreased Errors with Project Lifecycle Operations in US-West-2 minor2 h 27 min
SupabaseIntermittent 502/503 errors for pg_net calls to Edge Functions minor42 min
SupabaseStorage issues in us-east-1 and eu-central-1 minor16 h 18 min
SupabaseIntermittent errors on Supavisor Shared Pooler in us-east-2 minor28 min
SupabaseManagement API Postgres config updates overwriting previous updates no impact stated2 h 8 min
SupabaseStorage uploads failing in us-east-1 minor1 h 13 min
ClickHouseSQL Console database connection outage minor49 min
SupabasePG15 -> PG17 Upgrade Failures no impact stated1 h 8 min
SupabaseLogs degraded in multiple regions no impact stated51 min
SupabaseDelayed Log Delivery from 14:10 - 15:30 UTC minor52 min
ClickHouseDegraded support ticket submission and response minor2 h 47 min
SupabaseLog Drain Issues minor46 min
SupabaseElevated Mgmt API Error Rates in Multiple Regions minor3 days

Who is around them.

ChangesCSV of Laminar's changes · Atom feed of Laminar's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Laminar's site

Laminar transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/laminar-sh"><img src="https://thirdpartyindex.com/badge/laminar-sh.svg" alt="Laminar transparency rating on Third Party Index" height="20"></a>
[![Laminar transparency rating on Third Party Index](https://thirdpartyindex.com/badge/laminar-sh.svg)](https://thirdpartyindex.com/vendors/laminar-sh)