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