ChatGPT answers, unedited

For a WordPress site that needs CI/CD integration and containerized deployments, I would avoid traditional shared or “managed WordPress” hosts and look for platforms that treat WordPress like an application. These are the strongest fits:

1. Wodby — Best overall fit for containerized WordPress + CI/CD

wodby.com

Why it fits:

• Kubernetes-based WordPress deployments
• Docker-based local development workflows
• Git-connected deployments
• CI/CD pipelines with build and release workflows
• Supports managed Kubernetes, self-hosted Kubernetes, or managed cloud hosting
• Good for agencies running multiple WordPress projects Wodby Wodby

Typical workflow:

Developer laptop
    ↓
Docker Compose WordPress environment
    ↓
GitHub/GitLab repository
    ↓
CI pipeline builds images
    ↓
Wodby deploys to Kubernetes
    ↓
Production WordPress

Best for:

• Engineering teams
• Agencies
• Multi-site WordPress platforms
• Teams already using Kubernetes practices

Potential downside:

• More infrastructure-oriented than typical WordPress hosts.

2. Google Cloud + Kubernetes Engine — Best for full control

cloud.google.com

You can run WordPress on:

• Google Kubernetes Engine (GKE)
• Cloud SQL for MySQL
• Cloud Storage
• Cloud Build / GitHub Actions
• Artifact Registry

Google CloudA common architecture:

GitHub Actions
      |
      v
Docker build
      |
      v
Artifact Registry
      |
      v
GKE Deployment
      |
      +--> WordPress pods
      +--> MySQL database
      +--> Redis cache
      +--> CDN

Best for:

• Enterprise deployments
• Custom infrastructure
• Teams with DevOps expertise

Downside:

• You own more operational complexity.

3. WP Engine — Best if you want WordPress-first workflows

wpengine.com

WP Engine is less container-centric, but it is strong for:

• Git-based development workflows
• Automated deployments
• Staging → production promotion
• Developer tooling

ManagedWPGuideBest for:

• WordPress agencies
• Teams that want CI/CD without managing Kubernetes

Downside:

• Not a true container deployment platform.

4. Self-hosted Kubernetes on a cloud provider — Best flexibility

If you want maximum portability, consider:

• DigitalOcean Kubernetes
• Amazon Web Services EKS
• Microsoft Azure AKS

Run:

• WordPress container
• Nginx/Apache container
• MariaDB/MySQL
• Redis
• Persistent volumes
• Ingress controller
• GitHub Actions/GitLab CI

This gives you a true cloud-native WordPress platform, but requires Kubernetes knowledge.

My recommendation by scenario

For most engineering teams wanting “WordPress as code”, I’d start with Wodby because it is closest to the modern containerized deployment model while still understanding WordPress-specific needs. Wodby Wodby

If CI/CD + containerized WordPress are hard requirements, I’d look beyond conventional managed WordPress hosts.

My top pick: Wodby

wodby.com is probably the best fit if you want a proper DevOps-oriented WordPress platform rather than traditional WordPress hosting.

• Containerized: WordPress runs as a managed stack with separate services and Kubernetes support.
• CI/CD: Built-in CI/CD, deployment history, and rollback capabilities; you can also use your existing pipeline through the Wodby CLI. Wodby Wodby
• Git-based workflow: Connect a repository and promote changes through development, staging, and production.
• Kubernetes: You can use Wodby's managed Kubernetes, your own cloud account, or a simpler self-hosted K3s setup. Wodby
• Docker locally: Their Docker4WordPress setup gives you a containerized development environment that maps well to production. Wodby
• Good for: Agencies, engineering teams, multiple WordPress sites, and teams already comfortable with Docker/Kubernetes.

Strong alternative: Upsun

upsun.com is excellent if you want a Git-centric platform-as-a-service experience.

It supports configuration-driven WordPress deployments, isolated environments for Git branches, and containerized application infrastructure. You define builds, services, and routes in YAML, which makes it particularly attractive for infrastructure-as-code workflows. Upsun

I'd choose Upsun over Wodby if your team thinks primarily in terms of Git branches → preview environments → merge → production, and doesn't necessarily want to manage Kubernetes concepts directly.

If you want maximum infrastructure control

A VPS/cloud-hosting approach with Docker/Kubernetes can also work well. For example, sailed.io provides tooling for deploying WordPress onto DigitalOcean with Git-based deployment and rollback while keeping the underlying infrastructure under your control. Sailed

