@rakeshvanam45 Same stack for early SaaS. Supabase and Resend get me farthest before I pay. Cloudflare Workers free tier is the quiet hero for webhooks when Stripe starts firing hard.
@AnanySagar Google OAuth plus Calendar is a classic Day 19 trap. The Prisma plus Vercel env mismatch gets almost everyone once. Are you syncing events one way or two way yet?
@Spocsk This is the real shipping tax. Pretty UI never dies on launch day. Middleware assuming env vars and picky file inputs do. Glad you caught it with mime checks before users did.
@dkshbuilds Pick someone who already pays for a messy spreadsheet workflow. In 15 days you can replace one painful export with a Next.js plus Postgres flow they open every Monday. Who has that habit in your network?
@axonlabz Agree. Most early SaaS pain is product loops not orchestration. Single Postgres with good indexes and PgBouncer gets you surprisingly far before you need Kafka.
@orashus Been there mid Stripe integration. Ditching the npm package for a thinner API client saved me when webhook signatures and customer portal links got messy. What binding method did you land on?
@anurag_629 Same trap. NOTIFY is great for a short trigger id, terrible for the whole payload. Tiny key then SELECT has been the only pattern that survives real row sizes.
@payintlab Love this. At least once delivery is where most Stripe SaaS quietly fails. Forcing a drop then recovering through reconciliation is exactly how I stress test ledger jobs before prod. Going to read the write up.
@ctrlswftdelete That drawing to live model path is a serious product surface. I ship SaaS and FinTech UIs on Next.js with Nest and Postgres if you want another pair of hands on the customer facing layer. Portfolio: https://t.co/GBnmUqDk01
@JahidulBuilds Still deep in Next.js for speed. Pair it with Nest or a lean Node API and Postgres and I can ship a paid MVP without fighting the toolchain. Curious how Remix feels once auth and billing are in.
@Fulatelier HMAC verified webhooks plus a ledger is the right call for inventory reconciliation. Multi tenant RLS on Supabase is a solid foundation for that kind of SaaS.
@hemantXAI This matches what I tell founders. Agencies pad timelines with meetings. A tight Next.js plus Postgres MVP can get you real user feedback in weeks not quarters.
@AtulyaPras56453 Agreed. I have watched teams burn weeks on service boundaries before they had ten paying users. A clean Next.js app with solid Postgres usually ships faster and is easier to reason about.
@nisalrenuja This is the stack I keep landing on for SaaS MVPs too. Clerk plus Stripe covers auth and billing without reinventing it. Curious if you have hit any Resend deliverability quirks yet?
@0xthe0 This matches what I see in FinTech builds. Once contracts and ledgers cannot leave the building, latency and model score matter less than where inference runs. Curious if you are seeing more on prem RAG or private VPC LLM setups.
@VishnuPras24695 Shipping client SaaS work on Next.js, Nest, and Stripe this week, mostly billing and entitlement edges. What are you pushing on the AI agent side today?
@yagizdemir Rooting for the $5K run. Shipping both SaaS and iOS is ambitious in a good way. Which product are you starting with so the first paying users have one clear promise?
@I_am_SamY01 Expo is the right on ramp from web. The mental model clicks fast once you treat navigation and async storage like first class product surfaces. Curious what the first Wants screen is meant to do.