A small Next.js marketing site usually costs about $20 to $50 a month in platform fees if nobody touches it (a Vercel Pro seat plus optional monitoring), and roughly $300 to $900 a month once you add a developer retainer. Agency plans for custom-coded sites are quoted at $200 to $800 a month. Hosting on Vercel or Cloudflare is the small, predictable part. Most of the bill is developer time: Next.js upgrades, security patches and edits.
If the person who built your Next.js site has moved on, this post breaks the cost into the five things you actually pay for, compares it with a WordPress retainer and lists what to ask before someone takes it over.
What does Next.js website maintenance cost per month?
A small Next.js marketing site typically costs between $20 and $900 a month to maintain. Hosting and monitoring sit at the low end. Developer time for updates, upgrades and edits pushes it towards the high end. Below are published market ranges for each line. They come from different providers, so read them as a guide, not a quote.
| Cost line | Typical market range | Source |
|---|---|---|
| Hosting (Vercel Pro) | $20 per user per month, plus usage | Vercel pricing |
| Hosting (Cloudflare Workers Paid) | $5 a month, 10 million requests included | Cloudflare Workers pricing |
| Dependency and security updates | $100 to $300 a month | Nayan Kyada, DEV; North Cave Studio |
| Annual major upgrade, spread monthly | $50 to $250 a month | Nayan Kyada, DEV; CodeMiners |
| Monitoring and uptime | $0 to $30 a month | Nayan Kyada, DEV |
| Content support | $0 to $400 a month | Nayan Kyada, DEV |
| Emergency fixes outside a plan | $150 to $300 an hour | CodeMiners |
Packaged care plans land in the same range. One studio that maintains Next.js and WordPress sites publishes tiers at $90, $220 and $480 a month, priced by developer hours and response time. At the agency end, some firms quote $1,500 to $5,000 a month for post-launch support. That's app territory. For a brochure site it's overkill.
How much does Next.js hosting cost on Vercel or Cloudflare?
Next.js hosting costs $20 per user per month plus usage on Vercel Pro, or $5 a month on Cloudflare Workers Paid with 10 million requests included. On most marketing sites it's the cheapest part of maintenance.
Vercel. The Pro plan is $20 per user per month plus usage. The free Hobby plan isn't meant for commercial use, so a business site belongs on Pro. The seat price rarely surprises anyone. The overages do, and they come from bandwidth, image optimisation and function execution. Throw in some huge uncompressed images or uncached API calls and usage can cost more than the seats.
Cloudflare. The Workers Paid plan is $5 a month and includes 10 million requests, which is plenty for most small and mid-sized sites. You pay for it in setup instead. Vercel makes Next.js, so running it on Cloudflare means an adapter and more testing every time you upgrade.
A fully static Next.js export can sit on almost any static host, and many have free tiers that cover a small brochure site, so hosting for that setup can be close to zero. I go through the two main platforms in more detail in Vercel vs Cloudflare for Next.js.
If your site has no developer right now, check one thing today: whose account is the hosting on? If it's on the old developer's personal Vercel team, you don't actually control your own site. Moving it into an account you own is the first job, not a nice-to-have.
How much do Next.js framework and dependency upgrades cost?
Routine dependency and security updates take about two to four hours a month on a small site, which published ranges price at $100 to $300 a month. An annual major upgrade adds roughly $50 to $250 a month when you spread it out. In my view this is the line that decides whether maintenance stays cheap or doesn't.
A Next.js site depends on Next.js, React and often 200 or more npm packages. Most updates are small patch and minor releases. A sensible routine is security patches every month and minor updates every quarter, tested on a preview branch first. That's typically two to four hours a month for a small site.
Major versions are a different story. Next.js has shipped a new major roughly every October, and under the Next.js support policy each one gets security fixes for two years from release. Right now Next.js 16 (released 21 October 2025) is the Active LTS version and Next.js 15 is in Maintenance LTS. Next.js 14 and everything before it is unsupported.
On Next.js 15 or older? Check your date
Next.js 15 is in Maintenance LTS, and each major gets security fixes for two years from its release. Check the exact end date on the [Next.js support policy](https://nextjs.org/support-policy) and plan the upgrade to Next.js 16 before Next.js 15 joins 14 and older without routine security patches.
Skipped upgrades are how a cheap site turns into an expensive one. If you keep a Next.js site current, each major upgrade is usually a day or two of work. Let it fall two or three majors behind and it becomes a project: routing changes, caching changes and packages that no longer support your version, all landing at once. If your site runs the Pages Router on an old major, get a fixed-price upgrade quote before you sign any monthly plan.
Why do Next.js sites need security patches on short notice?
Because framework-level vulnerabilities hit every site on an affected version at the same moment. CVE-2025-29927 in March 2025 and React2Shell in December 2025 are two recent examples. When one is disclosed, the fix is a version bump, a build and a deploy, and someone has to do it quickly.
In March 2025, CVE-2025-29927 let attackers skip Next.js middleware, which a lot of sites used for authentication, just by sending a crafted request header. In December 2025, CVE-2025-55182, known as React2Shell, was a remote code execution flaw in React Server Components that affected Next.js apps.
Neither one needed a dodgy plugin or a weak password. Fixing them needed someone to notice, bump the version, build, test and deploy, fast. On a site with no developer, that simply doesn't happen. It's the best reason I know to keep someone on a retainer even when the site "just works".
Security headers are a separate and much cheaper fix. You can see what your site sends today with my free Security Headers Checker.
Do you need Core Web Vitals checks every month?
A light monthly check, yes. A deep monthly audit, no. The check takes minutes. Fixing a slowdown takes hours, so you want to catch it early.
Performance on a Next.js site slips over time. Someone adds a heavy hero video, a chat widget, another analytics tag or an unoptimised image, and LCP or INP gets worse without anyone noticing. Standard care tiers often include a monthly Core Web Vitals check, and real-user data from Vercel Speed Insights or Google Search Console is free or close to it.
Fixing those slowdowns is where a retainer's included hours tend to go. If your site is already failing, start with how to fix Core Web Vitals on Next.js, or paste a PageSpeed report into my free Page Speed Fix Planner to get a ranked list of fixes. Bigger performance work belongs under technical SEO and Core Web Vitals, not monthly upkeep.
Who pays for content and CMS edits on a Next.js site?
Content edits cost anywhere from $0 to $400 a month, and it comes down to where the content lives. If your team edits it in a CMS, it's cheap. If it's hard-coded, every change needs a developer. No line varies more than this one.
- Content hard-coded in the codebase. Every text change needs a developer, a commit and a deploy. Content support can easily end up as your biggest monthly cost.
- A headless CMS (Sanity, Contentful, or WordPress as a backend). Your team edits text and images themselves. You only pay a developer for new page layouts, schema changes, redirects and preview fixes.
- No CMS, but changes are rare. Pay per change and skip the retainer hours.
Market ranges for this line run from $0 to $400 a month. If you're paying a developer to fix typos, adding a CMS often pays for itself. A headless WordPress backend gives your team the editing screen they already know and keeps the Next.js front end.
Is Next.js maintenance cheaper than a WordPress retainer?
Usually not. Published retainers run $200 to $800 a month for custom-coded sites like Next.js, against $75 to $300 a month for WordPress. WordPress upkeep is mostly plugin management. Next.js upkeep is mostly dependencies and framework versions, and fewer developers can do that work.
| What you compare | WordPress site | Next.js site |
|---|---|---|
| Typical retainer | $75 to $300 a month | $200 to $800 a month for custom sites |
| What gets updated | Core, theme and an average of 20 to 30 plugins | Next.js, React and hundreds of npm packages |
| Hosting | Managed WordPress host | Vercel Pro from $20 a seat or Cloudflare from $5 |
| Content edits | Built-in admin | Depends on the CMS, or a developer |
| Main security risk | Outdated plugins | Framework CVEs and outdated packages |
| Cost of neglect | Hacked site, broken plugins | Unsupported major, costly catch-up upgrade |
There's one upside on the Next.js side. Every update goes through a build and a preview deploy, so a bad update is easier to catch before it reaches visitors. The catch is that someone who knows the codebase has to do it. For the WordPress side in detail, see what WordPress maintenance costs in the US. The ranges in this post are US market figures; if you're comparing retainers elsewhere, see WordPress maintenance costs in the UK and in India.
What should you do if your Next.js developer has left?
Get control of the domain, DNS, Git repository and hosting first. Then check the Next.js version and get a quote. This is the order I'd follow on any site I take over.
- 1
Collect the access
Domain registrar, DNS, the Git repository, the hosting account, the CMS and any API keys. Each should sit in an account your business owns.
- 2
Check the versions
Note the Next.js and React versions in package.json and compare them with the official Next.js support policy. This tells you whether you need an upgrade project or just upkeep.
- 3
Run a clean build
Clone the repo, install and build it on a fresh machine. If it won't build, that's the first fix, before any feature work.
- 4
Baseline speed and SEO
Record Core Web Vitals, Search Console coverage and key rankings, so you can tell later whether changes helped or hurt.
- 5
Agree a written scope
Decide what the monthly fee covers, how many hours, response times, and what counts as extra project work.
I've run a monthly maintenance retainer for IPL Biologicals since 2025, covering new pages, catalogue and price updates, and day-to-day store support.
What should you ask a developer before signing a Next.js retainer?
Get written answers on major upgrades, CVE response times, testing, account ownership and included hours. These are the questions I'd ask:
- Do you upgrade Next.js majors, and is that inside the monthly fee or quoted separately?
- How fast will you patch a critical framework CVE, and on which plan?
- Do you test updates on a preview deploy before they go live?
- Are the hosting, repository and domain in my account, or yours?
- How many hours are included, and what happens to unused hours?
- What do you report each month: updates applied, Core Web Vitals, uptime?
- Can you work with my CMS, or will every edit need you?
If one developer answers all of these clearly, in writing, and a cheaper one dodges them, I'd pick the first.
How do you get your Next.js site maintained?
Do the access and version check above, then hand the site to a developer on a written monthly scope. If nobody is looking after your Next.js site right now, send me the site URL and what you need. I'll tell you whether it needs an upgrade first or can go straight onto a maintenance retainer. And if it really needs a rebuild rather than patching, I can scope that too through my Next.js and React websites service.
