Next.js 16, Tailwind v4, server components, the edge runtime — what should you actually build a web product with in 2026?
Next.js 16's proxy, server actions and standalone build pipeline reshaped the 2024–2025 ecosystem. We share the decisions we made building a real product on the new stack.
Server components shine when used in the right places, not everywhere.
Tailwind v4's CSS-variable-first approach made design tokens feel native. You can now define your theme in globals.css alone, no tailwind.config.js — simpler and more flexible.
Server components are a major win, but they shouldn't be everywhere. Form inputs, animation, third-party widgets still belong in client components. Drawing the line correctly is the difference.
We shipped dozens of LLM-backed products. Which patterns scaled, which collapsed — field notes from production.
The technical details of dropping a $48K/month AWS bill to $15K.
