Deploy Drupal

Run Drupal with Wodby’s ready-to-run managed stack. Launch production environments faster, standardize deployments, and keep day-to-day operations simpler while relying on industry-standard infrastructure under the hood.

Launch production-ready Drupal faster

Start from a managed Drupal stack instead of assembling services, ingress, build pipelines, and runtime settings by hand.

Use a managed Drupal deployment model

Give your Drupal team a ready-to-run stack with preconfigured infrastructure, scaling controls, and a cleaner deployment workflow.

Keep updates, backups, and SSL under control

Use built-in platform features for releases, certificates, backups, and recurring tasks so your team can focus on Drupal delivery.

Build and release

What a Drupal deployment does on Wodby

A Drupal deployment begins with one of two boilerplates, Drupal CMS or Vanilla Drupal, or with your own Composer-based repository. After the first deployment you complete the Drupal installer in the browser.

Match the Drupal root to your layout

The stack looks for the Drupal root in a subdirectory called web. For a repository laid out differently, change the Drupal root subdirectory setting on the PHP app service.

Finish the installer on the main domain

When the first deployment is done, open the main domain of the app and go through the installer. If you leave it partway, return to the core install page to carry on.

Keep the Wodby settings include

A repository that brings its own site settings file must keep the line that includes the settings Wodby generates, and place its overrides after it. The generated file is never edited by hand in a running container.

Configuration sync in your repository

Out of the box the configuration sync directory is on persistent storage, not in Git. Override the sync directory in your own settings when configuration should travel with the application repository.

Bringing an existing site

To move a site that already exists, load its files with an application import and its content with a database import. Interactive work on a running container goes through the web terminal.

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

Bring an existing application

Plan your Drupal 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.

Drupal migration planning prompt
Load Wodby’s migration guidance. Inspect this Drupal 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 Drupal

Drupal teams need predictable deployments, easier scaling, better workload isolation, and infrastructure they can standardize across environments as projects grow.

Wodby makes that practical by packaging Drupal as a managed stack on top of managed and self-hosted Kubernetes foundations, so agencies and in-house teams get a modern platform model without turning every project into a platform engineering effort.

A practical fit for Drupal workloads

  • Separate web, PHP, cache, and database concerns into managed services.
  • Scale horizontally for traffic spikes, launches, and editorial campaigns.
  • Standardize staging and production around the same deployment model.
  • Reduce custom operations work around routing, certificates, backups, and releases.

What you get with Wodby

  • Managed Drupal 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 Drupal 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 Drupal stack and connect your repository.

  3. 3

    Configure services, domains, environment variables, persistent volumes, and databases.

  4. 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, product teams, and Drupal specialists

If you manage multiple Drupal sites, need repeatable environments, or want to modernize delivery without becoming a full-time platform team, this setup is built for that use case.

Wodby gives you a consistent way to deploy Drupal across projects while keeping room for customization through services, integrations, and Kubernetes-native infrastructure where it adds value.

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

Start deploying

Want to launch Drupal with less setup overhead?

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

Stack-specific feature

Drupal CMS 2.0 boilerplate

Wodby’s default Drupal boilerplate is based on Drupal CMS 2.0. You can clone it, use it as a starting point, and customize it for your project instead of assembling a new baseline from scratch.

If you prefer a leaner starting point, you can also deploy vanilla Drupal with the same Wodby stack and infrastructure model.

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 Wodby Cloud. Wodby maintains the cluster on all three.

Managed Kubernetes in your cloud account

Keep infrastructure in your own cloud account. Wodby provisions the cluster through AWS, GCP, DigitalOcean, Azure, or another supported provider and keeps it up to date.

View managed Kubernetes

Kubernetes on your own server

Use your own dedicated server or VM for the lowest cost. Wodby installs Kubernetes, keeps it up to date, and deploys your apps; you keep the server’s operating system updated.

Explore self-hosted Kubernetes

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.

See all integrations
Stack-specific feature

Keep local Drupal environments consistent with Docker

Use Wodby’s open source Docker4Drupal project to spin up a consistent local Drupal environment with Docker Compose before you deploy to Wodby. It is designed for local development across Linux, macOS, and Windows, which makes onboarding and day-to-day development more predictable.

That gives teams a cleaner path from local work to managed deployments: develop against a repeatable containerized stack locally, then move to Wodby for production infrastructure, CI/CD, backups, certificates, and scaling.

Stack preview

Drupal stack preview

Stack serviceBase serviceRole
Vinyl (Drupal)Primary
PHP (Drupal 11)Required
Nginx (Drupal 11)Required
ValkeyEnabled by default
MariaDBEnabled by default
MailpitEnabled by default
Ganesha NFS provisionerEnabled by default
PostgreSQLDisabled by default
SolrDisabled by default
ZooKeeperDisabled by default
Cloud MariaDBDisabled by default
Cloud MySQLDisabled by default
OpenTelemetry CollectorDisabled by default
GotenbergDisabled by default
OpenSMTPDDisabled by default

Keep moving

Explore the Drupal setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Drupal, 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 Drupal?

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