The Stack I Use to Build Everything: Next.js, Supabase, and n8n

One stack to rule them all

I build a lot of things. Marketing platforms, SaaS products, internal tools, client dashboards, this website. At some point I made a decision that changed how quickly I could ship: I would use the same stack for everything.

That stack is Next.js for the frontend and backend, Supabase for the database and authentication, n8n for workflow automation, and Vercel for hosting. Every single project starts from this foundation.

People ask me why I do not use the "best" tool for each job. The honest answer is that the best tool is the one you know inside out. Context-switching between different frameworks, databases, and hosting platforms is a hidden cost that most people massively underestimate.

Next.js: The workhorse

Next.js handles both the frontend and the API layer for all my projects. I use the App Router with TypeScript in strict mode. Every project follows the same folder structure, the same naming conventions, the same patterns.

This means I can jump between projects without that 20-minute "where was I" adjustment period. It also means any developer I bring in can work across multiple projects without learning a new codebase each time.

The specific things I rely on:

• Server components for fast initial loads and SEO
• API routes for backend logic without needing a separate server
• ISR (Incremental Static Regeneration) for content that changes occasionally but does not need to be real-time
• Middleware for authentication checks and redirects

Is Next.js perfect? No. The documentation can be confusing, the versioning is aggressive, and some features feel half-baked when they launch. But it is mature enough, fast enough, and flexible enough for everything I need.

Supabase: The database layer

I moved to Supabase about two years ago and I am not going back. It gives me a Postgres database with a REST API, real-time subscriptions, authentication, and file storage, all in one place.

For most of my projects, the Supabase setup is straightforward:

• Tables for the core data
• Row Level Security policies to control access
• Edge Functions for server-side logic that needs to run close to the user
• Real-time subscriptions for features that need live updates

The thing I appreciate most about Supabase is that it is just Postgres underneath. If I ever need to migrate, my data is in a standard database format. There is no vendor lock-in beyond the convenience features.

n8n: The glue

If Next.js is the face and Supabase is the brain, n8n is the nervous system. It connects everything together.

n8n is a workflow automation platform that I self-host. It handles all the "when X happens, do Y" logic across my businesses. Some examples:

• When a new lead fills out a form on a Byter client website, n8n adds them to HubSpot, sends a welcome email, and notifies the sales team
• When a blog post is published on any of my sites, n8n generates social media posts, updates the sitemap, and pings search engines
• When a property deal passes initial screening at Red Cardinal, n8n pulls comparable data and generates an investment memo

I have over 60 active workflows. The visual builder makes it easy to see what is connected to what, and the error handling is solid enough that I trust it to run unattended.

Vercel: The deployment layer

Every Next.js project deploys to Vercel. Push to main, it goes live. No CI/CD pipeline to maintain. No server to manage. No deployment scripts to debug at midnight.

The preview deployments are useful too. Every pull request gets its own URL, so I can review changes before they hit production. For client projects, this means they can see updates before we ship them.

Why this matters for your business

You do not need to use my specific stack. The principle matters more than the tools. Pick a stack. Learn it deeply. Use it for everything until you hit a genuine limitation that forces you to look elsewhere.

The businesses that ship fast are not the ones using the fanciest technology. They are the ones that have eliminated decision fatigue around tooling and can focus their energy on the actual product.

Every hour you spend debating whether to use PostgreSQL or MongoDB, React or Vue, AWS or Vercel, is an hour you are not spending on the thing your customers actually care about.

The cost

People assume this kind of setup is expensive. Here is what I actually pay:

• Vercel: Pro plan, around 20 dollars a month per project
• Supabase: Pro plan, 25 dollars a month
• n8n: Self-hosted on a small server, about 10 dollars a month
• Domain names: 10-15 dollars per year each

For under 100 dollars a month, I have a production-grade setup that handles thousands of users across multiple businesses. Try getting that from a traditional development agency.

Getting started

If you are building something new, here is my advice: start with Next.js and Supabase. Get a basic project running. Deploy it to Vercel. Then add n8n when you need to connect external services.

Do not over-engineer it. Do not add tools you do not need yet. Build the simplest thing that works, then improve it when you have real users giving you real feedback.