Does Hostney run Nuxt as SSR or a static site?

Both. If your build runs nuxt generate, we serve the static output from our edge cache. A standard Nuxt build runs as a live Node container so server-side rendering, server routes (Nitro), and API endpoints all work. We detect which one you use and deploy it the right way.

Which Nuxt version is supported?

Nuxt 3 and its Nitro server engine are what we target. You choose the Node.js runtime - 24, 22, or 20 - and we read it from your .nvmrc, .node-version, or package.json engines field if you set it there.

Do Nitro server routes and server API work?

Yes. Because a full Nuxt app runs as a real Node process in its own container, everything Nitro provides - server routes, server middleware, and API handlers under server/ - behaves exactly as it does locally.

What about my package manager?

We detect npm, pnpm, yarn, or bun from your lockfile and run the matching install and build commands. Nothing to configure - but you can override the commands if your setup is unusual.

How do I connect my repo?

Link GitHub, GitLab, or Bitbucket over OAuth or a token, choose the repository and branch, and a push webhook is registered automatically. From then on, pushing to that branch triggers a build.

What port does Nuxt need to bind to?

A server-rendered Nuxt app must listen on 0.0.0.0 using the PORT environment variable we provide (3000 by default). Nitro reads PORT automatically, so in most cases this just works out of the box.

Can I roll back a bad deploy?

Yes. Every successful build is stored. Promote a previous build back to live in seconds from the Deployments tab - no rebuild needed. We keep your five most recent successful container builds per app.

Is Nuxt hosting included in my plan?

Yes. Git deployment, container hosting, rollback, logs, and environment management are part of every plan. A server-rendered Nuxt app runs in a container that counts against your plan’s app allowance; a statically generated Nuxt site does not.

Nuxt

Nuxt hosting, from git push to live in one step

Server-rendered with Nitro or statically generated to the edge - we detect which and deploy it the right way. Connect a repo, push, and your Nuxt app is built into an isolated container and put online.

Start free trial See pricing

14 days free. No credit card. No commitment.

Push to deploy

GitHub, GitLab, Bitbucket

SSR or static

Nitro, auto-detected

One-click rollback

Promote any build

14-day free trial

No credit card required

99.9% uptime SLA

Container isolation

Using an AI coding assistant?

Point it at the plain-text build guide so it configures your deploy correctly. It is the same contract our docs describe, formatted for machines.

Deploying a specific stack?Node.js Nuxt Python Ruby Static & SPA Build guide

$ curl https://www.hostney.com/build-guide.txt

Pricing

Simple, transparent pricing

Every plan includes managed WordPress, SSH access, daily backups, and enterprise-grade security. Start with a 14-day free trial.

Startup

Great for growing businesses

$7.99/mo

$94.99 billed annually

Get started

1 website
10 GB storage
~10,000 visits/month
5 MySQL databases
250,000 inodes
5 FTP users

What's included:

SSL & Domain

Free SSL certificate
Free starter domain

Apps & CMS

1-click WordPress
Managed WordPress
WordPress staging

Advanced

For professional websites

$14.99/mo

$179.99 billed annually

Choose plan

5 websites
20 GB storage
~110,000 visits/month
10 MySQL databases
500,000 inodes
10 FTP users

Everything in Startup, plus:

Backups

14 days of backup history

Performance

Memcached

Pro

Maximum performance and features

$22.99/mo

$274.99 billed annually

Go pro

10 websites
40 GB storage
~200,000 visits/month
20 MySQL databases
750,000 inodes
20 FTP users

Everything in Advanced, plus:

Deployment

2 SSR applications

Backups

30 days of backup history

Compare plans

Two ways to ship

SSR or static - your nuxt.config decides

You don’t pick a hosting type. We read how your app builds and route it to the right place automatically.

Server-rendered (Nitro)

A standard Nuxt build runs as a live Node container. Server-side rendering, Nitro server routes, and API handlers all run for real - the same as your local dev server.

Full SSR and hydration
Nitro server routes & API
Runs in an isolated container
Live logs and one-click restart

Static generate

Run nuxt generate and the pre-rendered output is served from our edge cache - fast, globally close to visitors, and it doesn’t use one of your app slots.

Pre-rendered HTML to the edge
No container, no app slot used
Ideal for content & marketing sites
Instant cache-served responses

What you get

A deployment pipeline built for Nuxt

Connect a repository once. Every push runs through the same build, health-check, and promote pipeline - with rollback always one click away.

Git push deploys

GitHub, GitLab, or Bitbucket over OAuth or a token. A push registers a webhook and triggers a build automatically.

Nuxt auto-detection

We recognize Nuxt from your package.json, pick your package manager, and set install, build, and start commands. Override any of them.

Isolated containers

A server-rendered app runs in its own Podman container as a managed service with dedicated CPU and memory.

Blue/green deploys

A new build starts on a fresh port and only takes traffic after a health check passes. If it fails, the old build keeps serving.

One-click rollback

Promote a previous build back to live in seconds. No rebuild, no Git revert - the artifact is already there.

Static to the edge

Generated output goes to our Cloudflare-backed edge cache and is served close to your visitors.

Env vars & secrets

Build-time and runtime variables in the panel. Mark any as a secret and the value is sealed - write-only, never shown again.

Live logs

Stream Nitro output and platform events straight from the panel. See what your server did without opening SSH.

How it works

Push. Build. Live.

Three Git providers, one pipeline, and a health check that keeps a broken build from ever reaching your visitors.

Connect your repository

Link GitHub, GitLab, or Bitbucket, pick the repo and branch, and a push webhook is registered for you.

We detect and build

Each push clones the commit, detects Nuxt and your package manager, and builds in a resource-capped build container. SSR builds are packaged as a versioned image; generate output is uploaded to the edge.

Health-check and promote

A server-rendered container has to answer on its port within 30 seconds before going live. On Auto deploy it promotes itself; on Build only you promote when ready.

Build #v8

Current

Repositoryshop-nuxt / main

FrameworkNuxt

ModeSSR · Auto deploy

Build log

✓ Detected Nuxt · yarn

✓ Dependencies installed

✓ nuxt build (Nitro)

✓ Health check passed

✓ Promoted to production

Plain Vue SPA instead of Nuxt?

If you’re shipping a client-side Vue app rather than a server-rendered Nuxt one, it deploys as a static build to the edge - no container needed. Same Git pipeline, same one-click deploys.

See static & SPA hosting

Ship it

Deploy your Nuxt app in minutes

Connect a repo, push, and watch it go live - SSR or static. Included in every plan. Start free for 14 days, no credit card.

Start your free trial

Questions