The Default Stack
Every client site we build at Operon E2I starts from the same foundation: Next.js 14+ with the App Router, deployed on Vercel, with SendGrid for transactional email and Stripe for payments when needed. This isn't dogma — it's a set of defaults we've stress-tested across a dozen production sites and found consistently reliable.
Why Next.js App Router Specifically
The App Router — introduced in Next.js 13 and stable in 14 — changes the mental model from 'pages with data fetching' to 'server components by default, client components where needed.' For a typical small business site, this means:
Faster initial load. Server components render on the server and send HTML to the browser. No JavaScript bundle needed for static content, no hydration delay. A well-built App Router site scores 95+ on Core Web Vitals without heroic optimization.
Simpler data fetching. async/await directly in server components replaces the getStaticProps / getServerSideProps mental model. For sites pulling from a CMS or an API, this is significantly cleaner code.
Route handlers instead of a separate API. Files at app/api/route.ts handle form submissions, webhook ingestion, and Stripe callbacks without needing a separate Express server. One repo, one deployment.
Why Vercel
Vercel's edge network, preview deployments on every pull request, and zero-config Next.js support make it the obvious choice for Next.js projects. The free tier covers most small business sites. When sites scale, the cost scales proportionally.
The one real risk: vendor lock-in on some features (Edge Middleware, ISR implementation details). For most clients this is a non-issue, but we document the escape hatch to self-hosted Next.js if they ever need it.
When We Don't Use This Stack
Pure static brochure sites with no forms and no dynamic content: we'll sometimes use Astro instead. It's leaner, generates no client-side JavaScript by default, and is easier for a non-developer client to understand.
Heavy e-commerce: we point clients toward Shopify rather than building custom cart logic. The platform handles inventory, checkout compliance, and payment processing better than anything we'd build from scratch at a small-business budget.
Internal tools and dashboards: Next.js still, but with a different set of UI primitives (shadcn/ui, Recharts) and a Postgres database instead of file-based content.
The Practical Takeaway
If you're a small or mid-size service business in the Central Valley and you're evaluating a website rebuild, the technology stack matters less than whether the team building it understands local SEO, conversion optimization, and reliable hosting. The stack we use happens to produce fast, maintainable sites — but 'built on Next.js' is not a differentiator by itself.
Talk to us about your site at /contact if you want an honest assessment of what your current setup is costing you.