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 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?

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.

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

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

Re: [hippo-community] Improving the Hippo CMS developer experience
by: wim.lustenhouwer | 13-10-15 09:03:34 (CEST)

Hi Jeroen, Junior developer here. And generally the most of my time spent developing is in debug mode. And I generally have a hard time finding some of my beans set to a request. So as an RRC i’d propose the following: decouple the HstRequest from an HstComponent. Here’s how i’d see this. Any

Re: Migration from 7.7 to Hippo10 Release
by: New to hippo | 13-10-15 08:14:27 (CEST)

Hello Anoop, I dont have login credentials and I am using community version 7 so how can I upgrade hippo. Thanks JB On Monday, October 5, 2015 at 3:44:03 PM UTC+5:30, a.gangadharan wrote: > > Hi > Upgrading from Hippo version 7.7 to 10.0 has not been tested and is not > supported. This means

Re: [hippo-community] Namespace Migrator reordering nodes
by: phammer | 12-10-15 15:51:04 (CEST)

Hi Unico, Yes, the disordered nodes have, as their primary type, the namespace being migrated. Additionally, they are the specific part under the namespace that is being modified and requiring the custom updater. namespace:specifictarget. -Paul On Friday, October 9, 2015 at 5:50:05 PM UTC-4,

Re: [hippo-community] Improving the Hippo CMS developer experience
by: brian | 12-10-15 11:27:26 (CEST)

Hi Jeroen, Nice initiative and good to address this. Two suggestions by head: 1) By default, integrate pluggable Spring Security support in the HST. Almost all of our implementations use some sort of security. Since HST is already Spring-based, this shouldn't be too hard. In the case security is

Improving the Hippo CMS developer experience
by: Jeroen Reijn | 12-10-15 11:15:45 (CEST)

Hi all, for one of the upcoming Hippo CMS releases we want to further improve the experience of developers working with Hippo CMS. Currently, Adrian and I are gathering input from everybody we know (both on- and offline) so that we can come up with a concrete list of areas that need our

Re: [hippo-community] Re: Using Spring Loaded with Hippo CMS
by: Jeroen Reijn | 12-10-15 10:27:38 (CEST)

Oops sorry for my extreme late response! Yes I indeed looked at the matter. Last week actually. You can find what to do in the Hippo 10 branch It seems you were very close. As far as I figured it out the context needs to be like

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.