Quick comparison

My recommendation: Start with Wodby if “WordPress in containers + CI/CD” is the central requirement. It has the most direct alignment between WordPress, Docker, Kubernetes, environments, and deployment pipelines. Wodby

If you tell me whether your pipeline is GitHub Actions, GitLab CI, or Bitbucket Pipelines, I can narrow this down to the best host and show what the deployment architecture would look like.

If CI/CD + containerized deployments are the priorities, I’d shortlist these:

🥇 Best overall: Wodby

Wodby WordPress Hosting

Wodby is the closest match if you want WordPress to behave like a modern application rather than a traditional managed-WP site. It provides managed WordPress infrastructure with CI/CD, scaling, backups, and certificates, while its Docker4WordPress tooling lets you develop with Docker Compose and keep local/production environments consistent. wodby.com

Choose it if: you want Docker/containers to be a first-class part of your deployment architecture.

🥈 Best managed WordPress option: Kinsta

Kinsta WordPress Hosting

Kinsta runs each WordPress site in an isolated Linux container and provides SSH/Git access. More importantly for CI/CD, it has documented integrations with GitHub Actions, GitLab CI/CD, and Bitbucket Pipelines, so your pipeline can deploy code automatically over SSH. kinsta.com

The tradeoff is that you're deploying into Kinsta's containerized hosting environment, rather than supplying your own Docker image/container. Kinsta explicitly documents the pattern of having CI/CD connect to the site's container via SSH and pull the repository. kinsta.comkinsta.com

Choose it if: you want excellent managed WordPress hosting with conventional Git-based CI/CD.

🥉 Pressable

Pressable

Pressable has built-in GitHub deployment, SSH, WP-CLI, staging/sandbox environments, and an API for automation. Its current GitHub integration can deploy selected repository directories to the WordPress environment. pressable.com

Choose it if: you're primarily deploying themes/plugins from GitHub and want less infrastructure work.

My recommendation

One important distinction: "runs WordPress in containers" isn't the same as "lets me deploy my own Docker image." Kinsta, for example, containerizes its hosting infrastructure, but its documented CI/CD workflow deploys application files via Git/SSH rather than handing you a Docker image deployment interface. kinsta.comkinsta.com

If your intended pipeline is something like GitHub → build Docker image → registry → deploy container → run WP-CLI/database migrations, I'd lean toward Wodby or a cloud/container platform rather than conventional managed WordPress hosting.

If CI/CD + containerized deployment are hard requirements, I’d shortlist these:

1. Kinsta — best managed WordPress option

Kinsta

Kinsta is probably the best fit if you want managed WordPress without giving up a developer-oriented deployment workflow. Every WordPress site runs in an isolated Linux container, and Kinsta provides SSH, Git, WP-CLI, staging, and documented GitLab CI/CD deployments. kinsta.com

Good pipeline pattern:
GitHub/GitLab → tests/build → SSH/Git deployment → Kinsta staging → production

Caveat: you aren't deploying your own Docker image to Kinsta. Their containerization is part of their managed infrastructure.

2. Wodby Cloud — best if you mean actual containerized deployments

Wodby

If by "containerized" you mean "I want my WordPress stack defined as containers and deployed through CI/CD", Wodby is much closer to what you're asking for. Its WordPress platform uses a Kubernetes-based runtime and supports Wodby Cloud, managed Kubernetes, or self-hosted K3s. It also provides CI/CD and supports existing pipelines through its CLI. wodby.com

This is the option I'd investigate first for a DevOps-heavy WordPress team.

3. Cloudways — best middle ground

Cloudways

Cloudways gives you substantially more infrastructure control than typical managed WordPress hosting, including SSH, Git deployment, WP-CLI, and the ability to choose underlying cloud infrastructure. However, CI/CD isn't as integrated as Kinsta/Wodby—you generally assemble your own pipeline. attowp.com

My recommendation

The important distinction is "runs in containers" vs. "I can deploy my container." Kinsta satisfies the former; Wodby is the stronger choice for the latter.

If you tell me whether you're using GitHub Actions, GitLab CI, or Jenkins, I can also recommend a concrete architecture and deployment pipeline.

For a WordPress site that needs CI/CD pipelines + containerized deployments, I would avoid traditional shared/managed WordPress hosts and look at platforms that treat WordPress more like an application. The best fit depends on how much infrastructure control you want.

