DevOps

DevOps is the behind-the-scenes work that keeps a website running: how environments are set up, how changes are released, and how problems are spotted. When it's done well, you don't notice it. When it isn't, you notice at the worst moment.

We build and maintain the tools and processes that let developers release changes with confidence, so their time goes into your site rather than into fixing deployments.

Ready for the day traffic spikes

Government sites can see sudden surges from a health alert, a policy announcement, or an emergency update. Poor operational practice can be the difference between a site that stays up and one that fails when people need it most.

Our co-founder is a DevOps specialist, so it's a priority across the company. We've refined our processes and tools so developers are productive from day one and confident in every release.

What you get:

  • A site built to stay up. Monitoring that alerts us to possible problems, ideally before they happen.
  • Safer releases. Automated tests and deployments run the same way every time.
  • Consistency across hosts. The same approach on GovCMS, Acquia, and Pantheon.

Our approach to DevOps

Terminal window icon

Define environments in code

We use Docker to define environments, often with development tools such as Lando or Ahoy, so every developer works in the same setup. We have a saying: if a developer can't get up and running in 30 minutes, that's a bug.

Server icon

Work with your hosting platform

We work with GovCMS, Acquia, and Pantheon. We develop a similar recipe for each, so productivity doesn't depend on the environment.

Continuous Integration arrows icon

Automate testing and deployment

GitHub Actions runs our tests and deployments, with frameworks such as Cypress and BackstopJS checking the code. See our continuous integration service.

Eye icon

Watch and respond

We care about the reliability of the sites we maintain. Our monitoring alerts us to possible problems, ideally before they happen. See our monitoring service.

Frequently asked questions

It covers the infrastructure, deployment, monitoring, and operational practices that keep a Drupal site running in production: environment management, automated deployments, backup and recovery, uptime monitoring, and incident response. That's separate from the development work of building features.

Government sites can face unpredictable traffic spikes, such as a health alert or a natural disaster update. Poor DevOps practice can be the difference between a site staying up and going down at the moment people need it. Ask any prospective partner for concrete evidence of how they handle production incidents, not only a list of features.

GovCMS SaaS handles much of the infrastructure work for you, because it's a shared managed platform. GovCMS PaaS and other Drupal hosting put more of that responsibility on your agency or your delivery partner, which is an important factor when you choose between SaaS and PaaS.

We work with GovCMS, Acquia, and Pantheon.

Latest insights

Visual regressions testing - Backstop JS
Article

At DrupalSouth Community Day 2025, Marji Cermak shared a practical and grounded walkthrough of how visual regression testing, powered by BackstopJS, can prevent regressions long before they appear in production.
Beer poured from clean pipelines
Article

The Morpht CI pipeline caught a recent vulnerability in Drupal core which led to the problem promptly being fixed.