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.
14 days free. No credit card. No commitment.
Push to deploy
GitHub, GitLab, Bitbucket
Same price
On renewal, every year
99.99%
Uptime, last 12 mo
Daily
Backups kept up to 30 days
190+
Tasks Ellie handles
Two ways to ship
SSR or static - your nuxt.config decides
You do not 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 does not 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
CurrentBuild log
✓ Detected Nuxt · yarn
✓ Dependencies installed
✓ nuxt build (Nitro)
✓ Health check passed
✓ Promoted to production
The pipeline
What happens between push and live
Five stages, every time, with the previous build kept the whole way through.
Push
A commit lands on the tracked branch.
Detect
We read package.json, recognise Nuxt, and pick your package manager and commands.
Build
Install and build run in a resource-capped container. The result is a versioned image.
Health check
The new container must answer on its port within 30 seconds.
Live
It takes over traffic. The previous build stays, one click away.
Runtime
A real container, with a live view of it
A server-rendered Nuxt app is a managed service with its own resources, automatic restarts, and logs you can read without opening SSH.
Nitro binds itself
Nuxt reads PORT automatically through Nitro, so the one rule that catches out most server apps is already handled. Nothing to configure.
Managed as a service
The container runs as its own system service. If it crashes it restarts within seconds, without anyone watching it.
Restart without redeploy
Bounce the container from the panel to clear a stuck process, keeping the exact same build.
Server routes are real
Nitro server routes and API handlers run for real, the same as your local dev server. This is not a static export pretending.
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 hostingPricing
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
$94.99 billed annually
- 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
$179.99 billed annually
- 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 object cache
- Redis object cache
Monitoring
- 5 minutes between checks
Pro
Maximum performance and features
$274.99 billed annually
- 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
Monitoring
- 1 minute between checks
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.
Questions