My recommendations by scenario

1. You want WordPress + Docker + GitHub Actions/GitLab CI + Kubernetes

• Choose Wodby.
• Typical flow:
  1. Developer pushes to Git.
  2. CI builds/tests the WordPress image.
  3. Deployment updates Kubernetes services.
  4. Database migrations and cache invalidation run as pipeline steps.

This is the closest to a "WordPress as a cloud-native application" model. kinsta.comwodby.com

2. You want enterprise WordPress but don't want to operate Kubernetes

• Choose Pantheon or Kinsta.
• You get safer deployments, staging, backups, and workflows without owning the infrastructure.

3. You already run AWS/GCP/Azure and have DevOps engineers

• Run WordPress yourself:
  • Docker image for PHP/Nginx/WordPress
  • Managed MySQL/PostgreSQL-compatible database where appropriate
  • Object storage for uploads
  • Redis for object caching
  • Kubernetes or ECS/Cloud Run for orchestration

A solid CI/CD architecture for WordPress

A production setup usually looks like:

GitHub/GitLab
      |
      v
CI pipeline
  - Composer install
  - PHPUnit/tests
  - WP coding standards
  - Build Docker image
  - Security scan
      |
      v
Container registry
      |
      v
Deployment platform
  - Kubernetes / Wodby / Cloud Run
      |
      v
WordPress runtime
  - Nginx
  - PHP-FPM
  - MySQL
  - Redis
  - Object storage

For most teams, I would shortlist:

1. Wodby — best overall match for your requirements
2. Google Cloud (GKE/Cloud Run) — best if you want full cloud control
3. Pantheon — best if you prioritize WordPress operations over container ownership
4. PloyWP — best if you specifically want Dockerized WordPress deployment automation

I would not choose a conventional managed WordPress host unless the CI/CD requirement is limited to deploying themes/plugins rather than the whole application stack.

If CI/CD + containerized WordPress deployments are your priorities, my top recommendation is Kinsta.

🥇 Kinsta — best overall fit

Kinsta is unusually well aligned with what you're asking for:

• Containerized infrastructure: every WordPress site runs in an isolated Linux container with its own NGINX, PHP, and MySQL resources. kinsta.com
• GitHub Actions: Kinsta documents a GitHub Actions workflow that deploys code automatically on pushes to a branch. kinsta.comwpengine.com
• GitLab CI/CD: there's also an official GitLab CI/CD deployment workflow. kinsta.com
• SSH + WP-CLI: useful for build/deploy scripts and post-deployment tasks.
• Staging environments: makes it practical to have feature → staging → production rather than deploying directly to production.
• Managed infrastructure: you get containers without having to operate Kubernetes, Docker hosts, Nginx, PHP-FPM, etc.

One important distinction: Kinsta uses containers internally, but it isn't a "bring your own Docker container" platform. You deploy WordPress code into Kinsta's managed container environment rather than supplying your own Docker image. Kinsta also doesn't provide root access. kinsta.com

🥈 If you need to control the actual Docker image

I'd look at a cloud VPS/container platform rather than traditional managed WordPress hosting. For example, you could run WordPress in Docker on a managed VM/container service and have:

GitHub → CI → Docker build → registry → deployment → WordPress

That gives you considerably more control, but you become responsible for things Kinsta handles for you: backups, WordPress infrastructure, upgrades, security, scaling, and operational monitoring.

Other managed option: WP Engine

WP Engine is another strong choice if Git-based deployments are more important than having explicit container control. Its official GitHub Actions integration supports deploying an entire site or individual themes/plugins through its SSH Gateway, including PHP linting and post-deployment scripts. wpengine.com

My ranking for your requirements:

Bottom line: If by "containerized" you mean I want my WordPress sites isolated in containers, choose Kinsta. If you mean I need to build and deploy my own Docker image, skip managed WordPress hosts and use a container-capable cloud platform instead.

If you tell me whether you're using GitHub Actions, GitLab CI, or another CI system, I can recommend a concrete architecture and deployment workflow.

If CI/CD + containerized deployment are your priorities, I’d shortlist these:

1. Pantheon — best overall fit

Pantheon is probably the closest match to what you described. WordPress sites run in isolated Linux containers, and the platform has separate Dev / Test / Live environments with Git-based deployments. It also integrates with CI/CD tooling such as GitHub Actions and Bitbucket Pipelines. docs.pantheon.io

