§ Maintenance · Next.js
Next.js maintenance, monthly, in writing.
Next.js moves faster than almost any other production framework in this stack. A major version every twelve months, an app router that has redefined the data-fetching model twice, and a deployment surface that talks to Vercel, Cloudflare, AWS, and your own Node. Kebehut keeps a Next.js app current and shipping while you focus on the part that earns.
§ Where Next.js is today
Current version & release cadence.
- Current
- Next.js 15 (stable)
- Cadence
- Major every ~12 months; minors monthly; patches multiple per week.
- As of
§ Where this stack hurts
Specific maintenance pains for Next.js.
-
App-router contract drift
The app router has changed default caching behavior, RSC streaming semantics, and middleware contracts across recent versions. Apps that worked on 13.4 break in subtle ways on 14 and 15 — silent caching, broken middleware, mismatched RSC bundles.
-
Dependency tree gets out of date fast
Next.js drags React, the React DOM, the React Server Components runtime, the Webpack or Turbopack chunks, and the Vercel adapters with it on every major. Falling more than one major behind makes the upgrade exponentially harder.
-
Deploy-only bugs that don't appear in dev
Next.js production builds optimize differently than dev. Issues with module resolution, edge runtime mismatches, environment variable hoisting, and image optimization typically surface only in production — exactly where they hurt most.
§ What Kebehut does, by tier
The shape of work for Next.js.
- Each month we read the current Next.js release notes against your app, mark which patches affect you, and write the result up.
- Ship the patch upgrades and low-risk minor bumps in writing, with PRs against your repo and the migration steps documented inline.
- Drive a full major upgrade — app router migration, RSC behavior shifts, edge runtime moves — across a heavy quarter, with rollback paths.
Recommendation
Baseline: Basic.
Bump up for: Bump to Pro for the month you ship the next minor; bump to Enterprise for a major upgrade quarter.
§ FAQ
Questions, briefly answered.
- We're still on Next.js 12. Can Kebehut bring us current?
- Yes, but not in one month. The path is: Basic for one month to map the current state and pick the upgrade route; then Pro or Enterprise for the upgrade months themselves. We do not push you onto the latest major; we get you to a version with active patch support.
- We deploy on Cloudflare Pages, not Vercel. Is that fine?
- Yes. Most of the actual maintenance work is in the application code and dependency graph, not in the host. We have done Next.js maintenance against Vercel, Cloudflare Pages, AWS Amplify, and self-hosted Node — all the same shape of work.
- What about Pages Router vs App Router?
- Both are still supported by Next.js and both are maintainable. We do not pressure migrations from Pages to App Router unless the business case is there; the framework can run both indefinitely.
Send the Next.js app our way.
One paragraph about the app, the version you're on, and what's worrying you. Reply within one working day, from [email protected].
[email protected] →