Skip to content
NewHost
Menu

Next.js Hosting

Next.js Hosting in South Africa

Run full-stack Next.js on South African servers. Connect GitHub, pick a repository and branch, and every push builds and deploys your app: server components, API routes, middleware and incremental static regeneration included.

Features

Full Next.js support

App Router, server components, API routes, middleware and ISR on Node.js 20, 22 or 24.

Push to deploy from GitHub

Connect GitHub once and pick the repository (private ones too); every push to your branch deploys, and GitHub shows each deployment on the commit.

Build logs, redeploys & rollbacks

Live step-by-step deployment logs with your build output, one-click redeploys and rollbacks to an earlier commit.

Encrypted environment variables

Secrets are encrypted with AES-256-GCM at rest and never shown again after saving.

Local latency

Servers in South Africa keep round trips short for South African visitors.

Free SSL

Let's Encrypt certificates for your custom domain and free app address.

GitHub hosting plans

Every plan deploys from GitHub on each push, with build logs, rollbacks, environment variables, free SSL and databases. Pay monthly or yearly; no VAT is added.

Starter

For side projects and portfolios.

R79/month

or R790/year. No VAT is added.

  • 1 Node.js / Next.js app
  • 512 MB RAM · 0.5 vCPU
  • 5 GB NVMe storage · 100 GB traffic
  • 1 database next to your apps
  • Deploys from your main branch
  • Weekly backups, kept 28 days
Choose Starter
Most popular

Developer

Git-driven workflow for freelancers.

R199/month

or R1 990/year. No VAT is added.

  • 3 Node.js / Next.js apps
  • 1 GB RAM · 1 vCPU
  • 20 GB NVMe storage · 500 GB traffic
  • 3 databases next to your apps
  • Preview deploys per branch
  • Daily backups, kept 7 days
Choose Developer

Business

Production workloads and small teams.

R479/month

or R4 790/year. No VAT is added.

  • 10 Node.js / Next.js apps
  • 2 GB RAM · 2 vCPU
  • 50 GB NVMe storage · unmetered traffic
  • 10 databases next to your apps
  • Preview deploys per branch
  • Daily backups, kept 30 days
  • 3 team seats
  • Priority support
Choose Business

Agency

Host all your clients, white-labelled.

R1 199/month

or R11 990/year. No VAT is added.

  • 30 Node.js / Next.js apps
  • 4 GB RAM · 4 vCPU
  • 150 GB NVMe storage · unmetered traffic
  • 40 databases next to your apps
  • Preview deploys per branch
  • Daily backups, kept 30 days
  • Unlimited team seats
  • Priority support
Choose Agency

Compare plans

PlanStarterR79/monthDeveloperR199/monthBusinessR479/monthAgencyR1 199/month
Apps131030
RAM512 MB1 GB2 GB4 GB
vCPU0.5124
NVMe storage5 GB20 GB50 GB150 GB
Traffic100 GB500 GBUnmeteredUnmetered
Databases131040
Push to deploy from GitHubYesYesYesYes
Preview deploys per branchNoYesYesYes
Rollbacks and redeploysYesYesYesYes
BackupsWeekly, 28 daysDaily, 7 daysDaily, 30 daysDaily, 30 days
Team seats003Unlimited
Priority supportNoNoYesYes

How GitHub deploys work

  1. 1

    Connect GitHub once

    Sign in with GitHub and allow NewHost access to your repositories; GitHub's permission covers public and private ones (an organisation may need to approve NewHost first). The token is stored encrypted, and you can revoke it on GitHub at any time.

  2. 2

    Create an app

    Pick the repository and branch, the framework and Node.js version. Install, build and start commands are filled in for the framework; change them if your project differs.

  3. 3

    Set environment variables

    Add your secrets (database URL, API keys) before the first deploy. Values are encrypted at rest and only the names are shown after saving.

  4. 4

    Deploy

    NewHost creates your site, fetches the commit, installs dependencies, runs your build script and starts the app, with a live log of every step and your build output.

  5. 5

    Push to update

    Every push to the branch deploys again; GitHub shows the deployment status on the commit. Pushes to other branches can deploy as previews on plans that include them.

  6. 6

    Go live on your domain

    Use the free app address or connect your own domain; a free Let's Encrypt certificate is issued during the deploy.

What every app gets

Sign in with GitHub

NewHost uses your GitHub access only to list your repositories, add the push webhook to the ones you connect, fetch your code and show deployment statuses. It never changes your code.

Push to deploy

