"The only difference between Cloud CMS and your current on-premise document repository is that you don't have to worry about software or hardware installation and upgrades any longer."
Jeff Potts
Jeff Potts, Founder
Metaversant Group

Frequently Asked Questions

Do you offer private cloud or dedicated hosting?

Yes. We give you the option to have your own cluster of Cloud CMS servers running in your own Amazon virtual private cloud. This cluster is 100% dedicated to your own applications and business needs.

For information on pricing, please contact us and tell us about your project.

Can Cloud CMS help develop my app?

Yes. Cloud CMS provides implementation services to help build your iOS, Android or HTML5 application and connect it to Cloud CMS for dynamic content delivery. As experts in both the front-end and back-end technologies, we provide quality work and deliver on schedule.

For a quote, please contact us and tell us about your project.

Does Cloud CMS work with iOS, Android, Node.js, PhoneGap, JavaScript, HTML5 and any other popular frameworks?

Yes. You work with Cloud CMS just like you would any other ReSTful HTTP/OAuth2 service. In addition, we have a library of drivers and developer guides that you can look to for guidance on building apps for the web as well as iPhone, iPad, Android, PhoneGap, Titanium and many other frameworks.

What is the difference between an Application and a Project?

A Project is a logical separation for work within Cloud CMS. It could be a site, a sub-site, a department, a web project or anything else you'd like. Projects let you organize teams, invite members and provide a place for you to collaborate on content.

An Application is something that you create to provision resources and services dedicated to your web site or web/mobile application. Each Application provides storage and services that your app can access for things like user registration, password recovery and user settings retrieval.

One way to think of it is that Projects are business-side places where content is worked on and approved. Applications are delivery-side places focused on end users and presentation. Applications can draw content from a single Project or from multiple Projects.

Applications also give you a place to provide additional details such as GitHub source URLs so that Cloud CMS can automatically handle the deployment and hosting of your apps.

How does the deploy / publish functions work?

Cloud CMS stores everything in JSON format . The content is consumed through Content APIs which are ReSTful HTTP methods behind OAuth2. By this point, this is an industry standard, making it very easy for your apps to source content from Cloud CMS.

The Cloud CMS workflow engine lets you control the lifecycle state of content. Content is moved from creation to approval and finally to publication. Published content is live and available for consumption via the API.

Does Cloud CMS build my web site or mobile app for me?

No. Cloud CMS manages the backend lifecycle of your content and makes it available to your own applications via its REST API. You have to create your own applications (iOS, Android or web-based applications).

Using our Partner network, Cloud CMS provides implementation services if you're looking for assistance with developing your front end applications, middleware or any custom data APIs.

Cloud CMS also provides hosting for HTML5 applications and custom APIs within it's Node.js based application server tier. If you build an HTML5 web application, you can deploy it to our cluster directly from GitHub. It will be online and hosted instantly.

Is Cloud CMS only intended for smaller business applications?

Not at all. Cloud CMS is scalable, high-powered cloud application with an elastic architecture. It was designed with robust enterprise features in mind, but was put together in a such a way as to practical and affordable to businesses of all sizes.

Our private cloud / on-premise option is ideal for larger companies or enterprise clients.

We also offer full multi-tenancy for system integrators, consultancies and larger clients who wish to utilize Cloud CMS in a white-label capacity for their own customers, departments, projects and engagements.

How is validation handled on custom forms?

Cloud CMS provides both server-side and client-side validation for forms.

Validation logic is defined primarily using JSON Schema and content modeling within Cloud CMS. Inheritance, property definitions and server-side scripting all play a part in determining the validation of content before it is written to the underlying database.

Client-side validation is provided via our open-source Web Forms engine known as Alpaca (http://www.alpacajs.org).

Alpaca is an open-source project hosted on GitHub that anyone can use within their web projects. Using Alpaca, you can host Cloud CMS-driven forms right inside of your own web applications and web sites, no matter whether you're running WordPress, Drupal, Joomla or any other technology.

Client-side validation includes field-level indications to end users as to invalid values and leverages an extensive control library of 30+ fields. Alpaca is very flexible and can be customized extensively to add custom behaviors, rules, event handling and more.