---
title: "We're Transferring the Stripe Sync Engine to Stripe"
description: "The Stripe Sync Engine repository is moving from supabase/stripe-sync-engine to stripe/sync-engine after growing from an open-source tool for syncing Stripe data into a Stripe schema in Postgres. The transfer follows collaboration that added cursor-based incremental sync, JSONB storage with generated columns, multi-account support for Stripe Connect platforms, event ordering in a new CLI, and automatic incremental backfilling using Supabase Cron and Queue. The latest release adds coupon synchronization, branching support, immediate syncing on installation, one-click upgrades, SSL enforcement, and tighter installation controls, along with clearer errors and dashboard visibility for Edge Function source code. The project remains open source under Apache 2.0, existing installations continue to work, and the Supabase dashboard integration is unchanged. With Stripe data in Postgres, users can join it with application data for subscription checks, feature gating, MRR, and churn analysis."
---

# We're Transferring the Stripe Sync Engine to Stripe

[Supabase](https://yomu.fyi/company/supabase) · raminder\_singh, matt\_linkous, gregor\_vand, ana\_mogul · Apr 14, 2026

**Type:** Announcement

## Summary

The Stripe Sync Engine repository is moving from supabase/stripe-sync-engine to stripe/sync-engine after growing from an open-source tool for syncing Stripe data into a Stripe schema in Postgres. The transfer follows collaboration that added cursor-based incremental sync, JSONB storage with generated columns, multi-account support for Stripe Connect platforms, event ordering in a new CLI, and automatic incremental backfilling using Supabase Cron and Queue. The latest release adds coupon synchronization, branching support, immediate syncing on installation, one-click upgrades, SSL enforcement, and tighter installation controls, along with clearer errors and dashboard visibility for Edge Function source code. The project remains open source under Apache 2.0, existing installations continue to work, and the Supabase dashboard integration is unchanged. With Stripe data in Postgres, users can join it with application data for subscription checks, feature gating, MRR, and churn analysis.

## Context

Billing data lived in Stripe while product data lived in Postgres, and there was no good way to join the two datasets. The project began as an open-source tool to sync Stripe data into a Stripe schema in Postgres.

## Approach / What changed

The repository was developed collaboratively by Supabase and Stripe, adding cursor-based incremental sync, JSONB storage with generated columns, Stripe Connect multi-account support, a CLI with event ordering, and automatic incremental backfilling using Supabase Cron and Queue. It is transferring to stripe/sync-engine, with additional release improvements for installation, management, reliability, and supported Stripe objects.

## Takeaways

- Stripe engineers contributed incremental sync, JSONB storage with generated columns, Stripe Connect multi-account support, event ordering, and automatic incremental backfilling.
- The latest release adds coupon sync, branching support, immediate synchronization on install, one-click upgrades, SSL enforcement, and Admin- or Owner-restricted install controls.
- The project remains open source under the Apache 2.0 license; existing users and the Supabase dashboard integration are not disrupted by the repository move.

**Tags:** [Open Source](https://yomu.fyi/topic/open-source), [Postgres](https://yomu.fyi/topic/postgres), [Reliability](https://yomu.fyi/topic/reliability)

- Source: [Supabase](https://supabase.com/blog/stripe-sync-engine-transfer)
- Source URL: https://supabase.com/blog/stripe-sync-engine-transfer
- Ingested by Yomu: 2026-08-29T20:00:49.571Z

[Read original post](https://supabase.com/blog/stripe-sync-engine-transfer)