Where can you host a Next.js app at a flat price?
On a Frontend pack: connect the GitHub repository, the Next.js build is detected, and the app runs as a normal Node server on its own CPU, memory and disk. Server rendering, API routes, server actions and middleware all work because the app runs as a long-lived server, not as separate functions. The price is the pack, flat for the term, with no charge per seat, per request or per gigabyte served.
Step by step
- 1
Connect the repository
Dashboard → Deployments → New: select the repository, a branch and a pack. Build and start commands are filled in for Next.js. The order creates an invoice and the build starts once it is paid.
From an agent over MCP
deploy → price + approval link, then get_status until the site is running - 2
Add environment variables
Add each variable on the Environment tab (set_env over MCP). Anything the browser reads needs the NEXT_PUBLIC_ prefix.
Variables are read at build time, so the site rebuilds after you change them; the current version keeps serving until the new build is ready.
- 3
Add a database if the app needs one
Create a PostgreSQL or MySQL pack, set DATABASE_URL on the site, and run your migrations from the site's terminal or as part of the start command.
- 4
Attach the domain
Site → Domains tab → enter the domain and create the DNS record it shows. The certificate is issued once the record resolves.
- 5
Push to redeploy
Each push to the branch builds a new version; the running one keeps serving until the new build is ready. rollback_site returns to the previous version.
What breaks, and the fix
- next/image fails for remote images
- List the image hosts under images.remotePatterns in next.config, as on any Node host.
- Edge-only features
- Code written for an edge runtime runs in the Node runtime here. Remove the edge runtime export if a route needs Node APIs.
What it costs
- A Frontend pack from $1/mo; $5/mo for the pack most production apps pick (1 vCPU / 4 GB / 25 GB).
- A database, if you need one, from $10/mo.
- A domain from $11.39/yr, or use one you already own.
App
$1/mo
Starter Frontend pack, 1 vCPU / 1 GB RAM / 10 GB
Database, users and files
$5/mo
Smallest dedicated Supabase pack; several projects fit on one
Questions
Does server-side rendering work?+
Yes. The app runs with next start as a Node server, so SSR, API routes, server actions and middleware behave as they do locally.
Do I need a Dockerfile?+
No. A Next.js repository is detected and built as it is. If the repository has a Dockerfile, that is used instead.
Is there a per-seat fee for my team?+
No. The price is the pack. Teammates do not add to it.
What about bandwidth?+
Traffic is not metered. The pack's CPU and memory are the limit, and you can move to a larger pack when you need more.
Can I deploy from Cursor or Claude Code?+
Yes. Connect the Hostwares MCP server and the agent can deploy, set variables, read logs and roll back.
What does it cost?+
From $1/mo, flat for the term.