Interactive guide · 2026 edition

Backend Tech Stacks, Visualised

A mind-map view of the modern backend universe — languages, BaaS platforms, hosting, and every supporting service. Pick your stage, filter by what matters, and see exactly what stack fits.

/ search 1-4 stage Esc reset

The landscape at a glance

— · click a node to jump to its card

Which stage are you at?

Pick one — the stack below adapts, and cards fade to only what fits.

All technologies

Decision cheat-sheet

Pick by team situation

  • Solo founder: Next.js + Supabase on Vercel, or Rails 8 on Hetzner with Kamal.
  • Small TS team: Hono/Fastify on Cloudflare or Vercel, Neon, Clerk, Inngest, Sentry.
  • AI-first product: FastAPI + Postgres (pgvector) on Railway/Fly + Anthropic/OpenAI.
  • High-throughput API: Go (Gin/Fiber) or Rust (Axum) on Fly/Cloud Run.
  • Realtime / collab: Phoenix, Convex, or Supabase realtime.
  • Enterprise / regulated: Spring Boot or .NET on AWS/Azure, Auth0/WorkOS.

Pick by constraint

  • Zero ops: Supabase + Vercel. No regrets for year one.
  • Lowest bill: Hetzner VPS + Coolify/Dokploy + Postgres container.
  • Global low latency: Cloudflare Workers + D1/R2, or Fly multi-region.
  • Can't lose data: Managed Postgres with PITR — never DIY your primary DB early.
  • Future compliance: Stay on AWS/GCP/Azure (directly or via Vercel/Supabase).

Anti-patterns to avoid

  • Starting on Kubernetes without a platform team.
  • Picking BaaS just to dodge learning SQL — you'll hit the wall.
  • Microservices before product-market fit.
  • Chasing the framework of the month. Boring tech wins.
  • Free-tier roulette — know the paid price before you build.
Tweet Reddit LinkedIn Star on GitHub