Jahia: Detailed Technical Description
📅 Release Date
Jahia was founded in 2002 in Switzerland, born from the acquisition of the product originally developed by Xo3, a company that collapsed during the dot-com crisis. The first public version was released that same year. The platform has evolved significantly over time: Jahia 6 (2010) introduced the OSGi architecture, Jahia 7 (2015) brought headless capabilities, and Jahia 8 (2020) completed the transition to a modern, API-first Digital Experience Platform (DXP).
📝 License
Jahia follows an Open Core model: the majority of the source code is distributed under the permissive Apache 2.0 or MIT licence. A Community Edition is available free of charge. Advanced enterprise features (personalisation, 24/7 support, SaaS cloud) are available in the commercial Growth and Enterprise editions.
💻 Programming Language
Jahia is a so-called polyglot CMS: its core is developed in Java (J2EE standard), but developers can also build modules in JavaScript (NPM packages). Server-side rendering uses React as the templating engine, and the front-end relies on HTML, CSS Modules, and JavaScript/TypeScript, with Vite as the build tool.
🏛️ Architecture
- • Modular OSGi architecture: each module (bundle) is an independent component that can be deployed and hot-updated without restarting the server.
- • Hybrid API-first approach: Jahia can operate in headless mode (GraphQL or REST API), in traditional WCM mode (server-side HTML rendering), or both simultaneously.
- • Content repository based on the JCR (Java Content Repository) standard — Apache Jackrabbit Oak — with hierarchical storage of all content (text, images, videos, PDFs).
- • Cluster architecture for high availability in production: separation of browsing and authoring environments, with multi-datacenter replication.
- • Deployable on-premise, as a managed cloud SaaS (PaaS with strict per-tenant data isolation), or via public Docker images.
📂 Database
Jahia relies on several complementary storage layers:
- • Apache Jackrabbit Oak (JCR): the primary hierarchical content repository, storing metadata, structured content, and configuration data.
- • Relational database: MySQL, MariaDB, or PostgreSQL for persistent data and metadata storage.
- • Elasticsearch (optional): for full-text search and high-performance content indexing.
- • File system or object storage (S3) for binary assets (images, videos, documents).
- • Apache Unomi (built-in CDP): a dedicated database for customer profiles and audience segments used for personalisation.
⚙️ Key Features
✅ All-in-one CMS and DXP: Content management (jContent), personalisation (jExperience), and application integration (StackConnect) unified in a single platform.
✅ Headless and hybrid modes: Extensible GraphQL and REST APIs for decoupled architectures, or traditional HTML page generation — by choice or simultaneously.
✅ Multi-site management: Administer multiple websites, brands, and portals from a centralised interface, with shared templates and governance rules.
✅ Advanced visual editor: Edit (drag-and-drop) and Contribute modes for non-technical editors, with real-time preview.
✅ Workflow and governance: Configurable content validation workflows, and granular roles and permissions at the platform, site, page, or content element level.
✅ Native multilingual support: Full translation management, content localisation, and simultaneous publishing in many languages.
🔥 Advanced Features
🚀 Built-in Customer Data Platform (CDP): Apache Unomi embedded for real-time behavioural data collection, visitor profile building, and audience segmentation.
📊 Personalisation and A/B testing: Display different content based on visitor profile, geolocation, behaviour, or segment, with integrated A/B testing and analytics.
🔌 StackConnect — integration hub: Over 1,000 connectable applications (Salesforce, Marketo, CMIS, Alfresco, ERP, translation services, social networks, etc.) via standard connectors.
🔗 Extensible GraphQL API: A generic, customisable API to create custom data endpoints and integrate any front-end (React, Vue, Angular, mobile applications).
📦 CI/CD and cloud deployment: Provisioning API for DevOps pipelines, zero-downtime blue/green deployments, and self-service environment management.
💡 Java OSGi and JavaScript NPM modules: Maximum extensibility via Java bundles (OSGi) or JavaScript packages (NPM), with over 30 UI extension points.
🔐 Security
🔹 ISO 27001, GDPR, and HIPAA certifications: Compliance with the highest security and personal data protection standards across all layers of the platform.
🔹 Advanced authentication: Native support for LDAP, SSO, SAML, and OAuth for single sign-on and enterprise directory integration.
🔹 Granular access control (ACL): Roles and permissions defined precisely for each user or group, at the platform, site, page, or content element level.
🔹 Multi-tenant data isolation: Strict data segregation between customers in the PaaS cloud version, with no compromise on security.
🔹 Automatic security updates: In the SaaS version, security patches are deployed silently and rapidly, with no service interruption.
🔹 High-availability infrastructure: Data replication across multiple datacenters, 24/7/365 monitoring, and dedicated support for production environments.
✅ Pros and Cons
✅ Advantages
✔️ Complete DXP platform: CMS, CDP, personalisation, and integrations unified in a single product, eliminating the need for a fragmented tool stack.
✔️ Robust and scalable Java architecture: Ideal for large enterprises with high requirements in terms of performance, availability, and content volume.
✔️ Deployment flexibility: On-premise, SaaS cloud, or Docker — adaptable to any infrastructure constraint or IT governance policy.
✔️ Open Core Apache 2.0: Full access to the source code, complete transparency, and no proprietary dependency on the core.
✔️ High-level security certifications: ISO 27001, GDPR, HIPAA — well-suited to regulated industries (finance, healthcare, public sector).
✔️ Ergonomic visual editor: Marketing and editorial teams can manage content autonomously, without depending on developers.
❌ Disadvantages
❌ High complexity and steep learning curve: The platform's richness (OSGi, JCR, GraphQL, Java/JS modules) requires experienced developers.
❌ Cost of enterprise editions: Advanced features (personalisation, support, SaaS) are reserved for commercial editions at a significant price point.
❌ Less suited to small projects: The required architecture and infrastructure are oversized for simple brochure sites or small online shops.
❌ Smaller open source community: Compared to WordPress or Drupal, the ecosystem of free community modules is less extensive.
❌ Significant server resource requirements: The Java stack (JVM, Jackrabbit, Elasticsearch) demands considerably more RAM and CPU than a standard PHP CMS.
🌐 Official Website
Need more details on a specific point?
