New here?

Get 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 somewhere else 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 modelling 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.

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?

Simplify Upgrades with Hippo's Synchronization Add-on
June 15, 2015

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

Meet Hippo CMS 10 for Developers
May 27, 2015

Last week, we announced the release of Hippo CMS 10. Now we want to take the time to truly introduce this new release.

Re: [hippo-community] Exception when attempt login: cms or console
by: brian | 01-12-15 13:11:30 (CET)

Nice! So it was a clash after all. Probably the same classpaths (packagewise) in both libraries then. I didn't notice you've added CXF yourself, since it's also in Hippo. 2015-12-01 13:07 GMT+01:00 <>: > Hi Brian, > > *Problem* > The problem was in the *versions of the asm

Re: [hippo-community] Exception when attempt login: cms or console
by: | 01-12-15 13:07:03 (CET)

Hi Brian, *Problem* The problem was in the *versions of the asm libraries*. I have module where i am using this. *Solution* <dependency> <groupId>*org.apache.cxf*</groupId> <artifactId>*cxf-rt-frontend-jaxws*</artifactId> <version>*${cxf.version}*</version> <exclusions>

Taxonomy plugin does not create root folder
by: Martijn van der Vorst | 01-12-15 10:57:06 (CET)

Hello, I found an interesting problem today when implementing the taxonomy plugin. In my haste to get it all up and running I missed the "Configure" button in Essentials. Funilly enough it gives me the option to create Taxonomy items within the normal documents of the site (content/document/<sit

Re: [hippo-community] New maintenance tags with 3.2.2 commons collections version
by: Junaid K Sheriff | 01-12-15 10:51:42 (CET)

These artifacts are using latest version of apache commons collection 3.2.2 following our SECURITY ADVISORY CONCERNING JAVA DESERIALIZATION VULNERABILITY which is published in our .org site. We encourage all projects to remain on the regular maintenance release. Using a tagged artifact that is

Re: [hippo-community] @JcrPath isRelative not working
by: a.schrijvers | 01-12-15 10:37:17 (CET)

initial >> path. For this I set the following configuration on my document picker: >> isRelative=true, pickerRemembersLastVisited=false. >> This doesn't seem to work. It does work when I set isRelative=false and >> change the pickerInitialPath to an absolute path. >> >> Is there something

Re: [hippo-community] Upgrade Issues with hst:configurations not loading
by: a.schrijvers | 01-12-15 09:52:16 (CET)

Hey Jimmy, I suspect you do not have a bootstrap file that actually creates the node '/hst:hst/hst:configurations/common'. Most likely, you have however bootstrap files that want to add nodes below '/hst:hst/hst:configurations/common'. Thus, make sure that you check that you have a bootstrap

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.