Should I use Vercel or AWS for hosting a Next.js SaaS app with 10K monthly users and a team of 2?

Council notes

Evidence boundary

Observed from your filing

• Should I use Vercel or AWS for hosting a Next.js SaaS app with 10K monthly users and a team of 2?

Assumptions used for analysis

• Next.js App Router or Pages Router architecture without heavy custom server requirements
• 10K monthly users generating ~500K-1M page views/month (typical SaaS browsing pattern, not API-heavy)
• No hard requirement for persistent WebSocket connections at launch
• Team of 2 with limited DevOps experience — operational simplicity outweighs marginal cost savings
• Vercel Pro pricing remains stable at $20/seat/month with current included limits (1TB bandwidth, 1M serverless invocations)
• current scale defaulted: moderate scale assumed (not_addressed)
• existing stack defaulted: greenfield assumed (not_addressed)

Inferred candidate specifics

These details were introduced by the Council during analysis. They were not supplied in your filing.

• Stay on Vercel Pro ($40/month for 2 seats). For 10K monthly users generating ~500K-1M page views/month, Vercel Pro's included limits (1TB bandwidth, 1M serverless invocations) are sufficient. Total infrastructure cost: ~$90/month (Vercel Pro $40 + Neon Postgres $19 + Upstash Redis $10 + Cloudflare R2 ~$0 + misc ~$20). Critical architectural rule: DO NOT use Vercel KV, Vercel Postgres, Vercel Blob, or Vercel Cron. Use external providers (Neon, Upstash, Cloudflare R2, GitHub Actions). This preserves the 1-week reversibility constraint — your data layer stays platform-independent. Re-evaluate at 50K monthly users or $150/month Vercel spend. At that threshold, migrate to AWS via SST (~20 hours setup), where ~$60-80/month savings justify migration within 6 months. Key failure modes: (1) If you need WebSockets, add Railway/Fly.io ($0-5/month) from day one — Vercel doesn't support persistent WebSockets. (2) If cold starts exceed 3s on critical routes, use Vercel Edge Functions (<50ms cold start) instead of Node.js serverless functions (1-3s cold start).
• Set up Vercel Pro with 2 seats, provision Neon Postgres (free tier → $19/month plan), Upstash Redis ($10/month), and Cloudflare R2 (free tier), then configure environment variables in Vercel to point all data services to these external providers instead of any Vercel-native data products.
• Branch b006 had the highest raw confidence (0.95) but is a [reframe] branch — it describes a principle ('platform-independent core pattern') without naming specific providers, costs, or migration thresholds. It is structurally disqualified as the winner because it produces no actionable deployment plan. Branch b003 (0.92 confidence) operationalizes the exact same principle with specific dollar amounts ($90/month total), named providers (Neon, Upstash, R2), concrete migration thresholds (50K users or $150/month), and two specific failure modes with mitigations. b003 survived 3 rounds of adversarial debate — strengthened by both gpt and opus in rounds 2 and 3, and split-examined by glm. It is the clear implementation winner.
• Hybrid Vercel + AWS Lambda from day one
• Killed in round 1. Two deployment pipelines, two logging systems, two billing dashboards create cognitive overhead that dominates costs for a 2-person team. Realistic hybrid cost is $120-240/month vs $90/month all-in on Vercel + external services. Adds 20-80ms latency per cross-provider hop for zero benefit at 10K MAU. The branch's own failure modes (needing DevOps specialist, debugging complexity) contradict its thesis.
• AWS Elastic Beanstalk or AWS Amplify for cost control and flexibility
• Branch b002 offered two recommendations without committing to either. Vercel Pro at this scale is cheaper ($40/month vs $50-150/month for AWS) and requires near-zero DevOps. The 'longer-term flexibility' benefit is already captured by b003's migration plan at 50K users via SST, making early AWS adoption premature optimization.
• Railway, Fly.io, or unspecified hybrid approach

Inferred specifics table

Structured audit rows for Council-added details. Synthetic basis means the detail was introduced by analysis, not supplied by the filing.

Unknowns blocking a firmer verdict

• Vercel Pro pricing ($20/seat/month) may change — Vercel has adjusted pricing tiers historically, which could alter the cost-benefit threshold
• The 50K user / $150 monthly spend migration threshold is a heuristic, not validated against specific SaaS traffic patterns — actual migration timing depends on API-heavy vs static-heavy workload mix
• SST's '20 hours to migrate' estimate is community-sourced and varies significantly by app complexity, middleware usage, and ISR/SSR patterns
• Cold start impact (1-3s) depends heavily on function bundle size and whether the team uses tree-shaking effectively — actual cold start times at 10K MAU are untested for this specific app

Operational signals to watch

Branch battle map