A push to your production branch queues a deployment. One runs at a time per app; if several pushes arrive while one runs, the latest one is deployed next.

Preview deploys

On plans with previews, a push to any other branch deploys to its own address (branch--app on the platform domain). Idle previews are removed automatically.

Build logs

Every deployment has a step-by-step log with timestamps and your npm output, updated live in the dashboard. Secrets are kept out of the log.

Rollbacks and redeploys

Roll back to the commit of any earlier successful deployment, redeploy the current one, or cancel a deployment that is still queued.

Environment variables

Encrypted with AES-256-GCM at rest and passed to your app on each deploy; values are never shown again after saving.

Custom domains and free SSL

A free address on the platform domain from the first deploy, or your own domain with a free Let's Encrypt certificate.

Databases next to your app

Create MySQL or PostgreSQL databases on your app's server from the app's page (the engines that server offers), up to your plan's number.

Scheduled tasks

Deploy an app or call one of its URLs on a cron schedule or once, in South African time.

GitLab and other Git URLs

Paste a repository URL instead of connecting GitHub: deploy from the dashboard or on a schedule, and GitLab pushes deploy through a signed webhook per app.

Supported frameworks

  • Next.js

    Runs on Node.js 24, 22, 20. Default start file server.js, build script "npm run build".

  • Node.js

    Runs on Node.js 24, 22, 20. Default start file index.js, no build step.

  • Express

    Runs on Node.js 24, 22, 20. Default start file app.js, no build step.

  • Nuxt

    Runs on Node.js 24, 22, 20. Default start file .output/server/index.mjs, build script "npm run build".

  • Static site

    Built with your build script (optional) and served as files from the output folder, e.g. dist; no Node.js process runs.

Good to know

  • Dependencies are installed with npm (npm ci or npm install); yarn and pnpm install commands are accepted and run as an npm install, so commit a package-lock.json.
  • The build command must be a script in your package.json (npm run build, yarn build or pnpm run build).
  • One deployment runs at a time per app; while one runs, the latest push waits as the next one.
  • Your plan sets the number of apps, the RAM, storage and databases, and whether branch previews are included.
  • Apps run on NewHost's servers in South Africa. You don't get a shell on the server: everything is done through the dashboard, the API and Git.

Frequently asked questions

Which Next.js features are supported?

Server-side rendering, static generation, incremental static regeneration, API routes, middleware and the App Router. Apps run on Node.js 20, 22 or 24.

How do deployments from GitHub work?

Sign in with GitHub once and allow NewHost access to your repositories. Pick a repository and branch for your app and NewHost adds a webhook to the repository: each push to that branch queues a deployment, which installs dependencies, runs your build script and restarts the app. GitHub shows the deployment's status on the commit.

Do private repositories work?

Yes. GitHub's repository permission covers public and private repositories (GitHub has no read-only option for private ones). NewHost stores the token encrypted and uses it only to list your repositories, add the deploy webhook to the ones you connect, fetch your code and show deployment statuses; it never changes your code. You can revoke it on GitHub at any time (Settings > Applications > Authorized OAuth Apps); private repositories then stop deploying.

Can I preview branches before they go live?

On plans with preview deploys, a push to any other branch deploys it to its own address (branch--app on the platform domain), so you can check it before merging. Previews that are no longer used are removed automatically.

What happens if a build fails?

The deployment stops at the failed step and its log shows your npm output with the error. Fix it and push again, redeploy, or roll back to the commit of an earlier successful deployment.

Can I use yarn or pnpm?

Dependencies are installed with npm, so commit a package-lock.json. yarn and pnpm install commands are accepted and run as an npm install; the build command must be a script in your package.json.

Can I use my own domain?

Yes. Every app gets a free address on the platform domain; point your own domain at the app or register one through NewHost, and a free SSL certificate is issued.

Do I get a database?

Every app plan includes databases you create next to your app from its page, up to your plan's number. For more, or for databases used outside NewHost apps, add a database plan.

Can I deploy on a schedule or trigger jobs?

Yes. Scheduled tasks deploy an app or call one of its URLs on a cron schedule or once at a set time, in South African time.

Can I deploy from GitLab or another Git host?

Yes: create the app with the repository URL instead of connecting GitHub. Deploy from the dashboard or on a schedule; GitLab pushes deploy through a signed webhook per app.

Related

Deploy your Next.js app from GitHub

Connect GitHub, pick a repository and branch, and every push builds and deploys your app. Questions about your stack? Talk to us first.