On-Premise installations using Docker

Stand alone for simple setup eg development
Example of Cloud CMS in a simple cluster
Example of Cloud CMS in a more complex cluster

At Cloud CMS, we are seeing more customers transition to running Cloud CMS as a microservice. Docker puts the power of the cloud into the hands of the customer. The implication of this to traditional SaaS companies is very interesting. While SaaS companies will continue for some time to provide real value in terms of hosting their offerings and handling all of the Dev/Ops tasks associated with running the underlying infrastructure (along with data migrations, upgrades and support), we expect to see customers pull more of this on-premise and handle their own infrastructure management tasks themselves. Docker and other container technology companies make this easier and lower cost than ever before. This shift in customer preference may shift many traditional SaaS companies into offering a more conventional on-premise support model. We’ve certainly found this to be the case at Cloud CMS.

Why On-Premise?

Plug in one of our pre-built client libraries to connect your new or existing apps to the cloud.

  1. Support
  2. regional
  3. legal
  4. microservice
  5. security procedures
  6. performanace / storage

Why Docker?

Docker has provided Cloud CMS with a way to package up our tiers into services that could 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 to can Cloud CMS on-premise, in their own data centers, and even on their own laptops.

Docker allowed us to express our tiers as services that could be launched into containers. Docker then allocates these containers (Docker Swarm) onto a single host or many different hosts (EC2 instances) on the fly.

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 and largely automated.


  1. Standalone
    1. Cloud CMS containers are instantiated once
    2. All containers, including MongoDB and Elastic Search can be run within a single Docker Machine (EC2 instance)
  2. Cluster
    1. Cloud CMS containers are instantiated multiple times and organized into clusters
    2. Containers may be spread across many different Docker Machines (Ec2 instances)
    3. Load-Balanced so that if one server in the cluster fails, requests will failover to other containers in the cluster

Get Started with Cloud CMS

It's Free to Sign Up. No Credit Card Required.