From the source
Billing data lived in Stripe, product data lived in Postgres, and there was no good way to join them.
We built a tool to sync Stripe data into a stripe schema in Postgres, kept building it in the open, and it grew into something bigger than we expected.
Today, the repo moves from supabase/stripe-sync-engine to stripe/sync-engine .
How we got here # In December 2025, we announced a one-click integration that brought the Stripe Sync Engine directly into the Supabase dashboard.
That launch came from close collaboration with Stripe's engineering team.
Stripe engineers contributed directly to the repo: incremental sync using cursor-based pagination, JSONB storage with generated columns, multi-account support for Stripe Connect platforms, and a new CLI with proper event ordering.
A key part of that collaboration was Stripe's work on automatic, incremental backfilling using Supabase Cron and Queue.
This is what made it possible to ingest all of your existing Stripe data into Postgres reliably and at scale, and what unlocked the dashboard integration.
…
