Supported stacks

Nuxt hosting
on Shipped.

Ship your Nuxt pages, server endpoints, and content in the form your application needs. Shipped handles the infrastructure around them.

Choose the output that fits your pages

Nuxt can generate a static site or run an application server. Use static hosting for a generated site and a web service when your routes depend on server execution. Match the build output to the deployment so authentication, dynamic pages, and server endpoints keep their intended behavior.

Keep private configuration on the server

Connect your Nuxt server to PostgreSQL and other app services using secrets. Expose only configuration intended for the browser through public runtime settings. This gives server endpoints access to what they need without sending database credentials or private integration tokens along with your client-side application.

Give content changes a review URL

A staging environment makes it easier to review navigation, content queries, and authenticated flows together. Ship from your agent as you work, or connect GitHub for repository-driven deployments. Add your production domain when the site is ready, with HTTPS managed by Shipped.

A little more detail

Questions about Nuxt?

Do I need a server for a generated Nuxt site?

A fully generated site can use static hosting. If your app depends on server routes, runtime rendering, or server-only integrations, deploy its server output as a web service.

Can I separate public and private Nuxt settings?

Yes. Keep private values in server runtime configuration and supply them using Shipped secrets. Values intentionally exposed through Nuxt public configuration must be treated as visible to visitors.

From your workspace to the web

Ready to ship your app?

Start shipping