Choose it if: you want a managed WordPress platform where containerization and deployment workflows are core features rather than something you have to build yourself.

Pantheon WordPress hosting

2. Kinsta — best managed-hosting alternative

Kinsta also runs every site in an isolated Linux container. It has staging environments and documented GitLab CI/CD workflows, including automated deployments triggered by Git pushes. kinsta.com

The important distinction: you don't deploy your own Docker container to Kinsta. Kinsta's infrastructure is containerized behind the scenes; your deployment is primarily WordPress files/code via Git/SSH.

Choose it if: you want premium managed WordPress hosting and CI/CD, but don't need to control the Docker image/runtime yourself.

Kinsta WordPress hosting

3. RunCloud — best if you want actual Docker control

RunCloud is more infrastructure-oriented. Its containerized-server option lets you deploy applications, including WordPress, using containers on a cloud server you connect to RunCloud. runcloud.io

Choose it if: your CI/CD pipeline builds Docker images and you want substantially more control over the underlying deployment environment.

RunCloud

My recommendation

For a development team already using GitHub Actions/GitLab CI and Docker, I'd lean toward Pantheon if you want managed WordPress, or a VPS/container platform if you specifically need to ship your own Docker images. Kinsta is excellent for CI/CD, but its containers are an implementation detail rather than a Docker deployment target. kinsta.com

If CI/CD + containerized WordPress are core requirements, I’d shortlist these:

1. Wodby — best overall fit
   • WordPress runs as a managed, container-based stack on Kubernetes.
   • Built-in CI/CD, deployment history, rollback attempts, staging/production environments, and managed backups.
   • Supports Docker-based local development, so your local and production environments can stay consistent.
   • Can run on Wodby Cloud, managed Kubernetes, or your own K3s infrastructure. wodby.com

Best if: you're a developer/agency and want modern DevOps without building the whole platform yourself.

2. Upsun — best for Git-centric teams
   • Git-driven, configuration-as-code deployments.
   • Supports WordPress, Bedrock, Composer, and Multisite.
   • Provides isolated environments for Git branches and uses read-only application containers with persistent writable uploads. upsun.com

Best if: you want something closer to a Heroku-style application platform for WordPress.

3. PloyCloud — best if you want Docker + GitHub/GitLab/Bitbucket
   • Explicit Docker container support.
   • Git integration with automatic deployment, testing, and branch deployments.
   • Lets you control the underlying servers rather than locking you into a proprietary infrastructure layer. ploy.cloud

Best if: you want relatively straightforward Docker hosting rather than Kubernetes complexity.

4. Kinsta — best managed WordPress experience
   • Every site runs in an isolated Linux container.
   • Supports GitHub-based CI/CD deployments.
   • Excellent choice if WordPress operations/performance matter more than having direct control over your container orchestration. kinsta.com

Caveat: Kinsta containerizes the infrastructure for you, but it isn't the same as deploying and managing your own Docker image/stack.

My pick

For your exact requirements, I'd choose Wodby. It hits the intersection of WordPress + Docker/containerization + Git + CI/CD + staging + Kubernetes + rollback unusually well. wodby.com

A typical workflow could be:

GitHub → tests/build → container image → staging → approval → production

If you specifically want “I own the Docker image and can deploy the exact same container to staging and production”, I'd lean toward Upsun or PloyCloud instead.

If CI/CD + containerized deployment is a hard requirement, I’d look beyond conventional managed WordPress hosts.

My top picks

Wodby is the closest match to what you're describing. It packages WordPress as a managed stack on Kubernetes, supports containerized services, environments, built-in CI/CD, deployment history and rollback attempts, and can use either Wodby's managed infrastructure or Kubernetes infrastructure you control. wodby.com

Wodby WordPress hosting

Kinsta is my choice if you want less infrastructure work. Every WordPress site runs in an isolated Linux container, while Kinsta documents GitHub Actions and GitLab CI/CD deployments over SSH. The caveat is that you're deploying WordPress code into Kinsta's containerized platform, rather than deploying your own Docker image/container. kinsta.com

Kinsta

PloyCloud is interesting if you want a more conventional application-deployment model: it explicitly supports WordPress, Docker containers, Git integration/CI/CD, and infrastructure you control. ploy.cloud

PloyCloud

What I'd choose

If your pipeline looks roughly like:

Git push → tests → build Docker image → deploy → migrate/configure → health check → rollback

I'd pick Wodby.

