dotCMS Cloud Based Content Management System

dotCMS Cloud is an on demand cloud CMS and SaaS platform

dotCMS Cloud

All the Power, None of the IT.

The speed and agility you need.

The ease of deployment you want.

dotCMS Cloud provides all the capibilities of dotCMS without needing your IT department. Secure, scaleable and fully-customizable, dotCMS Cloud is capable of deploying websites, intranets, extranets, portals, apps or any type of Headless Content strategy -- with unprecedented speed and agility.

Every dotCMS Cloud installation comes with the award-winning dotCMS Enterprise Professional Edition feature set that has been performance tuned by the experts.

Rapid Development

Go from weeks and months of set up to days with dotCMS Cloud’s on-demand access and scalability.

Decrease Your TCO

dotCMS Cloud removes the spending on equipment and maintenance and overall IT spend.

Enterprise-level scalability

dotCMS Cloud gives you the extensibility and flexibility to grow as your website grows.

Easy to use

Your business team can start authoring, editing, and publishing pages, content and other assets easily.

Reduce Dependency on I.T.

With AWS secure and private infrastructure, along with dotCMS’s push-publishing and auto-scaling capabilities, IT can focus on business innovation, rather than server administration.

Real Time Execution

Fast, powerful and simple, dotCMS Cloud gives business teams the control and delivery they need to meet market demands in real time.

Moving to the Cloud

See how a B2B Email Marketing Platform moved to dotCMS Cloud to secure their site and offload many of their resource-strapped tasks, like backups, version upgrades and server maintenance.

Learn more

dotCMS Cloud Resources

Cloud Setup Examples

dotCMS Cloud offers high availability, load balancing between production nodes, UAT/Testing environment mirrors, dedicated authoring environment, and the option of a disaster recovery node that is completely separated by network and geography. Below are a few examples of typical dotCMS Cloud setups. To learn more please contact us we would be happy to work with you to design a custom solution that is right for your organization.

Amazon Technology Partner

