Stacks

Pick the simplest stack that proves your idea works. Add complexity only when you need it.

Why start simple?

Every technology you add is a decision you're committing to. Databases need migrations. Auth needs security reviews. APIs need documentation. If you don't need them yet, don't add them yet.

The goal is to prove value fast, then upgrade deliberately when the proof justifies it.

A

Next.js Only

Validate the idea. No backend complexity.

Includes

  • Next.js 16+ with App Router
  • Tailwind CSS 4
  • shadcn/ui components
  • Mock data and static content

Use when

  • →Testing if the concept works
  • →Validating UI/UX with stakeholders
  • →Marketing sites and landing pages
  • →Demos and presentations

Avoid

  • Adding a database 'just in case'
  • Setting up auth before you need it
  • Building API routes prematurely
B

Next.js + Supabase

Real users. Real data. Still simple.

Includes

  • Everything in Stack A
  • Supabase for auth and database
  • Row-level security (data protection)
  • Real-time updates
  • File uploads and storage

Use when

  • →Users need to log in
  • →Data needs to persist between sessions
  • →You need real-time features
  • →Users upload files

Avoid

  • Complex business logic in the database
  • Heavy third-party integrations
  • Background jobs that run for minutes
C

Next.js + Laravel

Complex backend. Full control.

Includes

  • Everything in Stack A
  • Laravel API backend
  • Queues and background jobs
  • Custom API design
  • Advanced caching and performance

Use when

  • →Complex business rules that don't fit in Supabase
  • →Many third-party API integrations
  • →Background processing (emails, reports, syncs)
  • →Custom auth requirements

Avoid

  • Over-engineering simple CRUD apps
  • Choosing Laravel when Supabase would do

Quick decision

A

No login? No saved data? → Stack A

B

Users + database + standard features? → Stack B

C

Complex logic? Many integrations? → Stack C

How stacks evolve

Most projects start at A and advance when the proof justifies it.

AB

Most common

Prove the concept first, then add users and persistence once you're confident it's worth building.

AC

Skip the middle

If you know you need Laravel from day one (complex integrations, heavy backend), skip Supabase entirely.

B → C is involved. If you start with Supabase and later need Laravel, you'll need to migrate your data. Plan carefully before choosing B if there's a strong chance you'll need stack C for a complex back-end.

Ready to start?

Find the right next step based on where you are now.

What Next