Cloud CMS Blog

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

Comparison: Cloud CMS vs Contentful

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.

Simple user interface for defining content types and instances.

Update Strategy

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

Documents are published one-by-one.

Workflow Process

Flexible workflow capability.

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

No online workflow capability.

API Access

Fully bidirectional, “API first” design

Fully bidirectional, “API first” design

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.

Uses CDN for all static assets, requiring them to be publicly available.

Pricing Factors

Based solely on your stages and SLA required

Pre-defined tiers with a fixed number of

  • Editors
  • Content entries
  • API calls / CDN hits

New reporting options

We’ve added some expanded reports lately: for both Workflow, as well as Logging.


Since it’s introduction, workflow remains a key component of our platform.  The process to define and execute various business processes in Cloud CMS is well documented.  Now, you can track and analyze each step involved to streamline operations even further:


Review any historical sequence of events, or those currently in-flight, to find patterns / trends / bottlenecks needing attention.  Especially where system log details are involved:


Also, if you need to build any custom reports - these are now called “Data Views”

They’re functionally equivalent to the reporting outlined in this video… to see any of the above in action, login to your tenant, or signup for a Trial!