Connect client traces to your logs
supabase-js now propagates W3C Trace Context to Supabase, so a client trace and the matching Supabase log share one trace_id.
Author: 
Katerina Skroumpelou, Steven Eubank
Published 18 August 20264 minute read
Supabase Blog
Introducing Supabase Evals
productPublished 31 Jul 2026
Sign in with ChatGPT is in beta on Supabase
productPublished 29 Jul 2026
Observability for every Supabase project with Grafana Cloud
productPublished 23 Jul 2026
Supabase Pipelines is now in Public Alpha
productPublished 21 Jul 2026
Unified Logs is now in open beta
productPublished 16 Jul 2026
Searchable field-level encryption on Supabase with CipherStash
productPublished 9 Jul 2026
Agentic Coding on Supabase with OpenCode
productPublished 30 Jun 2026
Supabase Series F
companyPublished 4 Jun 2026
Multigres v0.1 Alpha: an operating system for Postgres
productPublished 4 Jun 2026
Protecting your Supabase projects from npm supply chain attacks
securityPublished 26 May 2026
Supabase Is Now an Official ChatGPT App
productPublished 8 May 2026
Introducing @supabase/server
productPublished 6 May 2026
Realtime or Pipelines? How to choose the right tool
developersPublished 5 May 2026
Branching Without Git Is Now The Default
productPublished 4 May 2026
Introducing the OSSCAR Index
companyPublished 28 Apr 2026
Supabase is now ISO 27001 certified
companyPublished 22 Apr 2026
We're Transferring the Stripe Sync Engine to Stripe
companyPublished 14 Apr 2026
AI Agents Know About Supabase. They Don't Always Use It Right.
productPublished 9 Apr 2026
Custom OIDC Providers for Supabase Auth
productPublished 8 Apr 2026
100,000 GitHub stars
companyPublished 2 Apr 2026
Supabase docs over SSH
productPublished 1 Apr 2026
Navigating Regional Network Blocks
productPublished 26 Mar 2026