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

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 configuration s, 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

Latest Blogs

How to: Integrate Hippo CMS with an ElasticSearch enterprise search engine
January 28, 2015

Our most recent Hippo Lab focuses on integrating an open source Web Content Management System with an ElasticSearch enterprise search engine.

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

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

Unable to perform a versioning operation on a non versionable node
by: | 02-04-15 00:04:45 (CEST)

We are trying tom use the WorkflowPersistenceManager to update docs. We are running into two big issues: 1. After everything we try we cannot seem to get the correct combination to simply update the document in the JCR. To that end, we have taken to removing the object from the JCR and then rec

Re: [hippo-community] Content/Context Aware JAX-RS Services - HOWTO
by: j.reijn | 01-04-15 21:49:35 (CEST)

Hi, We don't have an exact example because in nature they are slightly different. I would advise you to take a look at the product related resources in the hippo test suite.

Re: Content/Context Aware JAX-RS Services - HOWTO
by: Gangel Dávid | 01-04-15 18:00:15 (CEST)

So what I want to reach is just to get a better understand between the plain and context aware rest api. Thats why I would like to see the same implementation for the same content. Can someone add some hit at least please? From the documentation I don't see what is the structure of the repositor

Re: [hippo-community] Eclipse dependency error on build
by: marijan milicevic | 01-04-15 17:50:49 (CEST)

On Wed, Apr 1, 2015 at 5:31 PM, <> wrote: > Sorry for digging up an old thread, but we've also started having this > problem. > > Is there a solution, beyond us manually overriding the version number of > eclipse.core.resources to 3.3.0? > > (And yes, it's weird, I can't find any

Re: [hippo-community] Eclipse dependency error on build
by: | 01-04-15 17:31:43 (CEST)

Sorry for digging up an old thread, but we've also started having this problem. Is there a solution, beyond us manually overriding the version number of eclipse.core.resources to 3.3.0? (And yes, it's weird, I can't find anywhere that indicates 3.4.0 even exists) Thanks, Mark. On Wednesday,

Re: [hippo-community] Making a date field optional makes it unusable
by: j.reijn | 01-04-15 17:10:20 (CEST)

Great. Thanks Joost! We'll look into it. ps. If this is an issue for a specific customer please also file a JIRA issue in the customer support JIRA project, so it will get picked up ASAP. On Wed, Apr 1, 2015 at 10:12 AM, Joost Oudeman <> wrote: > I filed an issue for this bug:

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.