Can I use my coding agent with Wodby? Do I need one?

You can connect a supported coding agent through MCP to plan migrations, prepare staging deployments, and troubleshoot applications using Wodby workflows. An agent is optional: you can continue using the dashboard, CLI, and API.

How do I control what an agent can change?

Use an OAuth connection with read-only permissions to start. OAuth scopes limit the available operations, and your Wodby permissions determine which resources the agent can access. Grant additional scopes only when needed, agree on the changes before execution, and revoke credentials when access is no longer needed. Review MCP-initiated tasks in task history; it is not a record of every read or the complete conversation.

What does using an agent with Wodby cost?

MCP access is included with free and paid Wodby 2 plans. Your plan limits and feature requirements still apply. Agent-created services, builds, storage, and infrastructure follow normal billing. Any charges from your agent or model provider are separate.

Do I need to have an account on a cloud provider to use Wodby?

You can connect your own managed Kubernetes provider or use one dedicated server for self-hosted Kubernetes. Alternatively, you can use Wodby Cloud when you do not want the cluster in your own cloud account or on your own server.

Can I use Wodby with a dedicated server?

Yes. Wodby supports budget single-server self-hosted Kubernetes setups with K3s, a lightweight open-source Kubernetes distribution, when you do not need Kubernetes scaling.

I couldn't find my specific application stack, how do I start?

Start with the closest pre-configured stack and customize it, or build a stack from managed services. You can also contact Wodby to request a new stack.

Will I be vendor locked-in to Wodby?

No. Wodby is built on open standards like Kubernetes. You can disconnect your cluster and keep running your apps, but Wodby-managed tasks stop.

I have a small website (PHP, MySQL). How much would it cost? What if I deploy 10 of them?

Pricing is based on total app services. One site with Nginx, PHP-FPM, and MySQL is 3 services and falls under the $48/month minimum tier. Ten such sites total 30 services and cost $60/month. Extra CI/CD minutes and registry storage are billed separately.

Deploy Next.js

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

Start with Wodby View Next.js stack

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.

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.

Connect your agent Read the migration workflow

Next.js migration planning prompt

Use get_wodby_guidance to load the Wodby migration workflow. 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
Choose the infrastructure model that fits: managed Kubernetes from your preferred provider or a single-server self-hosted Kubernetes setup for budget hosting.
2
Create a new app from the Next.js stack and connect your repository.
3
Configure domains, environment variables, persistent services, and any supporting infrastructure.
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.

View pricing Explore infrastructure features

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.

Start with Wodby View Next.js stack

Hosting options

Choose the hosting model that fits your team

Run Wodby on your own managed Kubernetes, on a budget self-hosted Kubernetes server, or on fully managed Wodby Cloud.

Managed Kubernetes in your cloud account

Keep infrastructure in your own cloud account. Wodby provisions and manages the cluster setup through AWS, GCP, DigitalOcean, Azure, or another supported provider.

View managed Kubernetes

Kubernetes on your own server

Keep control of your dedicated server or VM. Wodby prepares a single-server Kubernetes setup and provides tools to deploy and manage your apps.

Explore self-hosted Kubernetes

Fully managed Wodby Cloud

Use Wodby Cloud when you want the cluster hosted by Wodby instead of in your own cloud account or on your own server.

See Wodby Cloud

Integrations

Keep third-party integrations organized and under control across all of your apps and environments

Connect services once and reuse them across your apps. Keep credentials out of repositories, manage configuration centrally, and override values for each environment.

Connect the services your apps already use

See all integrations

Stack preview

Next.js stack preview

Stack service	Base service	Role
Node.js	Node.js (Next.js)	Primary
Mailpit	Mailpit	Disabled by default
Gotenberg	Gotenberg	Disabled by default
Valkey	Valkey	Disabled by default
OpenSMTPD	OpenSMTPD	Disabled by default
PostgreSQL	PostgreSQL	Disabled by default

See full stack service table

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.

Create account Check pricing

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
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

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