Answer 3 questions. Get a specific, opinionated recommendation — with setup commands, trade-off analysis, and two alternatives.
Step 1 of 3
What are you building?
Pick the category that best describes your project.
Step 2 of 3
What matters most to you?
Pick your top 1–2 priorities for this project.
Select 1 or 2 that best describe your situation.
Step 3 of 3
Your experience level?
Be honest — it helps us pick the right tool for where you are now, not where you want to be.
Recommended Stack
🏗️ Stack Components
🚀 Get Started
🔀 Alternatives worth knowing
Share this recommendation:
← Start over with different choices
Common tech stack questions
What tech stack should I use for a web app?
For most web apps in 2025, Next.js + PostgreSQL (via Supabase) + Vercel is the fastest path to production. It handles routing, server-side rendering, API routes, and auth in one framework. If you want more backend separation, Next.js + tRPC + PostgreSQL + Fly.io is a strong production setup. For solo developers shipping fast, Supabase handles your database, auth, and storage in one service.
What is the best tech stack for a startup?
The best stack is the one you can ship fastest with. Next.js + Supabase + Vercel is the current default for early-stage web startups — minimal infrastructure decisions, excellent free tiers, scales reasonably well. Once you have product-market fit, you can migrate databases or switch infrastructure. Don't optimize prematurely.
Should I use SQL or NoSQL?
Default to PostgreSQL unless you have a specific reason not to. It handles the vast majority of use cases, has excellent free hosting (Supabase, Neon, Railway), and you'll never regret choosing it. MongoDB makes sense for highly variable document structures or very rapid prototyping. Redis is for caching — not primary storage.
What backend framework should I use in 2025?
For Node.js: Express (battle-tested, huge ecosystem), Hono (fast, edge-ready, excellent DX), or NestJS (large teams, enterprise). For Python: FastAPI — modern, typed, auto-generates OpenAPI docs. For Go: Gin or Echo — excellent performance for high-throughput APIs. The framework matters less than your language fluency.
What is the best hosting for a side project?
Vercel for Next.js/frontend, Fly.io for containers/backends (generous free tier), Railway for simplest Dockerfile deploys, Render for good free tier on small projects, Cloudflare Pages/Workers for global edge. Avoid AWS/GCP/Azure for side projects — the complexity isn't worth it until you need enterprise features.
TypeScript or JavaScript?
Use TypeScript. The upfront cost of adding types pays back immediately when refactoring. Every major framework has excellent TypeScript support. The only exception: quick one-off scripts where you'll never touch the code again.
React, Vue, or Svelte?
React has the largest ecosystem and job market — safe default for anything team-maintained. Vue is more approachable, great docs, smaller but solid ecosystem. SvelteKit compiles to smaller bundles, excellent DX, but smaller ecosystem. For personal projects where you want to learn, try SvelteKit. For production or team projects, React is the safe call.
What is the best stack for a REST API?
For fast development: Node.js + Hono or Python + FastAPI. For performance at scale: Go + Gin or Rust + Axum. FastAPI is particularly strong because it auto-generates OpenAPI docs, has excellent async support, and Python's ecosystem is unmatched for data-heavy APIs.