Stripe Data Pipeline's Postgres sync is in public preview, with Neon selectable in the Dashboard
Stripe Data Pipeline now streams Stripe API data into a Postgres database in public preview, according to Neon. Teams that sync subscription state by webhook or API could drop that code, if the sync holds up in preview.
The Engineer · Build desk
Stripe streams Stripe API data to a Postgres database, manages the sync end to end and audits the synced data. Neon can be connected from the Stripe Dashboard. Webhook teams stand up an endpoint, verify signatures and write handlers; a down endpoint can lose events.
- What's now possible capability Stripe Streams Stripe API data straight to a Postgres database and manages the sync end to end, claim 1
- What's now possible capability Stripe, ongoing audits Audits the synced data, so the developer does not have to reconcile missing or out-of-sync records, claim 16
- What's now possible capability Neon One of the destinations that can be connected directly from the Stripe Dashboard, claim 12
- What it costs cost Teams using webhooks Stand up an endpoint, verify signatures, write a handler for every event type, then maintain it, claim 8
- Who's exposed exposure Webhook endpoints If the endpoint is down or a handler errors, the event is lost along with the change it carried, claim 7
| Who | How | Kind | Claim |
|---|---|---|---|
| Stripe | Streams Stripe API data straight to a Postgres database and manages the sync end to end | capability | 1 |
| Stripe, ongoing audits | Audits the synced data, so the developer does not have to reconcile missing or out-of-sync records | capability | 16 |
| Neon | One of the destinations that can be connected directly from the Stripe Dashboard | capability | 12 |
| Teams using webhooks | Stand up an endpoint, verify signatures, write a handler for every event type, then maintain it | cost | 8 |
| Webhook endpoints | If the endpoint is down or a handler errors, the event is lost along with the change it carried | exposure | 7 |
What happened
- Stripe backfills the tables a team selects, then continuously delivers new and updated records, according to Neon.
- Setup runs through four Dashboard steps: add a Neon pipeline, choose an existing project, select tables, and click Create pipeline.
- Columns mirror the Stripe API objects, and each table also has a _raw_data column holding the complete JSON for the object.
- Neon says the sync handles any volume, so teams do not throttle requests against Stripe API rate limits.
Why it matters
- What it costs cost The saving is the webhook stack: a hosted endpoint, signature verification, and a handler per event type, all maintained by the team that wrote them.
- Who has to decide decision Neon's examples are all reads, so the choice is narrow: replace the read path for subscription state, and decide separately what to do with everything else that touches Stripe.
- Who's exposed exposure A preview-stage table behind a feature gate can lag in the direction customers notice, either locking out someone who just paid or keeping access for someone who just canceled.
Next story · Invest · Oct 2
Open USD's $468 million launch supply equals about two hours of Stripe's 2025 volumeConfirmed8 publishers
Stripe writes into the same Postgres database as the app, so the app's side of this is a query. Connect an existing Neon project and billing data is "a join away" [9]. Neon's examples assume a users table that stores each user's Stripe customer ID, and a feature gate that queries stripe.subscriptions. By Neon's account, when a trial customer is upgraded, the new subscription has already landed in that table [10].
Neon's case against the old paths is specific. An API read for one question often takes several calls [5]. Neon lists four: fetch the customer, list their subscriptions, look up the price, check the latest invoice [14]. A scheduled sync cuts the calls, but the copy is only as current as the last run [6]. Webhooks lose an event if the endpoint is down or a handler errors, and an older update processed after a newer one leaves stale state [7].
The pipeline's answer to those failures is an audit. Stripe checks the synced data on an ongoing basis, so the app does not reconcile missing or out-of-sync records itself [16].
That is a claim about behavior, and the post does not back it with a measurement. It does not include a latency figure for "real-time", a statement on how out-of-order updates are handled, or a price beyond a free start [2]. The account is Neon's. Neon is one of the destinations selectable from the Stripe Dashboard, and the post points to Stripe's docs for details [12].
Every example in the post is a read: a feature gate, an invoice history, a sales and refund aggregate, a win-back list of customers who canceled and have not resubscribed [11]. Reads are what a synced table does well. We'd run the pipeline beside the existing handlers through one billing cycle, diff the two, and delete a handler only after the table has matched it every time.
What to watch
- Whether Stripe's own Data Pipeline docs publish sync latency and out-of-order handling for Postgres destinations.
- Pricing and terms when the Postgres sync leaves public preview.
- Whether destinations other than Neon appear in the Dashboard for the Postgres sync.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence35
- Adoption
- Not scored
- Hype gap+30
- Incentives75
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Stripe Data Pipeline now supports real-time sync to Postgres: it streams Stripe API data straight to a Postgres database without needing API or webhook integrations, and Stripe manages the sync end to end.
- [2]
Real-time sync to Postgres is available in public preview, and Neon says you can get started for free.
- [3]
Stripe backfills existing data for the selected tables and continuously delivers new and updated records to the database.
- [4]
Columns mirror the Stripe API objects, and each table also has a _raw_data column with the complete JSON for the object.
- [5]
With the API approach, answering a single question often takes several calls: fetch the customer, list their subscriptions, look up the price, check the latest invoice. Each call adds latency, and rate limits must be managed as traffic grows.
- [6]
Syncing on a schedule cuts down on API calls, but the copy is only as current as the last run.
- [7]
With webhooks, if the endpoint is down or a handler errors, the event gets lost along with the change it carried; if an older update is processed after a newer one, the database ends up with stale state.
- [8]
The webhook approach requires standing up an endpoint, verifying signatures, and writing a handler for every event type you care about, then building, monitoring and maintaining that separate infrastructure.
- [9]
If you connect an existing Neon project, Stripe writes into the same Postgres database as the app, so billing data is a join away.
- [10]
In Neon's example, the users table stores each user's Stripe customer ID, and when a free-plan customer is upgraded after a trial, the new subscription has already landed in stripe.subscriptions, so the feature gate just queries the database.
- [11]
Neon's examples are reads: checking for an active subscription, showing plan, invoice history and payment status on an account page, a dashboard aggregate of daily sales volume and refunds, and a win-back list of customers who canceled and have not resubscribed.
- [12]
Neon is one of the destinations that can be connected directly from the Stripe Dashboard, and the post points readers to the Stripe Data Pipeline docs for more details.
- [13]
Creating a pipeline takes four steps: add a Neon pipeline on the Data Pipeline page in the Stripe Dashboard, choose an existing Neon project, select the Stripe tables to sync, and click Create pipeline.
- [14]
Neon's example of one billing question lists four separate API calls.
- [15]
Neon says the sync handles any volume of data, so there are no rate limits to work around and no need to throttle requests.
- [16]
Stripe audits the synced data on an ongoing basis, so the developer does not have to reconcile missing or out-of-sync records.
Sources
2 independent publishers whose own reporting we read for this story.
- databricks.comStripe Data Pipeline now syncs real-time Stripe data to Lakebase Postgres
1 article · October 15, 2026
- Sync Stripe data in real-time to Neon
neon.tech
1 article · October 16, 2026
Topics and entities
Topics
- Webhooks and APIs
- Payments Infrastructure
Entities
- Lakebase
- Stripe Data Pipeline
- Databricks
- Stripe
- Neon
- PostgreSQL