blog/stripe sync engine donation title update (#44862)

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Blog post title update

## What is the current behavior?

Blog post titled "Stripe Sync Engine: from supabase to stripe" at
/blog/stripe-sync-engine-donation.

## What is the new behavior?

- Title updated to "We're transferring the Stripe Sync Engine to Stripe"
- Description updated to match new framing
- Slug changed to stripe-sync-engine-transfer
(/blog/stripe-sync-engine-transfer)
- Image directory renamed to match new slug

## Additional context

N/A


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Published a blog post announcing the transfer of the Stripe Sync
Engine repository to its upstream maintainer, with full metadata and
narrative covering timeline, continuity guarantees, licensing (Apache
2.0), redirects, and continued one‑click dashboard support. It lists new
capabilities (coupons sync, branching support, immediate sync on
install, one‑click upgrades, SSL enforcement, restricted admin controls,
improved install UX, clearer errors, and dashboard visibility of
function source).
* Updated the public blog RSS feed to include the new post and recent
entries.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Ana <ana1337x@users.noreply.github.com>

apps/www/_blog/2026-04-14-stripe-sync-engine-transfer.mdx

@@ -0,0 +1,65 @@
+---
+title: "We're Transferring the Stripe Sync Engine to Stripe"
+description: "We're transferring the Stripe Sync Engine from supabase/stripe-sync-engine to stripe/sync-engine"
+author: raminder_singh, matt_linkous, gregor_vand, ana_mogul
+imgSocial: stripe-sync-engine-transfer/og.png
+imgThumb: stripe-sync-engine-transfer/thumb.png
+categories:
+  - company
+tags:
+  - stripe
+  - postgres
+  - open-source
+date: '2026-04-14'
+toc_depth: 2
+---
+
+In 2021, we open-sourced the Stripe Sync Engine repo to solve a problem we had ourselves. 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`](https://github.com/supabase/stripe-sync-engine) to [`stripe/sync-engine`](https://github.com/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](https://stripe.com/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.
+
+Both teams kept iterating after launch on reliability, install flows, and expanded Stripe object support. The result is a more stable, more capable integration than either team would have shipped alone.
+
+Moving the repo to `stripe/sync-engine` is the next step in that collaboration, and both teams will keep building it together. All our changes going forward will be made to the new `stripe/sync-engine` repo.
+
+## What changes for you
+
+The Stripe Sync Engine stays open source under the Apache 2.0 license. The `supabase/stripe-sync-engine` repo will redirect to `stripe/sync-engine`. Nothing breaks for existing users. The one-click integration in the Supabase dashboard continues to work as before.
+
+This is how Supabase has always worked. We build in the open, support the tools and communities around us, and contribute back as things grow. We are proud to collaborate with companies like Stripe to deliver the best tech for builders.
+
+## What's new
+
+Alongside the transfer, the latest release includes improvements to reliability and day-to-day management.
+
+New capabilities:
+
+- Coupons sync, one of the most requested additions
+- Branching support, so you can install the engine on a branch for safer dev workflows
+- Data starts syncing immediately on install, no need to wait for the first cron cycle
+
+Better management:
+
+- One-click upgrades for existing installations
+- SSL enforcement now supported (previously a blocker for projects with SSL enforcement turned on)
+- Install and uninstall controls restricted to Admins and Owners to prevent partial installs
+
+Reliability and UX:
+
+- Smarter install flow: buttons auto-reset if a process gets stuck
+- Clearer, more actionable error messages
+- Edge Function source code now visible directly in the dashboard
+
+## Get started
+
+With your Stripe data in Postgres, you can join it directly with your application data. Useful for operational decisions like feature gating and subscription checks, and analytical queries like calculating MRR or understanding churn. For a full walkthrough with SQL examples, see [Sync Stripe Data to Your Supabase Database in One Click](https://supabase.com/blog/stripe-sync-engine-integration).
+
+The Stripe Sync Engine is available from the [Integrations section of your Supabase dashboard](https://supabase.com/dashboard/project/_/integrations/stripe_sync_engine/overview). The repo is at [github.com/stripe/sync-engine](https://github.com/stripe/sync-engine).

apps/www/public/rss.xml

@@ -4,9 +4,23 @@
       <link>https://supabase.com</link>
       <description>Latest news from Supabase</description>
       <language>en</language>
-      <lastBuildDate>Thu, 02 Apr 2026 00:00:00 -0700</lastBuildDate>
+      <lastBuildDate>Tue, 14 Apr 2026 00:00:00 -0700</lastBuildDate>
       <atom:link href="https://supabase.com/rss.xml" rel="self" type="application/rss+xml"/>
       <item>
+  <guid>https://supabase.com/blog/stripe-sync-engine-transfer</guid>
+  <title>We&apos;re Transferring the Stripe Sync Engine to Stripe</title>
+  <link>https://supabase.com/blog/stripe-sync-engine-transfer</link>
+  <description>We&apos;re transferring the Stripe Sync Engine from supabase/stripe-sync-engine to stripe/sync-engine</description>
+  <pubDate>Tue, 14 Apr 2026 00:00:00 -0700</pubDate>
+</item>
+<item>
+  <guid>https://supabase.com/blog/custom-oauth-oidc-providers</guid>
+  <title>Custom OIDC Providers for Supabase Auth</title>
+  <link>https://supabase.com/blog/custom-oauth-oidc-providers</link>
+  <description>Connect any OpenID Connect identity provider to your Supabase project: GitHub Enterprise, regional providers, and more.</description>
+  <pubDate>Wed, 08 Apr 2026 00:00:00 -0700</pubDate>
+</item>
+<item>
   <guid>https://supabase.com/blog/100000-github-stars</guid>
   <title>100,000 GitHub stars</title>
   <link>https://supabase.com/blog/100000-github-stars</link>