Amsterdam-based Hippo today released the latest version of its web content management platform — an update a company official called a "completely re-architected platform with all benefits of the cloud."
The open-source provider released Hippo onDemand, which is designed to transform digital business ecosystems into flexible and responsive digital experiences while leveraging all the benefits of the cloud.
At the same time, users of the platform will have access to the full Hippo enterprise stack with capabilities like cross channel and personalization in a Platform-as-as-Service (PaaS) platform, according to Sonja Kotrotsos, Hippo director of product marketing.
"Our customers are very busy with the topic of digital transformation and all of its changes to their businesses," Kotrotsos said in an interview with CMSWire. "Speed and agility is really what they need now, and that’s the essence of Hippo onDemand."
What's troubling enterprises with cloud CMS platforms? Hippo officials said enterprises that deploy cloud-based platforms often encounter time-intensive custom builds or complex workarounds for inflexible platforms. Hippo onDemand is a ready-to-use cloud platform that provides build freedom and flexibility via an open REST API-driven microservices architecture. It supports interoperability with third-party data and business solutions, and scales to support cross-channel growth, according to company officials.
Digital Experience Competition
“Hippo onDemand is the warp drive of digital experience innovation,” Hippo CTO Arjé Cahn said in a statement. “Industry leaders need to be able to take advantage of the latest technologies to create an experience that is unique to their brand and relevant to each individual customer. In a market shifting toward cloud solutions, a modern, agile, approach to digital experiences is what digital teams require."
Cahn said one-size-fits-all cloud offerings do not allow them to build differentiating experiences, and custom-hosted solutions limit the speed at which new digital initiatives can be introduced.
"We see some of our customers successfully rolling out new functionality dozens of times per day," Cahn added. "With the Hippo onDemand platform, they are in full control.”
Hippo onDemand is built on Amazon AWS and Docker technology. It allows enterprises to monitor the systems development life cycle (SDLC) pipeline, run multiple environments simultaneously, migrate from on-premise to cloud and take advantage of REST APIs. The open architecture of Hippo onDemand provides interoperability with third-party data and solutions.
Hippo also in this release updated multilingual experience delivery capabilities by localization of the user interface and improved time zone support for global collaboration.
"We now have a cloud-first strategy," Kotrotsos said. "We're ensuring that we remove all operational bottlenecks so customers can deliver with a competitive edge in their respective industries."
She added that offering Hippo CMS through Platform-as-a-Service helps ensure strength in interoperability and connectivity.
Hippo Partners Up
Hippo last week announced a partnership with Intershop to create personalized online shopping experiences. Intershop, headquartered in Jena, Germany, is a leading independent provider of enterprise solutions for omnichannel commerce. It serves more than 300 companies around the world with its solutions for modeling sales processes. Partnering with Hippo means that Intershop clients have direct access to Hippo’s content targeting and personalization capabilities.
Hippo also signed a partnership with Contentserv, an enterprise marketing management solution, to offer clients a more customized user experience and product information management capability.
Hippo in February announced it was combining traditional digital experience management with Content-as-a-Service in version 10.2 of its CMS platform. It includes a new automated Content REST API, which WordPress also included in its last iteration.
REST, or more formally, Representational State Transfer, is an architectural style that has a number of attributes, starting with what it can replace. It is an alternative to XML-RPC and to admin-ajax. Hippo already had a REST API, but it was not an automated read-only content API that came ready to use.
Company officials said it obviates the need for a “headless” or a decoupled CMS architecture, where the front end component of the CMS is removed and the backend delivers content via an API.