Deploy Next.js on Kubernetes

Run Next.js applications on Kubernetes with Wodby’s managed stack. Standardize deployments, keep environments consistent, and ship frontend workloads faster with less operational overhead.

Deploy Next.js faster with a managed stack

Start from a Next.js stack designed for Kubernetes instead of assembling runtime services, ingress, build steps, and deployment wiring by hand.

Keep frontend delivery predictable

Use a repeatable Kubernetes workflow for Next.js applications with preconfigured infrastructure, clearer environments, and simpler scaling.

Reduce platform overhead for app teams

Use built-in deployment, SSL, backups, and infrastructure management so your team can focus more on shipping product changes.

Build and release

What a Next.js deployment does on Wodby

A Next.js deployment copies your build context into the image, runs your build script as part of the image build, and launches the container through your start script. Installing dependencies is a step in your pipeline.

Two scripts your package file needs

The package file has to define a build script and a start script, normally the Next.js build and start commands. The first runs during the image build and the second starts the container.

Install before the image build

Dependencies are not installed by the service's Dockerfile. An install step in the pipeline, placed before the image build, makes the modules directory part of the image.

Prerendering cannot see runtime values

While the build script runs, neither link variables nor secrets exist. A page that depends on them has to be rendered when it is requested, not prerendered at build time.

Development server in a workspace

A development workspace starts the Next.js development server directly, so options written into your dev script are not applied. The Node environment is development there, and the build step is skipped.

Read the Next.js stack guide for setup steps, settings, and limits.

Bring an existing application

Plan your Next.js migration with your agent

Give your coding agent access to your repository and connect Wodby through MCP. Ask it to map your app to maintained services and flag what needs to change before deploying.

Review the plan first, then approve an isolated staging deployment. Production data transfer and cutover need separate approval. MCP access does not itself grant access to your repository.

Next.js migration planning prompt
Load Wodby’s migration guidance. Inspect this Next.js application repository and propose a Wodby deployment plan. Identify the runtime, database, background jobs, persistent files, and required secret names without revealing values. List missing information and plan an isolated staging deployment. Do not create resources, transfer production data, change DNS, or deploy anything yet.

Why run Next.js on Kubernetes?

Next.js teams need a clean way to standardize deployments, isolate supporting services, and scale application workloads across environments.

Wodby turns that into a managed Next.js stack built on managed and self-hosted Kubernetes foundations, so teams can modernize delivery without rebuilding the same infrastructure layer around every frontend project.

A practical fit for Next.js workloads

  • Standardize builds, runtime configuration, and deployment flow across environments.
  • Scale Next.js applications more cleanly as traffic and project scope grow.
  • Keep supporting services organized within a managed Kubernetes setup.
  • Reduce custom work around certificates, releases, backups, and platform operations.

What you get with Wodby

  • Managed Next.js stack for modern container-based deployments
  • Built-in CI/CD with image builds, deployment history, and rollback attempts
  • Controlled automatic updates for stack services, app environments, and infrastructure
  • Automated backups and imports for safer releases and migrations
  • Managed routes, endpoints, and domain setup
  • App service controls for settings, resources, links, volumes, actions, and terminal access
  • Open, portable infrastructure via Wodby’s platform model

How Next.js deployment works on Wodby

  1. 1

    Choose the infrastructure model that fits: managed Kubernetes from your preferred provider or a self-hosted Kubernetes setup on your own servers for budget hosting.

  2. 2

    Create a new app from the Next.js stack and connect your repository.

  3. 3

    Configure domains, environment variables, persistent services, and any supporting infrastructure.

  4. 4

    Deploy changes through the built-in CI/CD workflow and scale as traffic grows.


Read more about stack management in our documentation.

Suitable for product teams, frontend platforms, and full-stack apps

If you deploy multiple Next.js projects, need repeatable environments, or want a stronger production workflow, this setup fits that operating model.

Wodby gives Next.js teams a managed stack with enough flexibility to support both standalone frontends and larger application platforms, with Kubernetes as a proven infrastructure standard behind it.

Still choosing where to run it? Compare the options on the Next.js hosting page.

Start deploying

Want to launch Next.js with less setup overhead?

Start with Wodby's managed Next.js stack, connect your repo, and handle deployments, environments, and operations in one place.

Hosting options

Run your apps where it suits you

In your own cloud account, on a server you already rent, or on Wodby Cloud. The stacks and the deployment workflow are the same on all three, and Wodby maintains the cluster.

Lowest cost

Kubernetes on your own server

Use a dedicated server or VM you already rent, from Hetzner, OVH, or any other host. Wodby installs Kubernetes on it, keeps it up to date, and deploys your apps.

  • No managed control plane to pay for
  • One command installs Kubernetes on the server
  • Join more servers as worker nodes when you need capacity
  • Operating system updates install when you choose
Explore self-hosted Kubernetes

We handle everything

Wodby Cloud

Deploy without a cloud account or a server of your own. Wodby creates and operates the cluster, and you pay for the nodes and storage you run.

  • Nothing to connect or set up before your first deploy
  • A free demo cluster to try the workflow first
  • Scales between the node counts you set
  • The same stacks and deployment workflow as your own cluster
See Wodby Cloud

Connect the services your apps already use

An integration links Wodby to an account you already have, such as your Git provider, a storage bucket for backups, or an API your app calls.

Connected once
Set up a service once and reuse it across your apps.
Out of your code
Credentials stay out of your repositories and are managed in one place.
Per environment
Override any value for each environment.
Stack preview

Next.js stack preview

Stack serviceBase serviceRole
Node.js
Node.js (Next.js)Primary
PostgreSQL
PostgreSQLDisabled by default
Valkey
ValkeyDisabled by default
Mailpit
MailpitDisabled by default
OpenSMTPD
OpenSMTPDDisabled by default
Gotenberg
GotenbergDisabled by default
OpenTelemetry Collector
OpenTelemetry CollectorDisabled by default

Keep moving

Explore the Next.js setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Next.js, connect your repository, and keep delivery inside the same workflow.

Trusted by developers and businesses worldwide since 2015

Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.

  • We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.

    Tony Miller
    Eighty Options
    Tony Miller, Eighty Options
  • Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.

    Martin Normann Lund
    Ramsalt Lab
    Martin Normann Lund, Ramsalt Lab
FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Get started

Ready to deploy Next.js?

Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.

  • Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
  • Deploy app environments for production, staging, previews, and development
  • Use Wodby CI or your existing pipeline with the Wodby CLI
  • Keep backups, certificates, integrations, and access control in the platform

Start for free

No credit card required
$0/month
  • 10 app services
  • 30 minutes of integrated CI
  • 5 GB of private registry
  • Stacks & integrations
  • Technical domains with SSL
Create free account
Upgrade when you need more capacity