New here?

Our tutorials 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.

Quick links


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

Have a look

What is Hippo CMS?

Hippo CMS is a little bit different from other CMS systems. 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


Query content using REST, or import content from somewhere else into Hippo. Hook up an external application into the rendering phase via Spring. Use external data systems to feed our personalisation engine


Protect your content with fine grained authorizations and LDAP support

The CMS Features You'd Expect

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


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

Flexible Content Model

Fully customizable document oriented content model with built-in modelling tools. Strict separation of content from presentation. Reuse content across Websites, Mobile Websites and apps


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! Download our demo. Or look under the hood if you like, we share our source code.

Latest Blogs

Kickstart your projects with the Hippo feature library
September 25, 2014

With this feature library, you can add commonly used functionality to your project

Hippo CMS Integration Patterns
October 15, 2014

At this year's Hippo GetTogether, Senior Architect Jeroen Reijn presented examples of integration patterns used by Hippo clients in their existing application landscape.

Re: [hippo-community] import-tool errors
by: Steve McCoole | 20-12-14 22:20:06 (CET)

After a few more hours of trying to work this out, I've had to abandon the effort.  I sort of got it to work, but then PDF's starting throwing Tika errors and I had some strange issues where imported images would sometimes show up in the CMS console and some times would not, making me concerned abou

Re: [hippo-community] Link vs Compound
by: t.jeger | 20-12-14 12:04:29 (CET)

Hi, I guess the answer really depends on your actual use case. The compound solution is kind of the normal thing to do, and it means that you have a 1-to-1 (or even a 1-to-many) relation between your document and your "group of fields", each instance of the compound is embedded within a document and

Link vs Compound
by: | 20-12-14 02:46:01 (CET)

I need to add some fields that are going to be used by 4 documents, what is the best practice?: 1. Create a compound component and embedded into each document OR 2. Add Links to the documents that points to other type of document that was created to handle all fields needed Thank you

set logo for a channel
by: Sachin Jain | 20-12-14 00:02:44 (CET)

Hi I was looking into setting the logo for a channel (website/facebook). I see in the green demo project there are logos for website and facebook channel in: /content/gallery/channels/website.png /content/gallery/channels/facebook.png but cant find a place where they are defined or configured. t

Re: [hippo-community] import-tool errors
by: Steve McCoole | 19-12-14 22:47:57 (CET)

So far I have had to add the following to the applicationContext.xml:     <bean id="importConfigTaxonomyMappings" class="org.springframework.beans.factory.config.MapFactoryBean">        <property name="sourceMap">            <map>            </map>        </property>    </bean>     <bean id="importC

Re: [hippo-community] import-tool errors
by: Steve McCoole | 19-12-14 22:09:30 (CET)

That's what I followed.   On Fri, Dec 19, 2014 at 2:53 PM, Jeroen Hoffman <> wrote: Hi Steve, As far as I know the quickstart at generates a working example project using an archetype. We checked that quite recently. Is tha

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.