In March 2026, Next.js 16.2 made Adapters stable. That sounds like a release note for engineers. For a small business picking a host, it changes the shortlist: hosting platforms now have a public, documented way to build and run Next.js sites, so the framework is no longer tied to one vendor’s infrastructure.
So which host should you pick? Fewer of them are wrong than a year ago. The harder question is who will look after the site once it is live.
What changed for Next.js hosting this year
An adapter is code a hosting platform writes so that a standard Next.js build turns into something its servers can run. Until the API became stable, platforms had to work around the framework’s build output on their own. Now there is one public contract, and the Next.js team lists an adapter as verified only when its source is open and it passes the framework’s compatibility test suite. For you, that means a host’s claim to “support Next.js” is something you can check rather than take on trust.
The minimum a host has to provide
The official deployment guide sets a low bar: a Node.js server. One next start process runs every feature. The rest of this list is about speed and reliability, and most business sites will want all of it.
- A long-running Node.js process, or a container you control, rather than a PHP-only shared plan.
- Streaming responses that no proxy buffers, so pages can render progressively.
- Support for the sharp package, which Next.js uses to optimise images.
- A CDN in front of the server, so visitors far from it still get cached pages quickly.
- A shared cache once you run more than one instance, so a content update reaches every server.
- Clean shutdowns during deploys, so work that runs after a response is not cut off halfway.
Shared hosting, a VPS or a managed platform
Most plans fall into one of three groups. Read the table from the bottom: the work never disappears, it moves to whoever runs the option you choose.
| Question | Shared hosting | VPS or container host | Managed platform |
|---|---|---|---|
| Runs Next.js? | Only if the plan offers Node.js apps | Yes, with next start or Docker | Yes, through its adapter |
| Caching and CDN | Rarely configurable | You set it up | Included and tuned for the framework |
| Security patches | The host patches the server, not your app | You patch both | The platform patches the runtime, you patch the app |
| Good fit | A static export of a small brochure site | Teams with an engineer who enjoys servers | Businesses that would rather pay than maintain |
Questions to ask a host before you sign
Is your Next.js support a verified adapter?
Ask for the repository. Open source code that runs the official test suite is the standard the Next.js team itself applies; a closed integration may work fine, but nobody outside the host can confirm it.
What happens to the cache when content changes?
If the site pulls articles, prices or opening hours from a CMS, one edit should refresh every page that shows it. Say a bakery changes its Sunday hours on Saturday night. With two servers and no shared cache, only one of them may learn about the edit, and some customers walk up to a locked door. Ask how theirs works.
Who patches what?
Security fixes land in the framework as well as on the server. A good host states in writing where its responsibility ends and yours begins.
Can I leave?
Because the adapter API is public, moving a Next.js site between platforms is far less painful than it used to be. A host that makes exports awkward is telling you how the relationship will go.
Who keeps the site healthy after launch
Hosting is a monthly invoice. The site itself keeps changing: framework upgrades, a CMS your editors rely on, caches that need attention as traffic grows. WordPress owners know this rhythm too. WordPress 7.0 slipped to May 20, 2026 because contributors needed more time for architectural work, and every host and plugin vendor had to adjust. Someone has to own that calendar for your site.
Pagepro, a Next.js and Sanity migration specialist, moved Localcoin, Canada’s largest Bitcoin ATM network, from WordPress to Next.js and Prismic in 2021 and is still its development partner 5+ years later. That is the pattern to look for in any team you hire: the people who built the site still answer for it years on. Proofed has worked with Pagepro since 2020, a relationship now 6+ years old.
The trade-off is plain. A managed platform costs more each month and asks less of your team; a VPS costs less and asks more. Neither is wrong. What goes wrong is renting the cheaper server and assuming the upkeep comes free. If nobody on your side will patch, upgrade and watch the cache, the extra spend belongs on the platform, or on a partner who will do that work for you.