dotCMS Enterprise Cloud FAQ

  • Q:  How many sites can I run on a dotcms_abbr Cloud server?
  • A: You can run an unlimited number of sites dotcms_abbr has multi-tenant/virtual hosting capabilities baked in.  In dotcms_abbr. you can create new hosts or copy existing host, point your DNS at them that's it. Content contributors access can be limited to a single host within the system.  Your only limit is the server instance and implementation capacity.
  • Q:  How many content authors can I have?
  • A: Unlimited - again, really.  From the dotcms_abbr admin, you can set up as many Developers,  Content contributors and Content managers as you need.  The only limit to the number of users is the server's capacity, which varies as the server size grows and from implementation to implementation.
  • Q:  What is included in “Developer Support”?
  • A:  Developer support is intended for organizations, companies and agencies who are comfortable building custom websites and are looking for a service to host their dotcms_abbr installation. Developer support includes server monitoring, server "uptime care" and cloud backups. Customers who choose Developer support are responsible for building their own websites, content and web applications and leveraging the same community resources that are available to the public at large, including the monitored forum, the dotcms_abbr documentation site and other public channels of support.  Customers who choose Developer Support can also choose purchase online or onsite training courses to accelerate new developments in dotcms_abbr this is included in “Cloud Support”?
  • Q:  What is included in “Cloud Support”?
  • A:  Cloud Support gives you access via the phone and our support portal to dotcms_abbr team of support engineers, who can help you with issues, roadblocks or questions you might have with the dotcms_abbr system.  It also insures that your dotcms_abbr installation is up to date with updates, upgrades and the latest dotcms_abbr code (scheduled to meet your uptime requirements). 
  • Q: What does “Uptime Care” mean?
  • A: Uptime Care means that dotcms_abbr is responsible - on a for keeping your dotcms_abbr server running and serving 24/7/365.  If there is an issue with the dotcms_abbr or the server environment that is preventing dotcms_abbr from delivering content, dotcms_abbr support staff will work to resolve the issue or to provide the customer with a recommended resolution. Uptime care does not extend to support of outages due to capacity (we will provide you with a recommendation), custom plugins or custom implementations, all of which can cause outages on a Cloud server.   
  • Q:  Do we get access to the whole dotcms_abbr codebase?
  • A: dotcms_abbr Cloud customers looking to develop custom plugins or functionality can access the dotcms_abbr public source code at DotCMS Cloud customers do not have access to the dotcms_abbr EE source code, which is only available to dotcms_abbr licensees.
  • Q:  How long does it take to setup my server?
  • A:  Generally speaking, once your subscription payment has been made, dotcms_abbr will have your server up in less than a day.
  • Q:  How secure is my cloud server? I would like to use it to store XYZ sensitive information.
  • A: dotcms_abbr cloud servers are built using security best practices for running infrastructure on Amazon Web Services. This includes a dedicated private network for each client, limiting administrative access as appropriate, running all services with "least privilege" access, and encrypting data at rest and in transit (additional SSL configuration may be necessary for the latter).This said, dotcms_abbr cloud has not been audited for PCI compliance and you should not use dotcms_abbr to store any sensitive information like credit cards. We recommend using a 3rd party payment gateway or system for storing this type of information.
  • Q:  How do I point my domain name to my dotcms_abbr instance?
  • A:  You will need to change your domain's DNS record to point to your server's ip.  The process for doing varies per Domain registrar.  We recommend using a cname record to point to the host name we have provided to you.
  • Q:  Can I access the REST apis and/or deploy and use plugins?
  • A:  Yes, the REST apis are available for use by external systems. Additionally, you can deploy OSGi based plugins in your cloud instance to extend and build apps on top the dotcms_abbr.   Be aware that dotcms_abbr staff reserves the right to remove these plugins if we find or suspect that one or more of them are causing service outages. 
  • Q:  How many IP addresses do I get?
  • A:  Every dotcms_abbr Cloud server gets one public IP address.
  • Q:  How about SSL - can I install my own cert?
  • A:  dotcms_abbr can provide you with a csr that you can have signed and we will install it on your server(s).  Email or enter a support ticket to get the process started.
  • Q:  If I don’t get support, can I add it later?
  • A:  You can, but it will require you to purchase a "Basic" support agreement from dotcms_abbr which is an annual support contract.
  • Q:  Can I pay by Invoice?
  • A:  If you need to pay by invoice, you will need at least a one year contract.  Contact us for more information.
  • Q: How can I connect to my instance?
  • A:  dotcms_abbr' browser based admin interface has all the tools included that are required to manage your web sites.  You can connect to your instance via http and https.  We do not offer any shell, ftp or ssh access.
  • Q:  Can I install other web software on my instance?
  • A:  No, your instance is dedicated to dotcms_abbr only.  You can always spin up new Amazon instances and use them in conjunction with your dotcms_abbr cloud server.
  • Q: Can I use other Amazon cloud services (CDN, Route 53) with my dotcms_abbr managed instance?
  • A: Sure.  If you have other cloud services you can include a dotcms_abbr cloud instance as completely managed dotcms_abbr instance in your infrastructure - though you will still only have access to the dotcms_abbr admin interface and APIs.  
  • Q: If I need to move to bigger instance or add storage, can I do that and how much does it cost?
  • A: Moving to a difference instance size is easy.  All you need to do is open a support ticket or send an email to and our support engineers will schedule the upgrade in.  You will receive payment instructions in your email (a new cloud subscription will be started at the new price and your old subscription will be cancelled. The actual instance upgrade process takes about an hour (though often less) but does require a server restart.

dEC Migration Process

Migrating to the dotCMS Enterprise Cloud (dEC) requires the execution of the steps described below. 

Depending on the dotCMS version you are currently using and whether or not you have any custom plugins, the effort  may vary. Each one of these steps usually take a one-week iteration to be completed, but some of them may take longer and others may be skipped.

From Database Conversion to Database Upgrade, the heavy lifting is executed by dotCMS. Based on the resources available on your team, Plugin Upgrade may be a shared load between your developers and dotCMS'. Testing and Tweaking relies almost 100% on the knowledge that only you and your team have about your own custom implementation. Las but not least, Going Live is the final step of an already rehearsed and tested process that will conclude in dotCMS experts managing your dotCMS infrastructure.

1. Database Conversion

Postgres is the standard database in our dEC environments, so the first step in the migration process is to convert the data from your custom implementation (MySQL, Oracle, or MS SQL Server) to Postgres.

These are the general steps involved in this iteration:

  1. Customer provides a first snapshot of database and assets.
  2. dotCMS creates a series of scripts to export the data and import it into Postgres.
  3. dotCMS executes initial testing.

2. Legacy page and file migration

Depending on the original version, migrating legacy files and pages to content may be necessary. 

If you are running dotCMS 3.7.x or earlier, you can use the following queries to determine the amount of legacy pages and files existing in your database:

select count(*) from htmlpage;
select count(*) from file_asset;

If both queries return no results, this step can be skipped.

These are the general steps involved in this iteration:

  1. Execute page to content migration tool and resolve any conflicts reported by the process.
  2. Deploy the 3.7.x compatible version of the file to content migration plugin and resolve any conflicts reported by the process.
  3. dotCMS executes initial testing.

3. Database Upgrade

Once the data is stored in a Postgres database and all legacy elements have been migrated to content, the next step is to execute the upgrade to the latest dotCMS version.

These are the general steps involved in this iteration:

  1. dotCMS runs upgrade tasks and resolves any conflicts reported by the process.
  2. dotCMS cleans up data inconsistencies.
  3. dotCMS executes initial testing.

4. Plugin Upgrade

In order to migrate full functionality, every custom plugin needs to be adapted to the new dotCMS version.

There are only a few static plugins that we are able to manage on a dEC environment:

  • SAML Authentication
  • WYSIWYG Editor Customizer
  • Content Import and Export

Any other static plugin will need to be converted into a dynamic (OSGI) plugin.

These are the general steps involved in this iteration:

  1. Customer provides code for all static and dynamic plugins.
  2. dotCMS adapts configuration for dEC static plugins.
  3. dotCMS and/or customer upgrade custom plugins.

5. Testing and Tweaking

Once database and plugins are upgraded, dotCMS provides the customer with access to their new dEC environment(s). Both front-end and back-end functionality must be tested by the customer.

Any issues related to back-end functionality will be addressed by the dotCMS team working on the migration.

Any custom front-end implementation requiring to be adapted to the new dotCMS version will have to be taken care by the customer; dotCMS experts will assist during troubleshooting and solution identification, but the customer is responsible for the implementation of any custom code modification.

These are the general steps involved in this iteration:

  1. Customer provides SSL certificates.
  2. dotCMS sets up dEC environment(s).
  3. dotCMS provides access to new environments running the latest dotCMS version with the customer's data and static plugins.
  4. Customer tests both front-end and back-end functionality.
  5. dotCMS assists on troubleshooting.
  6. Customer tweaks custom code.

6. Go-Live!

Once testing is done, we are ready to go live with your new dEC environment(s).

These are the general steps involved in this iteration:

  1. Customer starts a content freeze.
  2. Customer provides a second snapshot of database and assets.
  3. dotCMS executes database conversion, upgrade, and inconsistency clean-up/legacy page and file migration.
  4. dotCMS refreshes environments with latest set of database and assets.
  5. Customer executes a quick round of testing.
  6. Customer switches DNS to dEC instances.
  7. Customer ends the content freeze.
  8. The dotCMS team working on the Migration Project hands off the environment to the dotCMS Support Team.