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] jcr path image variant
by: | 31-07-15 16:57:08 (CEST)

Hi Mahesh This works if i'm referencing an image which is part of the document bean, but for an image I've added as a component parameter I can't seem to access any of the variants. Thanks! Ashil On Friday, July 31, 2015 at 11:59:50 AM UTC+1, m.acharya wrote: > > Hi Ashil > > In the rendering

Re: [hippo-community] trying to make repository available on external port
by: Jeroen Reijn | 31-07-15 16:28:05 (CEST)

Hi Jay, are you just trying to expose the repository over RMI? In that case that's a setting usually placed in the context.xml file in tomcat. Jeroen On Fri, Jul 31, 2015 at 3:31 PM, Jay F <> wrote: > We're using hippo enterprise edition 7.9.1 with tomcat 6.0.24 on centos 6.6 >

Re: trying to make repository available on external port
by: Jay F | 31-07-15 15:36:21 (CEST)

I've currently got the attached repository.xml to try and run it with just jackrabbit, but this is giving me a few errors, starting with ERROR main [RepositoryImpl.<init>:366] failed to start Repository: Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.pool.DerbyPer

trying to make repository available on external port
by: Jay F | 31-07-15 15:31:01 (CEST)

We're using hippo enterprise edition 7.9.1 with tomcat 6.0.24 on centos 6.6 Our current instance is using oracle as an external repository, that's working fine but we're trying to replace this instance with another that does not use oracle because of reasons. The first thing I did was to change

Re: [hippo-community] Document not visible in cms
by: w.borgbarthet | 31-07-15 15:23:19 (CEST)

Hi Eric, how were these documents created? I can see the problem: the "validationlabels" document's handle's name doesn't match the variant name (see [1] for info on what a handle is). I'm guessing this was created by moving nodes around in the console or by using the JCR API directly, or maybe

How to display multiple documents under the same page
by: Gangel Dávid | 31-07-15 14:59:03 (CEST)

Hi, I would like to display multiple content on the same page. Let's say I have the following content structure: Root - Translated folder1 - Simple Document1 - Translated folder2 - Simple Document2 - Simple Document3 AFAIK under one sitemapitem I can reference one relative

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.