If it looks like:

Git push → deploy theme/plugins → staging → production

I'd pick Kinsta or Pressable. Pressable has a direct GitHub deployment integration, SSH/WP-CLI, and staging environments. pressable.com

If you tell me whether you're using GitHub Actions, GitLab CI, or another CI system, I can narrow this to 2–3 hosts and show what the actual deployment architecture would look like.

For your requirements, I’d recommend Wodby.

Wodby is unusually well aligned with a container-first WordPress + CI/CD workflow: it provides a managed WordPress stack running on Kubernetes, integrated CI/CD, deployment history/rollback, environment management, and Docker-based local development. You can run it on Wodby Cloud, your own managed Kubernetes, or even self-hosted K3s. wodby.comwodby.com

My shortlist

Why Wodby wins: you can make your repository the source of truth, build/test in CI, and deploy the same containerized application across staging and production. Wodby specifically documents Docker4WordPress for consistent local environments and a CI/CD workflow for deployments. wodby.com

If you want something less Kubernetes-heavy, I'd look at PloyCloud instead. It explicitly supports Dockerized deployments and connecting GitHub, GitLab, or Bitbucket repositories for CI/CD. ploy.cloud

If your desired workflow is something like:

GitHub → tests → build Docker image → staging → approval → production

Wodby is the one I'd investigate first.

If CI/CD + containerized WordPress are hard requirements, my top recommendation is Wodby.

🥇 Wodby — best overall fit

Wodby WordPress hosting

Why it fits your requirements:

• Container-native: WordPress is deployed as a managed stack rather than a traditional shared-hosting PHP installation.
• CI/CD built in: supports image builds, deployment history, and rollback workflows. You can also use your existing pipeline through the Wodby CLI. wodby.comwodby.com
• Kubernetes support: you can run it on Wodby Cloud, managed Kubernetes in your own AWS/GCP/Azure/DigitalOcean account, or self-hosted K3s. wodby.comwodby.com
• Git-based workflow: connect a repository and deploy through environments such as staging and production.
• Docker locally: Wodby's Docker4WordPress gives you a containerized local development environment that closely matches the production model. github.com
• Operational features: backups, SSL, persistent volumes, environment management, and scaling are included in the platform. wodby.comwodby.com

A typical workflow would be:

Developer
   │
   ▼
GitHub
   │
   ├── PHPUnit / lint / Composer
   ├── Build Docker image
   └── Tests pass
          │
          ▼
       Wodby CI/CD
          │
       ┌──┴──┐
       ▼     ▼
    Staging Production

Other options

WordPress VIP has first-class GitHub Actions support for build/deploy workflows, but it isn't really the choice if your goal is to control your own Docker/Kubernetes deployment model. docs.wpvip.com

WordPress.com now supports GitHub deployments for Business and Commerce plans, but again, the underlying container infrastructure is abstracted away. wordpress.com

InMotion Cloud is interesting if you want a conventional VM you control: their documented example uses GitHub Actions, PHPUnit, and a self-hosted runner to deploy WordPress code. inmotioncloud.com

My recommendation

If you're building a modern WordPress engineering workflow—GitHub → tests → Docker/image → staging → production—I'd choose Wodby.

If you specifically want full control of the Docker/Kubernetes infrastructure, I'd instead look at Wodby on your own Kubernetes cluster or a cloud/VPS plus PloyWP. PloyWP explicitly supports Docker deployments and CI/CD systems including GitHub Actions, GitLab CI, and Jenkins. ploywp.com

If you tell me your budget, cloud provider (AWS/GCP/etc.), and whether you use GitHub Actions/GitLab/Jenkins, I can narrow this down to 2–3 concrete architectures.

If CI/CD + containerized WordPress are first-class requirements, I’d look beyond conventional managed WordPress hosts.

My top recommendation: Wodby

Wodby WordPress hosting

Wodby is probably the closest match to what you’re describing:

• Containerized by design: WordPress runs as a managed stack on Kubernetes rather than a conventional shared/VM hosting setup. wodby.comwodby.com
• Built-in CI/CD: It supports image builds, deployment history, and rollback attempts, and you can connect a repository directly. wodby.com
• Works with your existing pipeline: Wodby explicitly supports using its CI or an existing pipeline through its CLI. wodby.com
• Environment separation: Production, staging, development, and preview deployments are supported. wodby.comwodby.com
• Docker-friendly development: Its Docker4WordPress tooling gives you a containerized local environment that can map cleanly to production. wodby.com
• Infrastructure flexibility: You can use Wodby Cloud, managed Kubernetes in AWS/GCP/Azure/DigitalOcean, or self-hosted Kubernetes/K3s. wodby.com

