Next.js hosting in South Africa comes down to three realistic options: a serverless platform (usually running in overseas regions), a managed Node.js host that runs next start for you, or a VPS you manage yourself. If most of your visitors are in South Africa and you want to pay in rand, a managed Node.js host with servers in Johannesburg is usually the simplest fit. This guide explains how Next.js runs in production, what each option really costs you in effort, and what to check before you choose.
How Next.js actually runs in production
Before comparing hosts, it helps to know what a host needs to do. A Next.js app can be deployed in three shapes:
| Output | How it runs | What you get |
|---|---|---|
Default (next build + next start) |
A long-running Node.js server | Every feature: App Router, Server Components, Server Actions, Route Handlers, proxy (middleware), ISR, image optimisation, streaming |
output: 'standalone' |
Same Node.js server, but with a minimal, self-contained folder | The same features, with a much smaller deployment |
output: 'export' |
Plain HTML, CSS and JS files | No server: no Server Actions, no ISR, no on-demand image optimisation, no request-time rendering |
The key point: a full Next.js app needs Node.js. Any host that can run a Node.js process, keep it alive and route HTTP traffic to it can run Next.js with every feature. The official Next.js self-hosting docs confirm this. You do not need a specific vendor's platform.
If your site is purely static (a brochure site with no forms handled on the server), output: 'export' works on any web host. Most real apps (logins, dashboards, CMS content, forms) need the server.
Your hosting options compared
| Option | Good for | Trade-offs |
|---|---|---|
| Serverless platform | Global audiences, teams that want zero server thinking | Regions are mostly overseas, usage-based billing in US dollars, some features tied to the platform |
| Managed app hosting | Most business apps, agencies, small teams | Less low-level control than a VPS; you rely on the host's build pipeline |
| VPS | Custom setups, background daemons, full root access | You patch the OS, run Node, configure Nginx, SSL, backups and restarts |
| Shared cPanel with a Node selector | Small hobby projects | Often limited RAM and process control, builds may need to happen elsewhere |
We go deeper on the platform question in self-hosting Next.js vs Vercel, and on the server question in Node.js on a VPS vs managed hosting.
Local vs overseas servers
Physical distance matters for anything that is rendered on request. A server-rendered page, a Server Action or an API call has to travel from the visitor to the server and back. When the server is in Johannesburg and the visitor is in Cape Town or Durban, that round trip is short. When the server is in Europe or the US, every request crosses an undersea cable first.
A CDN hides much of this for static assets and cached pages, but it cannot hide it for:
- pages rendered per request (personalised dashboards, carts, search results)
- Server Actions and form submissions
- API calls from the browser to your backend
- database queries, if your database sits far from your app server
The last one catches people out. If your app runs overseas but your database is local (or the other way round), every query pays the long round trip, and a page that runs ten queries pays it ten times. Keep the app and database in the same place.
Other local factors worth weighing:
- Billing in rand. No exchange-rate surprises and no foreign transaction fees on your card.
- VAT invoices. A South African VAT invoice is simpler for your bookkeeping than a foreign invoice.
- POPIA. POPIA does not ban hosting overseas, but sending personal information across the border has its own conditions under section 72. Keeping data local removes one question.
- Support in your time zone.
What to look for in a Next.js host
Use this as a checklist when comparing providers:
- Node.js LTS versions. Next.js 16 needs Node.js 20.9 or later. Node.js 24 is the current Active LTS and a sensible default; see nodejs.org for the release schedule.
- Git deploys. A push to your main branch should build and deploy without you touching a server.
- Configurable commands. You should control the install, build and start commands (for example
npm ci,npm run build,npm start). - Environment variables. Secrets stored encrypted, separate from your code.
- Enough RAM. A small site runs comfortably on modest memory, but image optimisation and large pages use more. Builds for big apps can need more memory than the running server.
- Preview deploys. A separate URL per branch makes client and team reviews much easier.
- Databases nearby. Managed MySQL or PostgreSQL in the same location as your app.
- Scheduled tasks. For sending emails, cleaning up data or syncing with other systems.
- Free SSL. Let's Encrypt certificates issued and renewed automatically.
- Backups you can restore. Ask how often, how long they are kept and how a restore works.
How NewHost runs Next.js
NewHost is a South African hosting platform with servers in Johannesburg. For Next.js hosting, this is what you get:
- Deploy from Git. Connect a GitHub or GitLab repository and pick a branch. A push to that branch deploys automatically via a webhook.
- Your commands. Install, build and start commands are configurable, so the default Next.js scripts or a standalone setup both work.
- Encrypted environment variables for API keys and database credentials.
- Branch preview deploys on the Developer plan and up. Pushes to other branches get their own preview URL (up to 5 per app), removed when the branch is deleted or after 14 days without a deploy.
- Managed MySQL databases, with PostgreSQL or MS SQL available on request.
- Scheduled tasks (cron-style, as often as every 5 minutes).
- Free Let's Encrypt SSL and automatic backups, plus on-demand backups.
Choosing a plan
All prices are monthly in rand, excluding VAT. Yearly billing is 10x the monthly price (two months free).
| Plan | Price | Apps | RAM per app | Databases | Backups |
|---|---|---|---|---|---|
| Starter | R99 | 1 | 512 MB | 1 MySQL | Weekly, kept 4 weeks |
| Developer | R249 | 3 | 1 GB | 3 | Daily, kept 7 days |
| Business | R599 | 10 | 2 GB | 10 | Daily, kept 30 days |
| Agency | R1,499 | 30 | 4 GB | 40 | Daily, kept 30 days |
A single marketing site or small app fits Starter. If you want preview deploys or run a few apps, Developer is the step up. Business adds unmetered traffic, priority support and three team seats. Full details are on the pricing page.
Frequently asked questions
Can I host Next.js on normal cPanel web hosting?
Only partly. If you use output: 'export', the result is static files that any web host can serve. For server features like Server Actions, ISR and image optimisation you need a host that runs a Node.js process, which many shared plans limit or do not support.
Do I need Vercel to use Next.js?
No. Next.js is open source and every feature works on a Node.js server you run anywhere. Vercel adds its own platform features on top, and whether those are worth it depends on your audience and budget.
How much RAM does a Next.js app need?
It depends on traffic, page complexity and how much image optimisation you do. Small sites run well on 512 MB. Busier apps, heavy image use or several apps on one account benefit from 1-2 GB each. Measure your app's memory under realistic load rather than guessing.
Is hosting in South Africa faster for South African visitors?
For anything rendered on request, yes, because each request travels a shorter distance. Static files behind a good CDN are fast from almost anywhere, so the difference shows most on dynamic pages, API calls and form submissions.
Which Node.js version should I run for Next.js?
Use a current LTS release. Node.js 24 is Active LTS, and Node.js 22 is still supported in maintenance. Pin the version in your package.json engines field so your local machine and the server agree.
Ready to run your Next.js app on local servers and pay in rand? See NewHost Next.js hosting and pick a plan that fits.