Cloud CMS ships its on-premise offering using Docker. Docker provides a way to package up the architectural tiers of Cloud CMS into services that can easily be deployed in all kinds of interesting configurations. It greatly reduced the heavy Dev/Ops and IT cycle involved with running a cloud infrastructure service.

With Docker, our customers can easily and efficiently run Cloud CMS on-premise, in their own data centers and even on their own laptops.

Cloud CMS services running in Docker are launched as containers. Customers allocate these containers to host machines. They can do this manually or they can use a best-of-breed orchestration approaching using something like Kubernetes, Amazon CloudFormation Templates, Elastic Container Service or Docker Swarm.

Furthermore, the elastic architecture of Cloud CMS means that new containers can come online at any time and join the pack. Others can come offline at any time. It's self-healing, elastic and automated.

To learn more, see Configuring Docker.