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 WordPress

Run WordPress with Wodby’s managed WordPress stack. Keep deployments repeatable, handle traffic growth more cleanly, and manage multiple WordPress projects with a more consistent hosting model.

Start with Wodby View WordPress stack

Deploy WordPress faster with a managed stack

Start from a WordPress stack built for Kubernetes instead of piecing together services, deployment logic, and runtime configuration manually.

Use a scalable WordPress hosting model

Run WordPress with a managed stack that supports cleaner scaling, better service isolation, and more repeatable deployments across environments.

Keep operations simpler across multiple sites

Use built-in releases, backups, SSL, and environment management so your team can handle WordPress hosting with less repetitive infrastructure work.

Bring an existing application

Plan your WordPress 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

WordPress migration planning prompt

Use get_wodby_guidance to load the Wodby migration workflow. Inspect this WordPress 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.

A modern deployment model for WordPress

WordPress teams benefit from a more scalable and standardized hosting model, especially when traffic patterns vary or multiple projects need to be managed consistently.

Wodby packages WordPress as a managed stack on top of managed and self-hosted Kubernetes foundations, so agencies and businesses can modernize operations without building a custom layer around every site.

A practical fit for WordPress workloads

Keep web, PHP runtime, cache, and database services organized in a managed stack.
Scale for traffic spikes, campaigns, and content-heavy workloads more cleanly.
Use a repeatable deployment model across staging and production environments.
Reduce manual work around SSL, backups, upgrades, and infrastructure operations.

What you get with Wodby

Managed WordPress 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 WordPress 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 WordPress stack and connect your repository.
3
Configure services, domains, environment variables, persistent volumes, and databases.
4
Deploy changes through the built-in CI/CD workflow and scale when traffic grows.

Read more about stack management in our documentation.

Suitable for agencies, publishers, and multi-site WordPress hosting

If you manage multiple WordPress sites, need repeatable hosting environments, or want a more scalable deployment model, this setup is built for that pattern.

Wodby gives WordPress teams a managed stack while keeping room for customization and infrastructure growth over time, with Kubernetes available where its strengths matter most.

View pricing Explore infrastructure features

Start deploying

Want to launch WordPress with less setup overhead?

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

Start with Wodby View WordPress stack

Stack-specific feature

Modern WordPress deployment with Composer

For teams that want a more modern and repeatable way to manage WordPress, Wodby also supports a Composer-based deployment workflow.

Use Wodby’s WordPress Composer boilerplate as a starting point to keep WordPress core, plugins, themes, and project code under version control with a more modern, repeatable deployment model.

View the WordPress Composer boilerplate on GitHub

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

Caching with Vinyl

The WordPress stack includes Vinyl (Varnish) Cache as a built-in service for straightforward page and HTTP caching in front of WordPress.

That helps reduce response times and absorb traffic spikes more efficiently without forcing WordPress and PHP to handle every anonymous request directly.

Stack preview

WordPress stack preview

Stack service	Base service	Role
Vinyl	Vinyl (WordPress)	Primary
PHP SSHD	PHP (WordPress)	Required
Nginx	Nginx (WordPress)	Required
WP content NFS storage	Ganesha NFS provisioner	Enabled by default
Mailpit	Mailpit	Enabled by default
Gotenberg	Gotenberg	Enabled by default
Valkey	Valkey	Enabled by default
MariaDB	MariaDB	Enabled by default
Cloud MariaDB	Cloud MariaDB	Disabled by default
Cloud MySQL	Cloud MySQL	Disabled by default
OpenSMTPD	OpenSMTPD	Disabled by default

See full stack service table

Keep moving

Explore the WordPress setup, then start your own deployment

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

Create account Check pricing

Stack-specific feature

Object caching with Redis

The stack also includes Redis for object caching. Connect WordPress to Redis with a compatible Redis object cache plugin to reduce repeated database work and improve performance for cache-heavy sites.

This is especially useful for dynamic WordPress workloads where faster object caching can lower database load and make the application more responsive under sustained traffic.

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

Stack-specific feature

Keep local WordPress environments consistent with Docker

Use Wodby’s Docker4WordPress project to spin up a consistent local WordPress environment with Docker Compose before you deploy to Wodby. It gives agencies and site teams a repeatable setup for local development across Linux, macOS, and Windows.

That keeps the path from local work to managed hosting cleaner: develop against a containerized WordPress stack locally, then deploy to Wodby for production infrastructure, CI/CD, backups, certificates, and scaling.

View Docker4WordPress on GitHub

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

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