CloudPloy
WordPress CI/CD Hosting

Automated WordPress Deployments From Every Git Push

Push your WordPress code to GitHub, GitLab or Bitbucket and CloudPloy deploys it to your own cloud server. Run your tests in your existing CI, roll back when you need to, and trigger deploys from the REST API.

Start Deploying WordPress

CI/CD for WordPress With CloudPloy

CloudPloy handles deployment; your CI service handles tests

🔄

Continuous Deployment

CloudPloy handles the deploy step: every push to your WordPress repository's branch goes live.

  • Git webhook for automatic deployments
  • Manual deploy and redeploy from the dashboard
  • Rollback to a previous deployment
  • Deployment history and logs
🧪

Bring Your Own CI

CloudPloy does not run your tests. Run them in GitHub Actions, GitLab CI or Bitbucket Pipelines first.

  • Protect the deploy branch so only passing changes reach it
  • Or turn off auto-deploy and call the CloudPloy API from CI
  • PHPUnit, PHPCS and other checks run in your CI service
🌐

Staging and Production

Use two CloudPloy apps from the same repository to test changes before they reach production.

  • One app per branch, for example develop and main
  • Separate environment variables for each app
  • Database and uploads are not copied between apps; sync them yourself
📊

Deployment Visibility

See what each deploy did and whether it worked.

  • Deployment status and logs in the dashboard
  • Deployment list and details through the REST API
  • Operational emails to your team
🔒

Configuration and Access

Keep secrets out of Git and control who can deploy.

  • Environment variables per app
  • Team members and roles
  • API tokens with scoped permissions
⚡

Hosting Basics

The rest of what a WordPress site needs to run on your own server.

  • Optional MySQL on the app's server
  • Custom domains with Let's Encrypt SSL
  • Health check after each deploy
  • Replicas from 1 to 10 on paid plans; auto-scaling and load balancing coming soon

Git Integration

Connect with your existing Git workflow and development tools

🐙

GitHub

  • • Connect with the CloudPloy GitHub app
  • • Webhook auto-deploy
  • • Works alongside GitHub Actions

Connect GitHub from the CloudPloy dashboard

🦊

GitLab

  • • OAuth connection
  • • Webhook auto-deploy
  • • Works alongside GitLab CI/CD

Connect GitLab from the CloudPloy dashboard

🪣

Bitbucket

  • • OAuth connection
  • • Webhook auto-deploy
  • • Works alongside Bitbucket Pipelines

Connect Bitbucket from the CloudPloy dashboard

Flexible Deployment Workflows

Choose the CI/CD workflow that matches your WordPress development needs

Auto-Deploy on Push

The simplest workflow for theme and plugin changes.

Every push
Simple
1

Push to the deploy branch

2

The webhook notifies CloudPloy

3

CloudPloy builds the new commit

4

The new container starts and is health-checked

5

Roll back if the change broke something

CI-Gated Deploys

Run your own checks first, then deploy from CI.

Every merge
Moderate
1

Open a pull request

2

Your CI runs tests and code standards

3

Merge when checks pass

4

CI calls POST /api/v1/apps/{app}/deploy

5

CI reads GET /api/v1/apps/{app}/deployments

Staging Then Production

Two CloudPloy apps on two branches of the same repository.

Two apps
Moderate
1

Merge to develop

2

The staging app auto-deploys

3

Review the staging site

4

Merge develop into main

5

The production app auto-deploys

Why Automate WordPress Deployments?

What changes when deployments come from Git

Fewer Manual Steps

  • No FTP uploads or SSH sessions to deploy
  • The same deploy process every time
  • A record of every deployment

Safer Changes

  • Tests run in your CI before code reaches the deploy branch
  • Review changes on a staging app first
  • Roll back to a previous deployment

Team Collaboration

  • Git-based review with pull requests
  • Team roles control who can deploy
  • Deployment logs everyone can check

Example CI/CD Setups

How different WordPress projects can use CloudPloy deployments

WordPress Agency Development

Scenario:

Several client sites with custom themes and plugins, each in its own repository.

CI/CD Solution:

One CloudPloy app per client site, each auto-deploying from its repository, with a staging app where the client needs review.

Benefits:

Same deploy flow for every client
Rollbacks per site
Separate env vars per site
Custom domains with SSL

WordPress Product Company

Scenario:

A product built on WordPress with frequent releases.

CI/CD Solution:

CI runs the test suite on every pull request, and CI calls the CloudPloy API to deploy after merge.

Benefits:

Deploys only after tests pass
API-driven releases
Deployment logs
Quick rollback

In-House Marketing Site

Scenario:

A company site where several people change the theme.

CI/CD Solution:

Pull requests with required reviews, a staging app on develop, and auto-deploy to production from main.

Benefits:

Reviewed changes
Staging preview
Team roles
Rollback

WooCommerce Store

Scenario:

An online store where a broken deploy costs sales.

CI/CD Solution:

Test theme and plugin changes on a staging app, deploy to production from main, and roll back if checkout breaks.

Benefits:

Staging first
Health check after deploy
Rapid rollback
Replicas on paid plans
CI/CD with CloudPloy

Ready to Automate Your WordPress Deployments?

Connect your repository and deploy on every push. Server compute is billed separately by your cloud provider.

View Plans
Auto-deploy on push
Rollback to a previous deployment
REST API for CI