DEV Community

PubliFlow
PubliFlow

Posted on

The $0 Tech Stack That Powers a Complete SaaS Platform

When I set out to build a SaaS platform, I had two constraints: no budget and no time to waste.

After evaluating dozens of combinations, I landed on a tech stack that costs exactly $0 to run in production — while handling authentication, database, storage, payments, and deployment.

Here's the breakdown:

Frontend: Next.js 15 + TypeScript

  • App Router for file-based routing
  • Server Components for performance
  • Built-in API routes (no separate backend needed)

Styling: Tailwind CSS

  • Utility-first CSS that scales
  • Dark mode support out of the box
  • Zero runtime overhead

Backend & Database: Supabase

  • PostgreSQL database (free tier: 500MB)
  • Built-in authentication (email, OAuth)
  • Real-time subscriptions
  • Storage for file uploads
  • Auto-generated REST API

Payments: Creem / Stripe

  • One-line integration
  • Supports subscriptions and one-time payments
  • Handles taxes and compliance

Deployment: Vercel

  • Push to deploy from GitHub
  • Free tier includes SSL, CDN, and edge functions
  • Preview deployments for every PR

The Result: PubliFlow SaaS Starter Kit

I packaged everything into a production-ready starter kit that includes:

  • ✅ Authentication (sign up, login, OAuth)
  • ✅ Dashboard with data visualization
  • ✅ Payment integration (subscriptions + one-time)
  • ✅ Landing page template
  • ✅ Email templates
  • ✅ SEO optimization
  • ✅ One-command deployment

The goal: Go from git clone to paying customers in 7 days, not 7 weeks.

👉 Check it out: PubliFlow


What's your go-to SaaS stack? Drop it in the comments — I'm always looking to learn from what works for others.

Top comments (2)

Collapse
 
aditya_sorathiya_069252f4 profile image
Aditya Sorathiya

I found a ui bug on your site

I tried to zoom out I that happened

Collapse
 
publiflow profile image
PubliFlow

Zooming out is a classic way to expose hidden responsive layout flaws, especially when containers rely on fixed pixel widths instead of relative units. I need to track down which specific media query is failing to handle that extreme viewport scaling. Could you let me know which browser and screen resolution you were using when the UI broke? That context will help me isolate and fix the overflow issue much faster.