New here?

Our Getting Started tutorial will get you up to speed with Hippo development.

Follow the Hippo Trail


The relations between repository, CMS and delivery tier.

How it all fits together

Developer Info

Source code, forge, license, roadmap and system requirements.

Developer Info


Interested? We're always on the lookout for new talent.

Have a look

What is Hippo CMS?

Hippo CMS is an open source Java CMS. We built it so you can easily integrate it into your existing architecture.

Open Platform

We are big believers in open source. We use and contribute to many open source components - and our entire core is available under the Apache License

Java Stack

What you'd expect from a Java environment: easy to integrate, testable, ready for continuous integration, and sticking to familiar Java standards such as JCR 2.0 and JAX-RS


Highly scalable platform which supports both clustering and replication


Performance matters to us! Hippo CMS  scales both  horizontally and vertically and makes use of multi-layered caching to squeeze the most out of your implementation


Query content using REST, or import content from elsewhere into Hippo. Hook up an external application into the rendering phase via Spring. Build a Mobile app or an AngularJS app that consumes content from Hippo. Use external data systems to feed our personalisation engine


Protect your content with fine grained authorizations, LDAP support, and secure replication

The CMS Features You'd Expect

Content editing, workflow, history, version control, image library, user management, out of the box

Multi-lingual, Multi-site, Multi-channel

Out of the box support for multi-language, multi-site and multi-channel implementations. Cross-domain, cross-site, cross-language and cross-channel linking between documents are resolved automatically.

Separate Content from Presentation

Break free from page oriented development. Redesign your website without modifying content and reuse your content across websites, mobile  apps, etc. Use Hippo's  fully customizable document-oriented model and built-in modeling tools to separate content from presentation.


Deploy on-premise or in the cloud on your preferred servlet container

Extensible Components

Use or extend existing components from the Hippo Feature Library or build your own. Use JSP, Freemarker or AngularJS to render your components

Give Control To End Users

End users can manage page configurations, menus, URL structures and component mappings. Without you having to go into code


Deliver personalized pages to visitors with the Relevance module


We don't mess with your HTML output. Use whatever web framework you like; Bootstrap, AngularJS, it's up to you


Out of the box querying, facetting and full-text search capabilities based on Apache Lucene - or hook up Elasticsearch if you need more power


Can I try it out?

Yes! Try the online demo of  Hippo Enterprise Edition or create your own  project with Hippo Community Edition.

Look under the hood if you like, we share our source code.

Help, I'm Lost!  This seems a bit technical. Take me to the business site.

Gallery Media Banner

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s

Did you see this?

Synchronization Add-on
June 15, 2015

Use the Synchronization Add-on to smoothen the process of continuous delivery.

Hippo CMS Videos
November 28, 2016

Watch some instructional videos on working with Hippo CMS as content editor.

Re: [hippo-community] Reload updater editor registry on startup
by: woonsan.ko | 26-05-17 22:12:55 (CEST)

Hi Dave, The auto-export probably exported the registry.xml as enhanced system view XML, not a simple system view XML, with "combine" merging option. For that reason, that cannot be reloaded on startup unfortunately. See "Combine and Overlay Enhanced System View XML Directives" section in [1].

Reload updater editor registry on startup
by: Dave Kennedy | 26-05-17 21:50:51 (CEST)

I added a new updater editor script, which changed the file at bootstrap/configuration/src/main/resources/configuration/update/registry.xml. I updated the version of the node from 1.00.01 to 1.00.02 in the bootstrap/configuration/src/main/resources/hippoecm-extension.xml file, so it looks like

Re: [hippo-community] ResourceBundle
by: SumitP | 26-05-17 11:04:28 (CEST)

Hi William, Thanks a lot for your valuable response!!! Thanks&Regards, Sumit P. On Friday, May 26, 2017 at 1:03:27 PM UTC+5:30, william.borgbarthet wrote: > > Hi Sumit, > > I guess built-ins don't work for tags, sorry about that. You can read the > label in your component and set that as an

Re: [hippo-community] ResourceBundle
by: william.borgbarthet | 26-05-17 09:33:27 (CEST)

Hi Sumit, I guess built-ins don't work for tags, sorry about that. You can read the label in your component and set that as an attribute and use the built-in there. HstComponent: ... request.setAttribute("label", label); Template: ${label?replace("XXX", catTemp); At that point you probably

Re: [hippo-community] ResourceBundle
by: SumitP | 26-05-17 09:09:49 (CEST)

Hi William, Thanks for quick reply!!! I resolved these issue by accessing resource bundle at backend and replaced placeholder with particular value. But in some cases I need to replace placeholder with value in front end (Free marker template), as You told I tried (<@fmt.message key="foo"/>?re

HstQuery Field Boost Without Searching Entire Document
by: Brendan S | 26-05-17 01:03:44 (CEST)

I have read the documentation about boosting search results for certain fields: The documentation implies that this only works if you search against the entire document. Is it possible to

Looking for assistance? You're welcome to ask for help. We have a very active mailing list! Please do check the tutorials and the guidelines first, though.