February 10, 2026
No-webhooks? Webhooks in disguise
Show HN: Stripe-no-webhooks – Sync your Stripe data to your Postgres DB
Plug-and-play Stripe syncing to your DB—then HN roasted the name and an auth outage
TLDR: A new tool syncs Stripe billing to your own database and auto-handles notifications. The crowd loved the convenience but mocked the “no webhooks” name, worried about price-change complexity, and watched a demo stumble under an auth outage—proving demand is real, but billing is still messy.
A new Show HN drop promises to make Stripe payments less painful: “stripe-no-webhooks” lets you define plans in code, auto-syncs products and prices to Stripe, and keeps your data mirrored in your own Postgres database (that’s just a fancy word for a data box). It even handles Stripe’s “webhooks” (automatic messages Stripe sends to your app) so you don’t have to wire them up yourself. The creator shared a demo at snw-test.vercel.app, but launch day drama hit fast when the auth provider Clerk had issues, confirmed by Downdetector—cue the popcorn.
Comments split into two camps. Fans loved the “finally, local Stripe data” angle, noting Stripe’s APIs can feel slow; one dev plugged their forecasting app and backed the idea with “APIs can be slow” (repo). Skeptics went straight for the name: “Stripe-no-webhooks”… that still uses webhooks under the hood? The roast wrote itself: “wait for it… webhooks.” Practical questions flew in too—“How do you change prices?”—because billing tweaks, upgrades, downgrades, and credits are where things break hearts and bank accounts. Someone dropped webhookdb as a broader alternative, hinting this might be part of a larger trend: syncing third‑party data into your own database. The vibe? Half applause for convenience, half side-eye for marketing spin, with a bonus launch hiccup for meme fuel.
Key Points
- •stripe-no-webhooks abstracts Stripe webhook handling and syncs Stripe data to a PostgreSQL database.
- •The library offers APIs for subscriptions, credits, wallet balances, top-ups, and usage-based billing, with support for taxes and seat-based billing.
- •Installation initializes environment variables and generates config, billing client, and webhook/API route files for a Next.js app.
- •Developers define plans in billing.config.ts, run DB migrations, and sync to Stripe to create products and prices with IDs saved to config.
- •Testing involves running the app and using the Stripe CLI to forward webhooks; the library provides a pricing page and checkout() helper with test card details.