Cilantrobyte.

Tech Stacks · Frontend

Next.js

The default for serious React applications.

Category

Frontend

At the studio

Since 2020

Projects shipped

5 case studies

Status

Active

(01) Our take

Next.js is what we reach for whenever a client says "web app" and the answer is not obviously WordPress or Shopify. The App Router is a real improvement on what came before, the Vercel deployment story is the best in the business, and the hiring market for it is the deepest of any frontend framework.

That said, we treat it as a framework, not a religion. Server Components have genuine trade-offs. Route Handlers are not the Express replacement the docs imply. We write about the sharp edges publicly so our clients inherit a codebase that reflects production realities, not blog-post idealism.

(02) What we build with it

Typical work

  • B2B SaaS web applications
  • Marketing and editorial sites with real interactivity
  • Dashboards and internal tools for growth-stage teams
  • E-commerce frontends paired with headless backends

(03) How we engage

Engagement shape

Most Next.js engagements start with a two-week discovery sprint, move through a phased build of 8–16 weeks, and ship to production with Vercel previews running from sprint two.

(04) In production

Where we've shipped it

All case studies →

(05) Pairs with

Works well with

Technologies we reach for alongside Next.js in most engagements.

Frontend

React

The UI library we'd still pick today.

Frontend

TypeScript

Strict mode, no exceptions.

Frontend

Tailwind CSS

The CSS framework that finally got out of the way.

Infra

Vercel

Where we host most Next.js applications we ship.

Thinking about a Next.js project?

Start a project →back to all stacks