Skip to content
NEW v0.2.0 — Tracks, roadmaps and tiered stacks
STACK IT FIRST
Install the skills
Browse the site
01 · Web · Roadmap

Four questions, one stack.

A 4-question roadmap for choosing a web architecture an AI agent builds well in. Every answer is explained; every path ends on a stack.

Interactive roadmap

Stage 1 of 2Where are you?

Do you have paying users, or more than two people shipping to this codebase?

Until money or a second pair of hands is involved, the cheapest mistake is over-building. One person can hold the whole app in their head and let the agent rewrite freely. Once others depend on it, every change needs a contract the agent can check against.
Stage 1 of 2

Where are you?

The tier is about how much has to keep working while an agent changes things, not about budget. Answer for the product as it is today, not as you hope it will be in a year.
Stage 1 · Q1

Do you have paying users, or more than two people shipping to this codebase?

Why this matters

Until money or a second pair of hands is involved, the cheapest mistake is over-building. One person can hold the whole app in their head and let the agent rewrite freely. Once others depend on it, every change needs a contract the agent can check against.

yes
Stage 1 · Q2

Do you need multiple regions, a compliance audit, or six or more engineers working in parallel?

Why this matters

These three all force the same thing: explicit boundaries. Regions need data locality rules, audits need traceable change, and parallel teams need modules that do not step on each other. If none applies, a single well-typed app on managed services is still the fastest thing an agent can work in.

yes Tier

Scale

Typed service boundaries, an API contract as the source of truth, and boring infrastructure.
no Tier

Growth

Managed Postgres, real auth and billing, and tests the agent runs before every change.
no Tier

MVP

One deployable, free tiers, and a codebase small enough for an agent to read end to end.
Stage 2 of 2

What are you building?

The profile decides where the complexity lives: in the pages, in the account model, or in one focused workflow. That in turn decides which framework an agent should be reasoning in.
Stage 2 · Q1

Will organic search be the main way people find this?

Why this matters

SEO changes the rendering model. Pages must be complete HTML at request time, fast, and cheap to generate in the thousands. Content-first frameworks make that the default, so the agent never has to fight hydration or caching to get a page indexed.

yes Profile

SEO-driven

Content and search-driven sites: marketing, docs, directories, editorial.
no
Stage 2 · Q2

Do users sign in and pay for it?

Why this matters

Accounts, billing and per-user data are where most web apps grow their complexity. If the answer is yes, pick a full-stack framework with well-trodden auth and ORM patterns; the agent has seen those thousands of times. If not, you are building a tool and can skip most of that machinery.

yes Profile

SaaS

Logged-in products with accounts, billing, and per-user data.
no Profile

Tool

Single-purpose utilities and internal apps where one workflow matters.
Result

Tier × profile.

Stage 1 picks the row, stage 2 picks the column. Each cell is a stack with a rule you can install.
Tier SEO-driven content & search SaaS logged-in product Tool utility & internal
01 MVP Ship it Astro + Tailwind + Cloudflare Pages 5/5 Next.js + Drizzle + Supabase 5/5 Vite + React + Hono on Cloudflare Workers 4/5
02 Growth Charge for it Astro SSR + Postgres on Cloudflare 5/5 Next.js + Prisma + Postgres 5/5 SvelteKit + Drizzle + Postgres 4/5
03 Scale Run it for many Next.js + Postgres + edge caching 4/5 Next.js front, NestJS + Postgres + Redis back 4/5 Go + Postgres + React 4/5