Pattern-level, not code-level
Indie SaaS tool integration patterns.
Pattern-level integration deep dives for common indie SaaS tool pairs — Stripe+Supabase, Resend+Next.js, Cal.com+Stripe, Supabase+Vercel, Stripe+Beehiiv, Stripe+Loops, Tally+Supabase. Each page covers what each tool owns, the integration shape, implementation steps with gotchas, and when NOT to build the integration.
Stripe + Supabase integration
Stripe + Supabase is the dominant indie SaaS payment + database integration. Stripe owns checkout and subscription state; Supabase owns user identity and product state. The integration glue is a webhook handler that reflects Stripe events into Supabase tables.
Resend + Next.js integration
Resend + Next.js is the modern indie SaaS transactional-email stack. Resend provides the API and deliverability; Next.js Server Actions or Route Handlers call the API; React Email templates render JSX into HTML emails. Three-line setup once the domain is verified.
Cal.com + Stripe integration
Cal.com + Stripe is the indie SaaS pattern for paid scheduling (coaching calls, consultations, paid meetings). Cal.com handles the calendar logic; Stripe handles the payment. The integration sits at the booking-creation moment.
Supabase + Vercel deployment pattern
Supabase + Vercel is the dominant indie SaaS hosting stack. Supabase provides the database, auth, and storage; Vercel provides the Next.js hosting with preview deployments. The integration sits at environment variables and migration workflow.
Stripe + Beehiiv (paid newsletter) integration
Stripe + Beehiiv is the dominant paid-newsletter stack as of 2026. Beehiiv has native Stripe integration; the operator connects Stripe via OAuth and Beehiiv handles subscription state, paid-content gating, and customer portal access.
Stripe + Loops integration (event-driven email)
Stripe + Loops is the event-driven indie SaaS email pattern. Stripe fires events (customer created, subscription updated, payment failed); a webhook bridge syncs the events into Loops as contact properties; Loops triggers email sequences based on the properties.
Tally + Supabase integration (form responses)
Tally + Supabase is the pattern for capturing form data into your application database. Tally hosts the form; Supabase stores the responses. The bridge is a Tally webhook that fires on submission and writes a row to Supabase.
See the stack these tools come from
The integrations here apply within the named-tool stack recommendations. The stack pages tell you which tools to use together; the integration pages tell you how.