--- title: "Which Hostinger plan do you need for a Next.js app?" description: "Premium, Business, or Cloud Startup for a Next.js app? The answer comes down to build memory, traffic, and how many apps you want on one bill — plus the point where you should stop buying shared plans and take a VPS." canonical: https://wacrm.tech/blog/hostinger-plan-for-nextjs datePublished: 2026-08-25 dateModified: 2026-08-25 author: "Arnas Donauskas" license: "content © wacrm; product is MIT-licensed" --- # Which Hostinger plan do you need for a Next.js app? Three plans can run a Next.js app, and the difference between them is not features — all three give you a real Node process, Git deploys and managed SSL. The difference is how much memory your build gets, how much traffic the plan absorbs before it slows down, and how many apps you can park on one bill. Here is how to pick in about two minutes, plus the point where the right answer stops being a shared plan at all. > **Disclosure:** the Hostinger links here are referral links, and we host > [wacrm](https://wacrm.tech/) on the Business plan. Specs and prices were read from Hostinger's > own pages in August 2026 — check them before you buy. ## The three plans ## Start with the build, not the traffic The counter-intuitive part of sizing a Next.js host: the peak memory moment is not serving requests, it is `next build`. The build type-checks and compiles the whole project at once, and a large app can use several times more memory than the running server ever will. That makes it the deciding number: - **Under 2 GB peak** — Premium is fine, and it is the cheapest way to put a small app on a real domain. - **2–3 GB peak** — Business. This is where most production apps land, and the extra core means a build no longer starves the running app. - **Consistently tight, or a monorepo** — Cloud Startup, or build in CI and deploy the output. Measure it rather than guessing: run `npm run build` locally and watch memory in Activity Monitor or `htop`. If a deploy ever dies without a useful error message, memory is the first suspect, not the framework. ## Then count the apps App slots are the quiet reason to skip the cheapest tier. Most projects are not one app: - the product itself - a marketing site or landing page - a staging copy you can break safely Premium and Business both allow five web apps; Cloud Startup allows ten. Since each slot is an independent Node application with its own domain, that is three metered projects on a metered platform and one line on this bill. ## Then think about traffic Bandwidth is unlimited on all three plans, and there is no per-gigabyte charge — that is the meaningful difference from a metered host, where traffic converts directly into invoice. What is finite is CPU and memory. A spike does not produce an overage line, it produces slower responses. So the traffic question is not "how many gigabytes" but "how much concurrency": - **A few thousand visits a day** — Business handles it without drama. - **Sustained real traffic, or bursts** — Cloud Startup's four cores are the cheapest fix, and moving up is a plan change rather than a migration. - **Traffic you cannot predict at all** — a shared plan is the wrong shape. Either take a VPS you can size, or use a platform that autoscales and accept the metered bill. [Hostinger vs Vercel](https://wacrm.tech/blog/hostinger-vs-vercel) works through that trade with real numbers. ## What every plan includes Worth knowing before you compare against a bare $5 container elsewhere: - A **free domain** for the first year, and unlimited free SSL certificates. - **GitHub integration** — push to your branch and it builds and deploys. - **Managed MySQL**, if the app needs a database on the same account. (wacrm uses Supabase for Postgres instead, so this one goes unused there.) - **Cron jobs** at any interval, against a persistent process. - **Email** on your domain, backups (weekly on Premium, daily above it), and 24/7 support. - A **30-day money-back guarantee**, which is the part that makes trying it low-risk. ## When to stop buying shared plans Be honest about this rather than upgrading twice. Move to a [VPS](https://www.hostinger.com/vps-hosting?REFERRALCODE=WACRMHOST) when you need something the shared platform does not do, not just more of what it does: - root access, or system packages you install yourself - Docker, or a runtime that is not on the platform - Redis, a queue, or any long-running background worker - more than about 4 GB of memory KVM 2 is $8.99/month on a two-year term ($14.99 at renewal) for 2 vCPU, 8 GB of RAM and 8 TB of traffic. The trade-off is real: OS updates, the web server, and backups become your job. ## What to check at checkout 1. **The term.** The advertised price requires prepaying it — usually 48 months. Shorter terms cost more per month. 2. **The renewal price.** $10.99, $16.99 or $25.99 a month for Premium, Business and Cloud Startup. Budget with this number, not the promotional one. 3. **The data centre.** Pick the one nearest your users; a shared plan serves from one region and you will feel the wrong choice. 4. **Whether the plan name matches.** The $3.99 tier appears as "Business" on the web-apps page and "Unlimited" on some others. Same plan; check the specs, not the label. ## Deploying wacrm specifically wacrm is a Next.js app with Supabase behind it, so Business is the recommendation: enough memory to build, daily backups, and slots left for a marketing site and staging. The [Hostinger deployment guide](https://wacrm.tech/docs/deployment-hostinger) walks through creating the app, connecting your fork, and setting environment variables, and [automations and cron](https://wacrm.tech/docs/automations-and-cron) covers the scheduled jobs. Ready to pick one? The [Business plan](https://www.hostinger.com/web-apps-hosting?REFERRALCODE=WACRMHOST) is the default choice for a production Next.js app, and the money-back window means a wrong guess on plan size is reversible.