Next.js App Hosting
Next.js apps, deployed and left running.
A Next.js app is not a folder you upload. It builds, it renders on a server, it revalidates pages in the background and it wants environment variables kept out of the repository — none of which cPanel was designed for. This is hosting shaped around that: connect the repository, push to main, and the build either goes live or tells you why it didn't.
What You Get
The parts that decide whether it holds up.
Deploys From Git
Push to your main branch and the build runs. If it passes it goes live; if it fails, the previous version stays up and nobody outside notices.
A Preview Per Branch
Every branch and pull request gets its own URL. Clients click through the real thing before it merges, rather than approving a screenshot.
Server Rendering And ISR
App Router, server actions, route handlers and incremental regeneration all run as intended — not a static export with the interesting parts removed.
Secrets Out Of The Repo
API keys and connection strings held per environment, so production credentials are never a line in a file somebody can clone.
Edge Cache, Local Origin
Static assets served from the nearest edge worldwide, with the origin in South Africa where most of your visitors and your database already are.
Rollback In One Click
Every build is kept. A release that turns out badly is reverted in seconds, which is a considerably better plan than fixing it under pressure.
Built for the way the app actually ships.
Git-connected hosting for Next.js and Node applications, with preview deployments and one-click rollback.
The point of this setup is that deploying stops being an event. Work merges, previews go out for review, releases happen on a Tuesday afternoon because there's nothing to be nervous about, and a bad one is undone before the meeting ends. We'll set the pipeline up on our infrastructure or inside your own accounts — the arrangement matters less than having one.
What runs on it
- Next.js App Router and Pages Router, any recent version
- Server components, server actions and route handlers
- Scheduled jobs and background functions
- Managed Postgres, Supabase or your existing database
- Headless WordPress and other API-driven front-ends
- Custom domains and subdomains with automatic SSL
- Other Node frameworks — Nuxt, Astro, Remix, plain Node
Plans
What it costs.
Deploy
R295per month
or R3 186 a year
One app, deployed from your repository, with preview builds on every branch. Right for a marketing site or a first release.
- Apps
- 1
- Environments
- Production + previews
- Builds
- Unlimited
- Bandwidth
- 100 GB a month
- Regions
- Global edge, SA origin
- Deploys straight from GitHub on every push
- A preview URL for every branch and pull request
- Free SSL on your domain and every subdomain
- Server rendering, route handlers and ISR
- Environment variables kept out of the repository
- One-click rollback to any previous build
Production
R650per month
or R7 020 a year
For an app people rely on: more headroom, a staging environment of its own and someone watching the error rate.
- Apps
- Up to 3
- Environments
- Production, staging, previews
- Builds
- Unlimited
- Bandwidth
- 500 GB a month
- Regions
- Global edge, SA origin
- Everything in Deploy
- A permanent staging environment
- Scheduled jobs and background functions
- Error and performance monitoring, alerting us
- Uptime checks every minute
- Priority support, same business day
Scale
Let's talkscoped per app
billed monthly
Higher traffic, tighter latency or compliance requirements — priced against what the app actually does.
- Apps
- Unlimited
- Environments
- As many as you need
- Builds
- Unlimited
- Bandwidth
- Metered, agreed up front
- Regions
- Multi-region on request
- Everything in Production
- Dedicated database and cache sizing
- Load testing before launch
- An agreed response time, in writing
- Quarterly performance and cost review
- A named person who knows your stack
Prices exclude VAT and cover the application hosting only. A database, mailboxes and your domain are billed separately.
Questions
Before you move over.
Switching hosts sounds like a big job. It usually isn't — we do the moving.
Can you deploy into our own Vercel or Azure account?
Yes, and for a team with an existing cloud account that's often the tidier answer. You hold the billing and the accounts, we set up the pipeline, the environments and the monitoring inside them. It's quoted as setup plus a support retainer rather than a monthly hosting plan.
Where does the database live?
Usually managed Postgres — Supabase or an equivalent — in the region closest to your users. We'll happily connect to a database you already run instead. Either way it's separate from the app hosting, so it can be sized and backed up on its own terms.
What happens if we go over the bandwidth?
We tell you before you do, and either move you up a plan or work out what's actually consuming it — an unoptimised image set is a more common cause than real traffic. Nothing is cut off and no surprise overage lands on the invoice.
Could this run on one of your VPS plans instead?
It can, and for an app with steady traffic and a database beside it that's sometimes cheaper. What you give up is the build pipeline and preview URLs, which then have to be assembled and maintained. We'll tell you honestly which one your project wants.
Do you host apps you didn't build?
Yes. We'll take a look at the repository first — mostly to check the build, the environment variables and whether anything is holding state on the filesystem — and then quote the migration. It's typically a day's work.
Also in hosting
Ready to bring your idea to life?
Let's create something amazing together.
Firm quote against a scoped roadmap before any work begins.