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 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 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] How to leverage CKEditor hippopicker plugin
by: k.salic | 28-07-16 15:44:26 (CEST)

Hi Victor, A way of doing it is extending the org.hippoecm.frontend.plugins.ckeditor.CKEditorNodePlugin and adding a similar dialogs as the linkpicker or the imagepicker. You'll need to see how the js ckeditor plugin works as well of the existing imagepicker and/or linkpicker and how it

Re: [hippo-community] Using Hippo with AngularJS 2 and Spring-Boot
by: Jasper Floor | 28-07-16 15:40:40 (CEST)

On Thu, Jul 28, 2016 at 3:39 PM, Drew Jocham <> wrote: > I am creating a CRM with spring-boot and AngularJS. I will start the > project using JHipster once Angular2 is officially released. Can I > integrate this project into Hippo once I get the where I need it. > That's a

Using Hippo with AngularJS 2 and Spring-Boot
by: Drew Jocham | 28-07-16 15:39:18 (CEST)

I am creating a CRM with spring-boot and AngularJS. I will start the project using JHipster once Angular2 is officially released. Can I integrate this project into Hippo once I get the where I need it.

Re: [hippo-community] Question and sitemap
by: Jasper Floor | 28-07-16 09:55:40 (CEST)

You can create a sitemap item "contentfolder" with relativecontentpath "contentfolder/contentdocument". Then the document name is hidden and you can still use hst:componentconfigurationmappingnames. mvg, jasper On Thu, Jul 28, 2016 at 9:41 AM, <> wrote: > Hi, > > I am trying

Question and sitemap
by: | 28-07-16 09:42:04 (CEST)

Hi, I am trying to link to documents with the fixed name "contentdocument" which are located in the folder hierarchy. As I'm trying to hide this fixed name and rather would like to use only the corresponding foldernames in the resulting URL, I have a sitemap entry _any_ with relative content

Re: [hippo-community] Document Type Editor - Missing field types
by: Bert Leunis | 28-07-16 09:38:01 (CEST)

On Wed, Jul 27, 2016 at 10:20 AM, Christopher Dodunski <> wrote: > Hi Mathijs, > > Yes, you are correct! I am using Android Tablet, and yes, the scroll bar > is hidden by default (silly me). I 'll know in future. :-) > You are not the only one running into this.

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.