Gentics CMS is where content gets made. Editors write in a real WYSIWYG editor, admins manage users, roles and workflows, and the CMS publishes everything into Gentics Mesh, from where portals, apps and AI agents consume it. It has been in production at public administrations, chambers and enterprises for more than two decades, and since Gentics CMP 9 the complete code is public.
| Repository | Component |
|---|---|
| gentics/cms-oss | This repo. Gentics CMS – editing, publishing, Workspace, MCP tools |
| gentics/mesh | Gentics Mesh – headless content repository, search, Content RAG, MCP server |
| gentics/cmp-portals | Portal | php and Portal | java – render content from Mesh |
| gentics/cmp | Umbrella: platform changelog, guides, Helm chart, licensing overview |
Content flows from Gentics CMS into Gentics Mesh and from there into the portals or your own applications. The cmp README has the big picture and the cross-repository getting-started guide.
- Editing that editors like. Content trees as websites think of them, a WYSIWYG editor based on Aloha Editor, in-place editing, multi-language content, automatic navigation and clean URLs.
- Publishing into Mesh. Pages, files, images and structured objects are published into Gentics Mesh and are available there through REST and GraphQL.
- Workspace. The AI co-pilot for editors (
workspace-ui): a chat-based assistant that works on the content of the CMS, with every action bound to the user's CMS permissions. AI calls go through GenAIx, the Gentics-hosted AI service, via the CMS proxy, so no key ever reaches the browser. - MCP tools. The CMS exposes its content operations through the Model Context Protocol
(
cms-core/.../mcp), so agents work with the same permission model as humans. - A complete REST API (
cms-restapi) with OpenAPI documentation, a Java client and TypeScript models for the UIs. - Built to run for years. Link checker, search, translation, clustering, and a Keycloak integration, content staging, forms and multichannelling as Enterprise Modules.
cms-oss/
├── base-api, base-lib shared foundations
├── cms-api, cms-restapi public API and REST models (OpenAPI)
├── cms-core the server: publishing, permissions, rendering, MCP tools
├── cms-oss-server server distribution (Docker image gentics/cms-oss)
├── cms-ui editor and admin UI, NX monorepo (Angular)
├── workspace-ui Workspace, the AI co-pilot for editors (React/Vite)
├── cms-aloha-* Aloha Editor bundle and plugins
├── cms-cache, cms-cluster, cms-search, cms-linkchecker, cms-translation
├── cms-oss-doc, cms-oss-changelog
├── cms-integration-tests
└── ee/ Enterprise Modules (BUSL-1.1)
├── cms-contentstaging content staging between environments
├── cms-forms, formgen forms and the form generator
├── cms-keycloak SSO with Keycloak
├── cms-multichannelling one content base, many channels
└── cms-server enterprise server distribution
The quickest way to a running CMS is the Docker image gentics/cms-oss. The installation guide walks you through the setup with MariaDB, the configuration files and the first login. For Kubernetes, use the Helm chart of the Gentics CMP umbrella chart.
Requirements: Java 17, Maven 3.9+, Node.js (for the UIs), Docker (for the integration tests).
git clone https://github.com/gentics/cms-oss.git
cd cms-oss
mvn clean install -DskipTestsThe reactor builds the core and the ee/ modules. The UIs have their own tooling, see
cms-ui/README.md (NX) and workspace-ui/README.md (Vite,
with a local GenAIx mock for development).
Everything the UIs do goes through the REST API, so you can too:
# log in and get a session
curl -X POST http://localhost:8080/rest/auth/login \
-H 'Content-Type: application/json' \
-d '{"login":"<user>","password":"<password>"}'The full API reference is in the guides.
dev– next releasehotfix-<version>– maintenance of released versionsf-<ticket>– feature branches
- Guides – installation, configuration, development, API
- Changelog
- System requirements
- Gentics CMP changelog and guides across all components
- Issues: github.com/gentics/cms-oss/issues
Gentics CMS is open core:
- Core – Apache License 2.0. Everything outside
ee/. OSI-approved open source: run it in production, modify it, redistribute it. - Enterprise Modules – Business Source License 1.1. Everything inside
ee/: content staging, forms and the form generator, the Keycloak integration, multichannelling and the enterprise server distribution. The source is public and free to use for development, testing, evaluation and demonstration. Production use requires a commercial license – contact sales@gentics.com. Every module converts to Apache 2.0 three years after its release (Change Date); the exact dates are inee/LICENSE.
The core runs without ee/. LICENSING.md has the details, the
cmp repository the overview across the platform.
Pull requests are welcome.
- Contributions to the core are accepted under the Apache License 2.0 with a DCO sign-off (
git commit -s). - Contributions to
ee/additionally need our Contributor License Agreement (corporate version). The CLA bot asks on your first pull request that touchesee/.
See CONTRIBUTING.md. Found a bug? Open an issue in this repository.
Gentics Software GmbH, the company behind Gentics CMS, offers product maintenance, developer support, consulting and custom development. Contact sales@gentics.com.
Copyright (c) 2014-2026 Gentics Software GmbH. Gentics is a registered trademark of Gentics Software GmbH,
see TRADEMARKS.md.