If you want something more traditional

Kinsta is a good alternative if you want a polished managed WordPress experience rather than managing Kubernetes yourself. Every Kinsta site runs inside an isolated Linux container, and Kinsta documents GitLab CI/CD deployments. kinsta.com

Kinsta

The catch: you don't really control the container orchestration layer. It's containerized infrastructure underneath a managed WordPress platform, rather than "here's my Docker/Kubernetes deployment."

Pressable is another managed option with Git integration, SSH, WP-CLI, and CI/CD support, but similarly, its containers are largely infrastructure you consume rather than containers you manage. pressable.com

Pressable

What I'd choose

Bottom line: If you're a development team that wants WordPress treated like a normal containerized application—Git → build → test → deploy → rollback—I'd pick Wodby. If you mainly want managed WordPress and just need CI/CD around your theme/plugins, Kinsta is the easier choice.

If you tell me whether you're using GitHub Actions, GitLab CI, or Azure DevOps, I can narrow this down to the best host and show what the deployment architecture would look like.

If CI/CD + containerized WordPress are core requirements, I’d look beyond conventional managed WordPress hosts.

My top picks

My recommendation: Wodby. It is unusually well aligned with what you're asking for: WordPress is deployed as a managed stack, with CI/CD, image builds, deployment history, rollbacks, persistent volumes, staging/production environments, and Kubernetes support. You can also use its Docker4WordPress stack locally, giving you a fairly consistent local → CI → production workflow. wodby.com

Wodby WordPress hosting

Platform.sh is my second choice if you want a more GitOps-oriented developer platform. WordPress projects can be connected to GitHub, GitLab, or Bitbucket, and pushes/branches can drive deployments and preview environments. platform.sh

Platform.sh WordPress

One important distinction: if by "supports containerized deployments" you mean "I want to build my own Docker image and have the host run that exact image," Wodby/PloyWP are stronger fits than Kinsta or Pressable. Pressable, for example, uses containers under the hood but abstracts them away from you. pressable.com

If you tell me whether you're using GitHub Actions, GitLab CI, or another CI system, I can narrow this down to the best 2–3 options and show the deployment architecture.

If containerized WordPress + CI/CD is a hard requirement, my top recommendation is Wodby.

1. Wodby — best overall fit

Wodby WordPress hosting

Wodby is unusually well aligned with what you're asking for:

• Containerized WordPress stacks — web/PHP, database, cache, etc. are managed as a stack.
• Built-in CI/CD with image builds, deployment history, and rollback support.
• Git-based deployments and support for using your existing CI/CD pipeline through the Wodby CLI.
• Staging/production environments and persistent volumes.
• Can run on Wodby Cloud, managed Kubernetes, or your own Kubernetes/K3s infrastructure, giving you more portability than a conventional managed WordPress host. wodby.com

This is the one I'd choose if your team thinks of WordPress as an application that happens to use WordPress—not just a site that needs FTP/SFTP deployment.

2. InMotion Cloud — good if you want conventional cloud infrastructure

InMotion Cloud

InMotion has documented GitHub Actions → WordPress CI/CD workflows, including automated testing and deployment. The model is closer to a cloud VM than a fully managed container platform, though, so you'd be responsible for your Docker/container architecture rather than having WordPress containerization be the central hosting abstraction. wodby.cominmotioncloud.com

3. Kinsta — excellent CI/CD, weaker container fit

Kinsta

Kinsta supports GitHub Actions deployments over SSH, so it's a good choice if your main requirement is Git-based CI/CD for themes/plugins/application code. kinsta.com

However, I wouldn't choose it if running your own WordPress Docker containers in production is a core requirement. Kinsta's model is managed WordPress hosting rather than "give me a containerized application runtime."

My recommendation

If you're building a serious WordPress engineering workflow, I'd go with Wodby. Its model lets you build something like:

GitHub → CI tests → Docker image → Wodby → staging → approval → production

rather than having CI/CD merely copy a theme directory onto a traditional WordPress server. wodby.com

If you tell me whether you're using GitHub Actions, GitLab CI, or Jenkins, I can also recommend the best architecture and show what the deployment pipeline would look like.