Cloud Connected

Finding sanity by losing your head

There was a lot of chatter last year regarding a “headless” or “decoupled” CMS design.  Zeitgeist, maybe… countermovement, definitely.

Since their inception, every expansion of content management software along the continuum from managing basic websites to full-on digital experiences drove CMSes further and further into the application’s presentation tier.

In parallel, we witnessed the maturity of frameworks such as Angular, Ember, and Ionic (just to name a few) - all pushing development out to the browser tier itself, and each one clashing with the template-driven approach ordained by any underlying CMS.

As a result, it’s become fashionable to lose one’s head.

Monolithic CMS vendors are now re-engineering their approach.  Varying levels of RESTful calls are surfacing to placate the JavaScript hungry masses.  Naturally, this journey carries risks - enough that companies keen to succeed are exploring alternatives.

And finding that an API-first solution makes for a more natural fit.

By definition, API-first is headless.  Nothing needs to be “decoupled”, but rather a pure CMS service is made available that blends naturally with your selected framework, whether for a:

  • Static site
  • JS Application
  • Single-page app
  • Mobile app

or a combination of the above.  Need proof, easy.  Just review our SDK packages, or better yet - sign up for a Free Trial.

Comparison: Cloud CMS vs Prismic

Not sure which CMS is a better fit? Review these points to help guide your selection.


Cloud CMS


Ease of Use

Implements a role-based UI to accommodate various functions.

Complex user interface for defining content types and instances.
Item creation must occur here.
See API Access.

Update Strategy

Documents are published individually, or as part of larger change sets.

Documents are published individually, or as part of larger change sets.

Workflow Process

Flexible workflow capability.

Allows teams and roles to be created along with a workflow designer for defining content production process and constraints.

Limited workflow, provides a writer and publisher role but incomplete support for content production process.

API Access

Fully bidirectional, “API first” design

Read-only, “API first” design.
NO WRITE capability.

Deployment Options

SaaS and / or On-Premise

(Docker images)

SaaS only

Security for Assets

Allows assets to be delivered via either CDN or Web API – with full security available.

Allows assets to be delivered via either CDN or Web API.

Pricing Factors

Based solely on your desired SLA

Pre-defined tiers with a fixed number of

  • Users
  • Features (roles, workflow)
  • API uptime

Comparison: Cloud CMS vs DIY

Not sure whether to build or buy? Review these points to help guide your selection.

Why DIY:

  • exact fit with your technology stack
  • use existing in-house skills and resources
    • build only the features you need
    • able to add new features as required
    • use existing developers for support
  • cost / budget - internal
    • no need for external services to deliver and support product
  • can be a ‘skunk works’ project

Why not DIY:

  • Risk (more complex than it looks)
    • time/effort/cost are all easy to under-estimate
    • CMS requirements can be extensive
      • what happens if it can’t be built in a timely manner?
      • distraction from core business
  • must maintain skills and in-house knowledge
    • to support, upgrade, and enhance
  • may have technical skills but unlikely to have CMS product experience

Why Cloud CMS:

  • Minimizes risk
    • exists today with the features you need
    • already built (many years of blood, sweat, and tears)
    • if you require a new feature talk to us…
    • discovered and conquered many development hurdles
  • fits with your stack
    • scalable and elastic
    • allows you to concentrate on your business now and in the future
  • lower financial risks with a SaaS model
    • Proven TTV
  • This is our business: we are the experts