Jahia

Jahia is built on JCR 2.0, defining content types via CND (Compact Namespace and Node Type Definition) files — a schema-as-code approach for developers. Property types span STRING, BOOLEAN, LONG, DOUBLE, DATE, BINARY, REFERENCE, WEAKREFERENCE, URI, NAME, PATH, and DECIMAL, with abstract mixins for reusable field sets (8.2.1 added the jmix:listedInRestrictions mixin) and choicelistValue/choicelistValues fields exposed via GraphQL. The CND approach is powerful but more complex than modern API-first schemas, and polymorphic/union field types are not natively supported.

JCR REFERENCE and WEAKREFERENCE properties support linking nodes, and JCR's tree structure enables parent-child traversal. Bidirectional lookups are possible via JCR-SQL2/XPath queries but require developer implementation rather than being automatically exposed in the API. Not graph-native, so reverse-relationship traversal is less ergonomic than purpose-built graph CMSes.

Jahia's component architecture allows content types to be composed into pages as nested components within Page Builder, with mixins providing abstract/reusable property sets applied to any node type. The jContent editorial interface supports block-based page composition, and the now-stable JavaScript Modules path adds React-native component nesting via Island Architecture. Solid for a traditional DXP — components nest within pages and sub-areas — but not portable-text-style unlimited nesting for pure content modeling.

JCR enforces type-level constraints (mandatory properties, value constraints via regex in CND) at the repository level — Jahia 8.2.0 closed a gap where the GraphQL API could previously create nodes with missing mandatory properties — and Jahia modules can add custom pre-save validation logic. Standard required, type, and regex constraints are built-in via CND definitions; AI-assisted content generation also triggers the standard validation/approval workflow rather than bypassing it. Cross-field validation or a visual rule engine for editors is not a documented out-of-box feature; custom validation requires module development.

JCR 2.0 provides native versioning at the node level — Jahia exposes this as full version history with rollback for content editors, and Page Builder now includes a redesigned version comparison interface. Scheduled publication is supported via the scheduled-publication-workflow module that separates validation from publication date/time, and workflow approval adds an audit trail. No documented content branching beyond draft/live workspaces.

Page Builder reached full feature parity with the legacy Page Composer in March 2026 and is now Jahia's recommended editor for all new projects: in-context visual editing, real-time preview, component management, side-by-side translation screen, insert-anywhere in content lists, and in-context preview of personalized content variants per audience segment. Non-technical editors can rearrange and edit page components without developer involvement, and drag-and-drop behavior in pickers has been improved. Not quite drag-and-drop best-in-class (AEM, SXA) but a solid traditional-DXP editor.

CKEditor 5 integration (1.0 module released June 2026) modernizes the rich-text editor with macro support, styles dropdown, CSS support, natively accessible HTML, and optional generative-AI tools for assisted writing, rewriting, translation, and summarization (OpenAI/Anthropic/Google/Mistral/DeepSeek configurable). Output remains an HTML blob stored in JCR rather than a portable AST, capping the score below platforms with structured rich-text formats.

jContent 3.5 (late 2025) and 3.6 (March 2026) improved the built-in media library with image size/format/usage metadata in thumbnail and list views, better single/multi-selection, automatic standardized file naming on upload, and Page Builder performance improvements. The Bulk Edit Content module (March 2026) lets editors update large volumes of structured content and metadata. DAM connectors exist for Cloudinary and Keepeek in the Jahia Store; a third-party Bynder integration is available via Gladtek (not in the Jahia Store). Native focal point and URL-based transforms are not built-in — provided via the Scaleflex CloudImage integration.

No documentation or product announcements indicate real-time co-editing (Google Docs-style) in Jahia. Each content item has an explicit lock action and the JCR/workflow architecture implies optimistic locking with workflow handoffs for review. Redesigned workflow/publication screens (March 2026) and the new Bulk Edit Content module improve multi-editor efficiency but do not enable simultaneous co-editing of the same node.

Jahia provides a customizable workflow engine with multi-stage approval processes, role-based transitions, and conditional routing; the Scheduled Publication Workflow module separates validation from publication timing. The Publication Dashboard gives editorial overview, March 2026 brought redesigned workflow and publication notification screens, and the new Bulk Edit Content module streamlines mass updates through the same validation pipeline. A caveat: custom JBPM-based workflows and the Workflow Extender module are now deprecated, with Jahia's replacement scheduled by end of 2026, creating modest near-term migration risk for shops relying on bespoke workflow logic.

Jahia provides a comprehensive GraphQL API (graphql-core module) and REST endpoints. GraphQL Provider 3.5.0+ adds Relay-standard pagination (cursor-based and offset-based), permission-based checks for introspection queries, a configurable per-page node limit (graphql.fields.node.limit), and Jahia 8.2.3 updated GraphQL types for better cross-schema consistency; the layer exposes every JCR node with filtering, pagination, locale support, subscriptions, and is extensible via Apollo Client. Available in both Jahia Cloud and self-hosted deployments. Not a purpose-built headless API (delivery and management share endpoint layers) but the GraphQL surface is broad, secure, and well-instrumented.

Jahia Cloud uses Amazon CloudFront for CDN-backed delivery with global PoPs, including a new APAC region available as of March 2026; CDN/WAF dashboards now provide cache-log analysis. CloudFront's April 2026 cache-tag invalidation support enables more granular purges, and Jahia 8.2.3 reworked HTTP header management for optimized caching. Self-hosted deployments still have no built-in CDN — operators must add their own — and edge-side personalization is not documented.

Jahia's StackConnect integration layer covers external connectivity (250+ connectors, many webhook-based) and the JCR observation API supports internal event listening, but public documentation does not describe a first-class outbound-webhook service with event filtering, HMAC payload signing, retry logic, or delivery logs. The traditional Java-DXP architecture supports event handling, but the polished webhook tooling found in modern headless CMSes is not evident in product docs.

Jahia is a hybrid CMS — coupled rendering, headless GraphQL delivery, and now stable native JavaScript Modules (React TSX + Island Architecture SSR/CSR) — with @jahia/nextjs-sdk as the primary official frontend SDK and headless-development guides centered on Next.js. Rich-text output is HTML (even after CKEditor 5), limiting non-web channels. The JS Modules path is a rendering-model improvement rather than a channel expansion, and SDK breadth beyond Next.js/React remains thin compared to purpose-built headless platforms; no native-mobile SDK is documented.

Jahia's segmentation engine is powered by Apache Unomi (open-source CDP co-created by Jahia), supporting behavioral, contextual, declarative, and socio-demographic data combined with CRM integration data. Segments update in real time with no technical intervention. StackConnect (Workato) provides 1000+ connectors for external CDP enrichment. This is genuine native segmentation at a strong tier-2 DXP level.

Jahia serves different content variants to different audience segments natively, with in-context preview per audience available directly in Page Builder as of the March 2026 update (the default variant of personalized content is now visible in Page Builder without opening the personalization window, and jExperience elements are color-coded purple). Personalization is content-item and full-page capable. Not quite best-in-class (lacks ML-driven decisioning engine), but native and editor-accessible.

Jahia includes built-in A/B testing for individual content items and full pages, with traffic allocation among variants and conversion rate analysis across segments and devices. Dedicated A/B testing dashboards were added/updated in the March 2026 release, and jExperience provides control-group configuration and metric monitoring on the Personalizations and AB tests page. Statistical significance reporting is not explicitly documented, which prevents a higher score, but this is genuine built-in experimentation with analytics feedback.

Jahia's scoring plans define affinities between visitors and offers, surfacing the most relevant content based on accumulated profile data — this is editorial rule-based with affinity weighting, not ML-based collaborative filtering. There is no documented algorithmic recommendation engine with collaborative filtering or neural embeddings. Adequate for rule-driven personalization but well below platforms with ML-based recommendation systems.

Jahia Augmented Search 4.x (Elasticsearch-based, 4.0 Nov 2025 on Elasticsearch 9, 4.1 April 2026 with faster indexing and optimized network traffic) provides full-text search across pages, content, and documents with typo tolerance, stemming, faceting (termFacet, treeFacet/hierarchical, rangeFacet, conditional facets), configurable boosts and Function Score for relevance tuning, and language plugins for major languages. Permissions, tags, and categories enable precise filtering. This is a genuine enterprise search offering.

Augmented Search is itself an Elasticsearch-based module, meaning Elasticsearch integration is the native path with a dedicated elasticsearch-connector. No official Algolia or Typesense connector is documented on the Jahia Store. Custom extension of Augmented Search is possible through its GraphQL API. StackConnect could bridge to external search services but no documented pattern exists.

Jahia is a DXP/CMS platform, not an e-commerce platform. There is no native product catalog, cart, checkout, pricing, or inventory management. Commerce content can be managed as editorial content but Jahia has no genuine commerce engine.

StackConnect (Workato) provides 1000+ no-code connectors that could include Shopify or Salesforce Commerce Cloud, but no dedicated pre-built commerce connector (product picker UI, API federation) is documented specifically for Jahia. No Shopify, commercetools, or BigCommerce official module appears in the Jahia Store.

Jahia's flexible JCR content type system (CND definitions) could be used to model product content with custom attributes and rich media fields, but no product-specific content type templates or commerce-aware field patterns are documented out-of-the-box. Generic content types repurposed for product content is the realistic scenario.

Jahia has rich built-in analytics powered by its Apache Unomi CDP, accessible in-context within the authoring interface. Metrics include referrer data, UTM parameters, geolocation, devices, browsers, site searches, forms, and CRM data. The March 2026 update added new A/B testing, personalization, and login event dashboards with filtering; the Content Reports module was revamped in 2026 with improved reporting UX. This goes well beyond basic usage metrics into genuine content performance analytics.

StackConnect powered by Workato provides 1000+ no-code connectors including Google Analytics, Salesforce, Microsoft Dynamics, Marketo, Microsoft Power BI, Slack, Zendesk, and other analytics/CRM platforms. The Jahia Store also lists a dedicated Google Analytics for jExperience module. This covers the documented integration path with major analytics platforms at the 65+ threshold.

Jahia's single dashboard manages multiple sites, each with its own domain, URLs, templates, language configuration, and user roles. The Local Site Manager feature allows localization of global content for local sites, enabling content reuse across sites. Centralized governance with granular roles, approval workflows, and audit trails is explicitly documented.

Jahia enforces mandatory language properties per content item and each language has its own independent workflow for publication — locale A can be published without publishing locale B. Language fallback/mixing automatically displays content in the default language when a translation is unavailable. Supports 100+ languages. Document-level localization with per-locale publishing independence.

Jahia has an official strategic partnership with Translations.com (TransPerfect's GlobalLink TMS) with a dedicated certified connector on the Jahia Store. One-click content submission for translation, real-time progress tracking, and automatic return of translated content are documented. The DeepL connector was updated January 2026 with one-click machine translation of pages in jContent, side-by-side review, and multilingual workflow support. SDL connector also available.

Jahia's multi-site architecture supports multiple brands under one platform with shared component libraries, independent site configurations, and centralized user/role management. Approval workflows and audit trails (via JCR versioning) provide governance structure. However, explicit cross-brand policy enforcement or dedicated multi-brand governance UI beyond multi-site management is not prominently documented.

Jahia's jContent serves as an integrated media library with folder structures, metadata, custom tagging/taxonomy, and JCR-based versioning for assets. However, it is not a purpose-built DAM — usage tracking across content, rights/expiry management, and bulk asset operations are not explicitly documented. Optional Jahia Store integrations for Cloudinary and Keepeek bridge the gap for enterprise DAM needs; a third-party Bynder integration exists from Gladtek but is not in the Jahia Store.

Jahia has no native CDN or on-the-fly image transformation engine. The Cloudinary Picker module provides cloud CDN + transformations (resize, crop, format conversion, WebP) when installed, but this is an add-on, not a native capability. Without Cloudinary, image delivery is basic static file serving. Score reflects the add-on model rather than native capability.

No native video hosting, transcoding, or adaptive bitrate streaming in Jahia's core platform. Video requires external embedding (YouTube/Vimeo) or the Cloudinary Picker / Keepeek Content Picker for cloud-hosted video. No documented captions management or audio file management beyond basic file storage.

Jahia 8.2.3 (March 2026) brought Page Builder to functional parity with the legacy Page Composer — production-ready in-context WYSIWYG editing with drag-and-drop placement, real-time preview, compare-preview-vs-live, customized preview, and inline insertion of content items anywhere in lists/areas. In-context preview of personalized variants is integrated. Continued jContent Page Builder performance improvements through mid-2026. Not as polished as modern headless visual editors (Sitecore Pages, Contentful Compose) but a genuine, mature visual authoring experience.

Jahia uses a jBPM-based workflow engine supporting multi-step approval processes with configurable states (draft, review, publication request), role-based routing (contributors, reviewers, editors-in-chief), notification system for task assignment, and JCR versioning for audit trail. The March 2026 release included a full redesign of workflow and publication notification screens. Custom workflow definitions are possible through module configuration. Parallel approval paths and SLA enforcement are not explicitly documented.

Jahia supports scheduled publication (publish at a future date/time) and auto-unpublish/expiry with timezone awareness as standard editorial features. A content calendar UI is referenced in editor/marketer tutorials but not clearly documented as a distinct calendar view. Release bundles (atomic multi-item publish) and explicit bulk scheduling are not documented.

No evidence of simultaneous multi-author editing, presence indicators, inline commenting, or @mention notifications in Jahia's authoring interface. The JCR-based workspace architecture (edit vs live) implies a lock-or-overwrite model rather than real-time collaboration. User and group management exists but collaborative authoring features are absent from documentation.

Jahia Forms Core 3.18.1 (April 2026) adds multi-file uploads, new input types (numeric, phone), improved accessibility, and server-side validation for file uploads — on top of multi-step forms, conditional display logic, submission storage with CSV/PDF/XLS export, email notifications, and form prefill from visitor profile/geolocation via the Forms Prefill module. Progressive profiling via profile-based prefill exists but a turnkey progressive-profiling UX and webhook-on-submit are not documented as native features.

No dedicated pre-built certified ESP connector (Mailchimp, Marketo, HubSpot, Brevo) is documented in the Jahia Store. StackConnect (Workato with 1000+ connectors) can integrate with major ESPs but is a general-purpose integration tool requiring configuration rather than a turnkey CMS-native ESP connector. Email notifications from forms are built-in but email campaign orchestration is not.

Jahia's jExperience module provides behavioral triggers (goal tracking from visitor interactions), visitor scoring (affinity-based lead scoring), campaign tracking, and engagement analytics — genuine marketing automation primitives. However, drip campaign orchestration, nurture flows, and multi-channel campaign management are not native Jahia features. StackConnect provides integration with external automation tools.

Jahia's jCustomer powered by Apache Unomi (which Jahia co-created and maintains) is a genuine native CDP delivering unified customer profiles, real-time segment evaluation, behavioral event streaming, identity resolution, and direct audience sync for personalization. This is deeply embedded in the platform rather than a third-party add-on. Falls short of enterprise CDPs on scale and ML enrichment.

The Jahia Store offers modules across analytics (GA, Kibana, Content Reports 2026), authentication (OAuth/SAML/LDAP/Okta/Keycloak/CAS), DAM (Cloudinary, Keepeek, Dalim), search (Elasticsearch/Augmented Search), translation (GlobalLink, DeepL, SDL), AI (Claude, Gemini), and developer tools. Modules are classified by support status (Supported/Community/Legacy). StackConnect (Workato) adds 1000+ external connectors. Solid for a tier-3 DXP but the store itself is smaller than Contentful/Contentstack marketplaces.

A Webhooks module is referenced in the Jahia Store and the developer documentation describes an OSGi rules engine for event-driven patterns; external systems can also send data to Jahia via a REST API to trigger listeners for content-modification events. However, comprehensive documentation on covered event types, filtering, signed payloads, retry-on-failure, and webhook management UI is not publicly available. The rules/event system is developer-oriented and requires custom configuration.

Jahia provides a GraphQL API for headless delivery (GraphQL Core Provider updated February 2026 with improved authorization for introspection and a custom HTTP header for live workspace operations) and dual workspaces (edit/draft and live). Personal API tokens enable authenticated headless access. Headless preview integration still requires developers to implement custom preview endpoints against Jahia's draft content API; turnkey shareable preview links and branch-per-environment promotion workflows are not documented as out-of-the-box features.

Jahia has a sophisticated JCR-based RBAC system supporting custom role definitions, node-level and property-level (field-level) ACL, site-specific and language-specific permissions, and team management. SSO is well-supported via SAML2, OAuth 2.0/OIDC, LDAP, CAS, Okta, Keycloak, and AWS Cognito modules. SCIM for automated user lifecycle management is not explicitly documented.

Jahia 8.2 positions GraphQL (via graphql-core, endpoint /modules/graphql) as the primary recommended API and deprecates the JCR REST API for content manipulation, with an interactive GraphQL Playground shipped in Developer Tools and custom SDL schemas supported. 8.2.0 added a dedicated GraphQL API to administrate External Data Provider mount points and fixed content-creation validation bugs. The API is GraphQL-first but still layered on a JCR-centric core rather than a purpose-built content-delivery API, capping the score below modern headless platforms.

Jahia Cloud is backed by AWS and OVH with 300+ edge locations providing CDN-layer delivery. Public documentation on specific API rate limits, pagination ceilings, or include-depth limits remains absent, and the platform lacks the transparent rate-limit posture seen in purpose-built headless APIs.

Jahia's primary development languages are Java (OSGi modules) and JavaScript/TypeScript (React, first-class in JavaScript Modules). The javascript-modules-library ships .d.ts typings for backend methods, but there are no official content-delivery SDKs for Python, Ruby, .NET, PHP, Swift, or Android — the ecosystem is oriented toward platform extension rather than headless content consumption. Apollo Client is recommended for GraphQL but is a community library, not an official Jahia SDK.

Jahia offers StackConnect (powered by Workato) with 400+ no-code connectors covering Salesforce, Microsoft Dynamics, Marketo, Mailchimp, and more, with ongoing 2026 connector expansions. The Jahia Store provides DAM modules (Cloudinary and Keepeek only), analytics (Google Analytics, Adobe Analytics), and Commerce Factory for ecommerce. Marketplace UX is less curated than modern headless platforms. Note: a Bynder integration exists but is developed externally by Gladtek and is NOT available in the Jahia Store.

Jahia's OSGi module system supports hot deployment of extensions without platform downtime, covering custom UI extensions (30+ documented hooks), custom GraphQL schema via SDL, custom JAX-RS REST endpoints, and server-side hooks. JavaScript Modules add a JS/React extension path (now considered stable) requiring no Java, with full Java/OSGi interoperability, plus an OSGi authentication service; Spring usage is deprecated in favor of OSGi declarative services. Dual Java + JavaScript extension paths give Jahia one of the broader extensibility profiles among traditional DXPs.

Jahia supports SAML 2.0 and OIDC-based SSO, with configurable password policies and SHA-256 + PBKDF2 password hashing. 8.2.3 introduces an OSGi authentication service, and the User Password Authentication — MFA module (2026) adds customizable MFA flows with GraphQL-driven secure login. SSO tier-gating details remain unclear from public sources.

Jahia uses a node-level ACL permission system where permissions attach to JCR nodes, supporting content-instance-level access control and custom roles. A deep-dive permissions doc covers granular actions (read, write, delete, publish), and Content Editor supports per-field permissions. The system is powerful but the JCR-heritage complexity prevents a higher tier.

Jahia holds ISO 27001:2022 certification (company-wide scope including dev teams), is GDPR compliant, HIPAA compliant (Coalfire assessment against the HIPAA Security Rule), and PCI DSS SAQ A 3.2.1 compliant. EU data residency is available via OVH. No SOC 2 Type 2 is publicly listed as of mid-2026 — a noted gap for North American enterprise buyers — which holds the score below the 80+ tier.

CVE Details records historical vulnerabilities including XSS in older versions. Jahia operates an ISO 27001:2022 ISMS with frequent cloud penetration tests, proactive third-party CVE remediation (e.g., snakeyaml upgrade in 8.1.9 for CVE-2025-52999), and a responsible-disclosure process via [email protected] plus Open Bug Bounty. The absence of a formal HackerOne/Bugcrowd bounty program caps this below 70.

Jahia supports both Jahia Cloud (managed SaaS on AWS and OVH) and self-hosted/on-premise deployment via Docker, with private cloud explicitly supported for regulated industries. Dual-mode flexibility positions Jahia well for data sovereignty needs, and Docker-based deployment enables consistent infrastructure-as-code patterns.

Jahia Cloud advertises a 99.9% base SLA per calendar month with fully redundant, dedicated software stacks, and SLAs up to 99.99% for enterprise tiers. SLA is measured via synthetic probes running every minute against Jahia, Augmented Search, and jCustomer. The public status page (status.jahia.com) reports 2026 uptime broadly meeting the SLA; self-hosted deployments have no vendor SLA, and 99.99% tier and incident-response SLA details are not fully public.

Jahia Cloud uses AWS and OVH with 300+ edge locations, auto-scaling Docker clusters that expand in under five minutes (triggered when average CPU exceeds 80% for five minutes), and clustered HA configurations with load balancers and multiple browsing nodes. It is built to span from standalone low-traffic instances to massive platforms with geo-data redundancy and high SLAs. Blue-green deployments via the Provisioning API enable zero-downtime releases.

Jahia Cloud automates backups, restores, and migrations across regions, with multi-datacenter replication and zero-downtime blue-green deployments. Specific public RTO/RPO targets remain absent from documentation and the trust center. Self-hosted deployments rely on customer-implemented DR. Automation is solid but the missing RTO/RPO commitments limit the score.

The @jahia/create-module CLI scaffolds projects with a pre-configured docker-compose.yml, letting developers spin up a full local Jahia runtime without a manual Java/OSGi install (npm/yarn create @jahia/module). Node.js plus yarn dev provides hot-deploy for JS/React modules, with Vite as the default bundler. Provisioning API + Terraform enable reproducible environments. Still more involved than emulator-style headless local dev, but the CLI-first Docker workflow is a genuine step-change.

Jahia's Provisioning API enables fully automated CI/CD workflows including environment creation, scaling, and blue-green upgrades. Docker images + Provisioning API together make Jahia compatible with Terraform, GitOps, and standard CI/CD tooling; the @jahia/create-module CLI ships GitHub Actions workflows out of the box. Jahia Cloud supports dev/staging/prod separation. Schema migration tooling is less mature than purpose-built headless platforms.

Jahia Academy provides comprehensive documentation segmented by persona (developer, sysadmin, end user) with GraphQL examples, module development guides, and get-started tutorials, plus an in-product GraphQL Playground. 8.2 added JavaScript/React developer guides (introduction to JavaScript modules, island architecture, under-the-hood). Some sections still reflect Java-heavy legacy material, capping the score below 80.

Jahia's JavaScript Modules (now considered stable) use a TypeScript + Vite build pipeline with React 19.x rendered server-side, and the javascript-modules-library provides .d.ts typings for the backend methods exposed by the Java OSGi bundle. There is still no auto-generated TypeScript type system from the JCR content model comparable to GraphQL codegen on headless platforms — TypeScript coverage sits at the component/presentation layer, not typed content delivery.

Jahia sustained a steady release cadence through 2025 into 2026: 8.2.0 (Jul 2025) added JDK 17 and merged Content Editor/jContent into jContent 3.0 with Page Builder; 8.2.1/8.2.2 (Jul–Aug 2025) and 8.2.3 brought Page Builder to production parity with legacy Page Composer plus JS Modules engine and CKEditor 5; 8.1.9 (Mar 2026) delivered security maintenance. Augmented Search 4.0 (Nov 2025) moved to Elasticsearch 9 and 4.1 (Apr 2026) added indexing improvements. Solid feature-plus-maintenance rhythm for a hybrid DXP, but still trails SaaS-native peers shipping weekly.

Jahia publishes structured per-version release notes at academy.jahia.com with dedicated 'What's New' and 'Customer Center' sections. Release notes distinguish feature improvements from security fixes, and Augmented Search 4.0 explicitly flagged breaking changes. Adequate, but no per-item migration guides or codemod tooling found.

Jahia publishes monthly product update posts summarizing recently shipped features, which provides some direction. No public community voting portal (Canny, GitHub Discussions) or structured long-range roadmap was found. Communication is retrospective marketing rather than forward-looking community transparency.

Portlets deprecated since Jahia 8.0 were fully removed in 8.2.0/8.1.9 with prior notice, and JDK 8 support was dropped in 8.2.0 alongside JDK 17 addition — indicating a working deprecation process. Augmented Search 4.0/4.1 shipped with documented breaking changes and upgrade notes. Parallel maintenance branches (8.1.x, 8.2.x) provided, but no evidence of 12-month deprecation windows or automated migration tooling.

Jahia is a niche, EU-centric platform with roughly 68 employees. No significant GitHub star counts on core repositories; community is largely contained to Jahia Academy and a private forum. Stack Overflow presence is sparse and the platform lacks the open-source community gravity of Drupal or even Magnolia.

Jahia Academy serves as the primary community hub with documentation, training, and a customer center. GitHub activity is present across 476 repos but engagement is modest, and no active Discord or Slack community was found. The academy model supports existing customers but does not attract broad developer participation.

Jahia operates a formal tiered partner program (Silver, Gold, Diamond) with a publicly accessible find-a-partner directory; the vendor cites 800+ trained partners though independent trackers list a smaller named set (~47 technology/channel partners, Salesforce the largest). Strong for the company's size, but most partners are EU/French-market-focused, limiting delivery coverage for non-EU enterprise buyers.

Third-party content ecosystem is thin. Tutorials, YouTube videos, and conference talks predominantly exist in French-language EU markets, with no significant Udemy/Pluralsight courses found. Limited English-language developer blog content beyond Jahia's own blog reduces learning accessibility for non-EU buyers.

Jahia developer skills remain primarily concentrated in EU/French-speaking markets and LinkedIn job postings mentioning Jahia are rare globally. The Jahia 8.2 JavaScript Modules path (React/TypeScript/Node.js) modestly broadens the addressable talent pool by removing the Java/OSGi barrier for frontend work, but the shift is nascent and the hire-ready talent pool remains small. Certification available via Jahia Academy with free open tutorials.

Jahia claims 1000+ organizations across 195 countries with a 96% retention rate, and expanded its cloud footprint with a new Asia-Pacific region in 2025–2026; independent tech-detection shows ~346 verified companies actively running Jahia. Long-term anchors include the European Parliament (since 2004), Ben & Jerry's, ISO, Sodexo, and Aviva France, with ongoing case studies (Netsmart, Socomec). Retention and product investment are healthy, but the absence of notable 2025–2026 new-logo announcements caps expansion signal.

Jahia's last known funding was a $22.5M growth equity round from Invus in February 2015 — over 11 years ago with no subsequent rounds. Estimated 2025 revenue $7.6–9.5M with ~68 employees and no reported layoffs; the company is stable and self-sustaining but shows no growth-capital investment. Recent CEO transition to Michael Tupanjanin executed without disruption.

Jahia is not listed in the 2024 or 2025 Gartner Magic Quadrant for DXP, nor the Forrester Wave: Digital Experience Platforms Q4 2025 — dropping out of top-tier analyst evaluations vs. its 2018–2019 Gartner MQ inclusion. Retains Gartner Peer Insights presence. Open-source Java/JCR DXP positioning with EU privacy focus is clear but niche; without current analyst placement, enterprise procurement credibility is weakened.

Jahia holds 603 G2 reviews — a substantial count for a Tier 3 Traditional DXP — with continued positive sentiment on flexibility, scalability, and modular architecture. Capterra and Gartner Peer Insights corroborate a stable, flexible platform with good day-to-day performance. Recurring criticism centers on initial complexity and learning curve; no major pricing or reliability scandal signals surfaced.

Jahia's first-party pricing remains sales-gated — jahia.com routes to a contact/quote form for both jContent and jEnterprise with no published figures. Third-party aggregators (Capterra, G2, GetApp, Techimply) surface indicative ranges (~€1,700/mo jContent, ~€3,000/mo jEnterprise; ~$1,800–$5,000/mo in USD), but partial visibility via review sites does not substitute for first-party transparency, so the score stays below the ~60 industry norm for public-lower-tier pricing.

Jahia uses tiered subscription pricing that varies by deployment (cloud vs. on-prem), environment count and support level — not per-API-call or bandwidth metering, which avoids the worst unpredictability. 2026 aggregator data confirms monthly subscription availability, and vendor material describes tier movement only when audience consistently exceeds plan capacity. The multi-variable negotiated model still makes budgeting harder than a flat SaaS list price.

SSO, user directories and roles/permissions are bundled into the base jContent tier — a positive differentiator versus DXP peers that gate SSO behind Enterprise. However, personalization, A/B testing, jCustomer CDP, consent management and the rules engine remain locked to jEnterprise, roughly doubling entry price for marketing-centric DXP buyers. Gating scope is defensible but the price step is steep.

2026 aggregator profiles confirm a monthly subscription option in addition to annual terms — a meaningful improvement over pure annual-only enterprise contracts. However, no published startup program, nonprofit pricing, self-service checkout or exit-provision documentation was found; all above-community deals go through direct sales negotiation. Improved from prior LOW-visibility scoring but still below the 50 threshold.

Jahia Community Edition is a permanent, downloadable, open-source release under GPLv3 with core CMS capabilities on a standard Tomcat + JDBC stack, and Docker images are published on the Academy. GPLv3 copyleft is a real restriction for commercial SaaS products built on top of it, and self-hosting still carries meaningful Java operational overhead relative to a fully-managed free SaaS tier. Solid entry point but not friction-free.

Jahia 8.2 JavaScript Modules are now GA-stable ('considered stable... no breaking changes coming in the foreseeable future'): `npm init @jahia/module@latest` scaffolds a TypeScript + React + Vite project shipping a docker-compose.yml that spins up a local Jahia instance, and GraalVM is no longer required (JS modules run on plain OpenJDK), removing prior local-runtime friction. A frontend developer can reach a working site within a dev session without Java/OSGi knowledge. It stays below the sub-hour bracket because the multi-GB Jahia EE Docker image, Node 22+/Yarn 4 prerequisites, and JCR content-model learning still gate first render, and backend extensions still require Java/OSGi.

The JS Modules path accelerates frontend delivery relative to pre-8.2 Java/OSGi builds, but full jEnterprise deployments still involve JCR content modeling, personalization/jCustomer setup, and integration work that community sentiment consistently describes as multi-month with a steep learning curve. Jahia's professional-services packaging (architecture, implementation, performance) implies non-trivial effort is expected, keeping the item below the mid-band for a traditional DXP.

With Jahia 8.2, the frontend profile shifts from 'Java/OSGi/Maven specialist' toward a standard TypeScript + React developer who can build views without JVM knowledge, broadening the talent pool. Backend extensions, custom workflows and deep JCR customization still require Java/OSGi specialists whose contract rates carry a real premium given the small community, and reviewers note Jahia-specific expertise is limited and commands a premium above generalist developers.

Jahia supports both Managed Cloud (SaaS) and self-hosted (Community or on-prem Enterprise) deployments. Cloud pricing (~€1,700+/month) bundles infrastructure but starts high relative to headless CMS peers. Self-hosted Community Edition adds server, database, CDN and backup provisioning. Comparable to other dual-mode traditional DXPs.

Managed Cloud reduces day-to-day infrastructure ops but customers still need Jahia platform expertise for module lifecycle, upgrades and configuration. Self-hosted deployments require JVM tuning, Tomcat administration, database ops and Java application monitoring — effectively a dedicated ops function familiar with the Java stack. Above the minimum operational burden for a traditional DXP.

The GPLv3 Community Edition and JCR (JSR-283) content storage provide meaningful data portability — content can be exported via standard JCR APIs and the underlying storage is documented. However, Jahia's proprietary module ecosystem, view templating, and jCustomer personalization data structures create real re-platforming effort. Exiting jEnterprise typically means rebuilding personalization, workflow and integration logic on a new stack. Better than fully proprietary DXPs but not easy.

Jahia 8.2's JavaScript Modules make React TSX a native server-side templating language with an Island Architecture (SSR + selective hydration) that maps to mainstream component mental models, and the framework is now marked stable (no breaking changes foreseeable per the javascript-modules repo, mid-2026). Developers still must internalize JCR node-type modeling (CND files), Jahia's content-centric page composition, and the module-engine rendering pipeline — an OSGi→JCR→modules→templates stack with no close analogue in modern JS/headless dev, per G2/Gartner. Legacy OSGi/Java remains for backend extensions but is no longer required for the primary view-building path, so it sits mid-band rather than lower.

Jahia Academy provides a dedicated 'front-end developer' getting-started track (intro + dev-environment setup) plus a 'Getting Started with JavaScript Modules' training course and full JS/React/Vite module documentation, alongside existing certification paths. Reviewer feedback (G2, Gartner 2025) still notes docs lack depth in advanced integration scenarios, and there is no interactive in-app onboarding tour. Sits in the 'adequate docs without interactive onboarding' band rather than the 65+ structured-interactive tier.

The primary frontend path is a mainstream Node.js stack — React 19.x TSX, TypeScript, Vite (official @jahia/vite-plugin), Yarn, CSS modules, server-side GraphQL — and the framework is now marked stable (mid-2026), removing the earlier immaturity discount. This is a genuine step change from the Java + Maven + OSGi profile. Module APIs remain Jahia-specific (server components, hydration primitives, JCR-backed data fetching) and backend extensions still require Java/OSGi, so it lands on par with mid-tier Traditional DXPs (Bloomreach 54.3, Magnolia 54.3 at category level) rather than pure headless CMSes.

The official `create @jahia/module` CLI has been revamped to offer multiple starter templates (TypeScript, Vite, React) with GitHub Actions CI/CD out of the box, and Luxe (github.com/Jahia/luxe-jahia-demo) is a maintained monorepo reference — views/templates, island architecture, GraphQL + JCR queries, a Storybook design system, and docker-compose. Luxe's README states it 'is not meant to be consumed as a tutorial,' so it is a production blueprint rather than a Next.js-style deploy-button starter, and the CLI templates are still pre-1.0. Better than pure Java/OSGi archetypes but short of first-tier headless CMS starters.

The CLI-generated docker-compose.yml removes the need to install Java, Tomcat, or a database locally for the dev environment, and module metadata/build are managed through standard package.json + Vite config. Production and advanced module configuration still use OSGi .cfg key-value files, and self-hosted deployments remain among the most config-heavy in the dataset — JVM + Tomcat + DB, plus multi-node clustering and HAProxy. A meaningful improvement over the fully-manual JVM+Tomcat+DB setup but still above a SaaS headless CMS's low-config bar.

Content types are still defined as JCR node type definitions (CND files) inside modules. Modifying a deployed content type against live content carries migration risk with no first-party schema diff/migration tooling — confirmed unchanged by the JS Modules path, since Luxe still ships CND-based node type definitions. Better than field-count-limited SaaS CMSes but riskier than platforms with explicit migration workflows; unchanged from prior scoring.

jContent provides in-context preview and draft mode for pages rendered by JavaScript Modules (SSR path — the same code renders in the editor and at runtime), which is a genuine strength. Fully headless consumers (e.g. external Next.js frontends hitting the GraphQL API) still need to implement custom preview endpoints against the draft GraphQL API — there is no plug-and-play preview SDK equivalent to Contentful/Sanity. Unchanged: good for the coupled/JS-Modules workflow, moderate for pure headless.

On the JavaScript Modules path, generalist TypeScript/React developers can build views, components, and content-driven pages without Java or OSGi knowledge — vendor docs and blog state you can start 'without knowing Java, JSP,' and independent coverage confirms JS modules 'require no knowledge of Java.' Academy tutorials are open/free; certifications remain optional. Java + OSGi expertise is still required for backend extensions and advanced customization, and although the framework is now stable, Jahia-specific talent is a small pool relative to mainstream React, so it lands at the low end of the no-certification band.

The CLI-generated docker-compose environment and JS-Modules path let a small frontend team (2–3 people) build and iterate without a dedicated Java specialist for view work, and Jahia Cloud reduces ops burden. Production still typically involves a solution architect for JCR schema design, a Java developer for backend extensions/integrations, and DevOps for self-hosted deployments — TrustRadius/G2 still describe months-long enterprise implementations with professional services. A modest team-size improvement over the pure Java/OSGi baseline but not a solo-developer platform.

jContent provides a usable WYSIWYG experience for editors to create pages, manage content, and publish routine changes without developer involvement — a genuine strength relative to lower-scoring DXPs. New content types, templates, layouts, and personalization rules still require developer effort (now JS Module code plus CND definitions rather than pure Java). The ongoing developer-dependency profile is essentially unchanged from prior scoring.

Jahia Cloud upgrades are vendor-managed, but self-hosted 8.2 upgrades carry multiple breaking changes: JDK 8 dropped (JDK 17 required), Hibernate removed from the public API, JSON override files consolidated from two to one, content types moved out of the default module to legacy-default-components, and a new provisioning-API permission with no migration script requiring manual setup. 8.2.2 further added enforced secured file uploads and removed session auth for /modules/api/bundles. The mixed hosting model tempers the worst of this, but self-hosted customers face real, recurring upgrade complexity.

Jahia publishes SBOMs and VEX files for vulnerability transparency and dedicates maintenance releases specifically to security (e.g., 8.1.8 in February 2025; 8.2.2 hardened file uploads and bundle auth). Cloud customers receive vendor-managed patches with no action required. Self-hosted customers must apply patches manually, but Jahia's advisory cadence and security documentation are reasonably mature for a mid-tier vendor.

Jahia has a pattern of significant forced migrations: JDK 8 dropped in 8.2 forced a JVM upgrade across all self-hosted deployments, and Augmented Search 4.0 (November 2025) forced an Elasticsearch 7→9 migration driven by Elastic Cloud's early-2026 EOL for v7. The jCustomer 2.x / jExperience 3.x prerequisites for 8.2 add further forced dependency bumps. Migration guides are provided, but the frequency of mandatory infrastructure-level changes is elevated.

Self-hosted Jahia carries a substantial dependency stack: JDK (now 17+), Elasticsearch (now v9), a relational database, Jackrabbit JCR storage, Tomcat, and optional jCustomer/jExperience add-ons; clustered cloud infra adds MariaDB, GlusterFS, and HAProxy. Major version upgrades to core dependencies have been forced in recent releases. Cloud deployment removes this burden entirely, but the dual-mode nature means a significant portion of customers manage complex dependency trees.

Jahia Cloud offers Datadog-based monitoring with custom Jahia dashboards covering application health and optimization signals, a synthetic /ping.jsp test each minute, and alerting when immediate attention is needed. Jahia 8.1.8 added dedicated instance health probes. Self-hosted deployments require customers to configure their own monitoring stack, and even for cloud deployments permanent monitoring is described as mandatory, so some application-layer effort remains.

Jahia provides content workflow and versioning features, but there is no specific evidence of automated content hygiene tooling such as orphan detection, broken-reference alerts, or content expiry dashboards. G2 reviews note that changes to data structures after content creation can be painful, suggesting content governance relies substantially on editorial discipline. Standard for a traditional Java DXP of this tier.

Jahia Cloud includes CDN, auto-scaling, and Datadog performance dashboards — substantially reducing the performance management burden for cloud customers. Self-hosted deployments require active tuning of caching, Elasticsearch indexing, Jackrabbit clustering, and JVM memory. Managed cloud infrastructure pushes the score up from the self-hosted baseline, but the significant self-hosted install base keeps the average moderate.

G2 (487+ reviews) and Capterra reviews consistently praise Jahia support as responsive, knowledgeable, and attentive through both sales and implementation cycles, with reviewers noting the team goes beyond initial tickets. A published Maintenance and Support Policy provides SLA clarity, and Jahia's relatively small customer base means enterprise accounts receive genuine attention. Scores are held from 70+ by the absence of evidence on mid-tier plan SLA quality versus enterprise-only access.

Jahia Academy hosts community forums and documentation, but the community is small relative to tier-1 platforms and reviewers describe low community momentum and a narrow talent pool. No evidence of a highly active public Slack or Discord with strong team participation, and reviewers note documentation gaps and scattered technical docs that require vendor contact to resolve. Response rates in community channels appear adequate but not fast by modern standards.

Jahia ships dedicated security and maintenance updates on a reasonable cadence (8.1.8 Feb 2025, 8.1.9, 8.2.2, and 8.2.3 in the March 2026 product updates), indicating active development. As a smaller vendor, critical patches appear to ship within weeks rather than immediately, and no significant backlog complaints appear in reviews, but resolution speed is not exceptional.

Page Builder reached full feature parity with the legacy Page Composer in March 2026 and is now Jahia's recommended editor for all new projects. Drag-and-drop, pre-built customizable templates, dynamic template inheritance, and inline editing allow marketers to create and publish landing pages without developer involvement. CKEditor 5 with optional AI-assisted writing is integrated.

Marketing Factory (up to v1.9) is a dedicated campaign management add-on covering A/B testing, campaign goal setting, conversion tracking, data-driven optimization, and publish lifecycle — all without IT involvement. Lacks a visual content calendar but covers campaign coordination and performance monitoring.

Jahia ships built-in SEO capabilities with no plugin required: clean URLs, vanity URL management, Google-compatible 301 redirect management, automated sitemap.xml generation (per-language), robots.txt configuration, and full HTML metadata management including Open Graph tags. Comprehensive native SEO coverage.

Marketing Factory provides native A/B testing, conversion tracking, goal monitoring, and CTA optimization. Form handling and lead capture are supported. UTM parameter awareness and deep lead routing to CRM/MAP still require StackConnect integrations. Good for a traditional DXP but not a full-stack performance marketing suite.

Jahia's jExperience product (built on Apache Unomi open-source CDP) provides native behavioral segmentation, geo-targeting, session-based and profile-based personalization, and real-time content targeting without requiring a separate CDP. GDPR-compliant by design. March 2026 added personalization dashboards and default variant visibility directly in Page Builder (purple color coding for jExperience elements).

Marketing Factory provides full A/B testing for pages, content components, and campaign elements. March 2026 added dedicated A/B testing dashboards and inline variant visibility in Page Builder (color-coded). Statistical reporting and winner selection are supported. This is genuine integrated experimentation, not just a third-party connection.

Page Builder supports template cloning, inline editing, drag-and-drop, and content reordering. jContent 3.4 (September 2025) added a rewritten side-by-side translation interface accessible from Page Builder. Publication dashboard is accessible directly from Page Builder. Some manual steps remain for complex multi-step approval workflows but general content velocity is solid.

Jahia supports headless API delivery (GraphQL and REST) enabling content to be delivered to web and headless frontends. Marketing Factory can target personalization across headless channels. Native email, social, SMS, or push notification channels require external tools via StackConnect. Primarily web-first with API-based headless delivery.

Marketing Factory includes built-in analytics dashboards for campaign performance, A/B testing results, and personalization engagement. Standard integrations with Google Analytics (GA4), Matomo, and AT Internet (Xiti) are confirmed. Page-level content performance and decay metrics require external analytics tools — CMS-embedded dashboards focus on campaign and personalization.

Site Factory model enables brand template governance — shared templates and locked component palettes enforced at the platform level. Standardized page models prevent off-brand layouts. Enforcement relies on workflow governance rather than automated guardrails; a determined author could still deviate. Good for a traditional DXP.

Jahia's SEO module handles OG and Twitter card meta tag management natively, ensuring proper social media preview cards. Social scheduling or push-to-social workflows require external integration via StackConnect. UGC embeds are possible via custom development or third-party widgets. Solid OG management but no native social scheduling.

Jahia includes a built-in media library (jContent) with image metadata, format control, and automatic standardized file naming. CloudImage integration reduces delivery sizes up to 75%. Dedicated DAM connectors for Cloudinary and Keepeek are available on the Jahia Store. A Bynder integration exists as a third-party build by Gladtek but is not available in the Jahia Store. Not a full native enterprise DAM but solid integration story with transforms and tagging.

Jahia has strong multilingual support — per-language sitemaps, locale-specific campaign variants via Marketing Factory, and a rewritten side-by-side translation interface (jContent 3.4, Sept 2025) accessible from Page Builder. GDPR compliance (cookie consent) is handled natively via Unomi. Market-specific promotional scheduling is possible but requires configuration.

Jahia's StackConnect platform provides 1,000+ no-code connectors covering CRM (Salesforce), MAP (Marketo, Mailchimp, Pardot), Adobe Experience Cloud, and AWS. Marketing Factory provides event-triggered content optimization. Depth of data sync varies by connector — many are webhook-based rather than deep API federations.

Commerce Factory supports product catalog management, physical and downloadable product types, multi-image per SKU, content enrichment at PIM level or directly in Jahia, and ElasticSearch-powered catalog. Commerce Factory is a separate add-on originally announced in 2014 with no 2025-2026 product updates, indicating maintenance-mode status. Adequate but not purpose-built for commerce content depth.

Commerce Factory provides automated category and brand pages, automated faceting on all product categories, up-selling and cross-selling content management, advanced couponing, and promotional content scheduling. Genuine merchandising tooling, though in maintenance mode. Scores above the 'no native tooling' floor given confirmed cross-sell/upsell and automated category management.

Jahia's commerce-io positioning focuses on API-based integration with third-party commerce platforms. StackConnect provides connectors including SAP Commerce and Salesforce Commerce Cloud. GraphQL and REST APIs enable data federation. However, no UI-level product pickers or deep real-time sync with Shopify or commercetools is documented — integrations are primarily webhook/API-based.

Commerce Factory enables editorial content enrichment alongside product data. Marketers can embed product references within editorial pages, creating buying-guide-style content. Shop-the-look, shoppable content with inline purchase CTAs, and lookbook patterns are not first-class authoring features — they require custom component development.

Commerce Factory includes basic promotional content scheduling and cart-adjacent banner management. CMS-managed trust badges and upsell banners in cart pages are possible through Commerce Factory. However, injection into external commerce platform checkout flows (Shopify, commercetools) without commerce template changes is not documented.

No specific post-purchase content management features found in Jahia documentation. Order confirmation pages and delivery tracking are primarily managed within the commerce platform. Marketing Factory can trigger follow-up content via behavioral signals but post-purchase order-event integration requires custom implementation via StackConnect.

Jahia Portal Factory explicitly supports B2B portal use cases with account-based access control, customer-specific content delivery, role-based catalog visibility, and gated documentation. The intranet/portal architecture extends naturally to B2B commerce content. Quote-request flows and customer-specific pricing display require custom integration.

Jahia's Augmented Search 4.0 (released November 2025, powered by ElasticSearch 9) provides federated search with improved performance. Commerce Factory's automated category faceting enables content-product blended search. Search landing pages are manageable via Page Builder. A solid but not best-in-class implementation.

Commerce Factory supports promotional content scheduling, advanced couponing, and time-based activation. Marketing Factory adds behavioral targeting of promotional content by audience segment. Countdown timers and tiered pricing tables require custom component development.

Jahia's multi-site architecture supports multiple storefronts from a single instance — each with independent domains, templates, language settings, and regional content. Site Factory enables rapid new-storefront deployment. Cross-site content reuse via Local Site Manager reduces duplication. Some content duplication may occur for storefront-specific editorial.

Commerce Factory supports multiple images per SKU. CloudImage integration provides responsive image delivery with up to 75% size reduction. Cloudinary DAM connector adds advanced media capabilities. However, 360-degree views, AR/3D models, and native video-in-PDP are not documented as native Commerce Factory features.

No marketplace or multi-vendor seller content management features found in Jahia documentation. Commerce Factory manages a single-seller product catalog. Seller profiles, seller-contributed content, and content moderation at marketplace scale are not native capabilities.

Commerce Factory supports multi-lingual stores, catalogs, categories, and promotions, as well as multi-country (taxes, currencies, regional specifics). Jahia's core multilingual CMS extends to product content localization. Regulatory content can be managed per locale. Currency-aware content blocks require configuration.

Marketing Factory + Commerce Factory integration enables some commerce analytics: ML-driven product recommendations, behavioral marketing signals, and conversion goal tracking. However, direct revenue attribution to CMS content pages and content-assisted conversion funnels are not documented as out-of-the-box features.

Jahia provides node-level RBAC where roles assigned to a content node are inherited down the tree with configurable inheritance breaks. Fine-grained permissions, custom role creation, SSO integration, and 2FA are confirmed. Audience-based personalization for department/segment-level content visibility is native via jExperience. Strong intranet-grade access control.

Jahia supports content lifecycle workflows, approval chains, version history, and content taxonomy. The employee intranet solution explicitly supports HR documentation repositories and internal knowledge bases. Augmented Search 4.0 improves internal knowledge discoverability. Content expiry scheduling relies on workflow rather than automated archival.

Jahia has a dedicated Employee Intranet Software product and Portal Factory module with 200+ out-of-box modules, personalized content delivery by role/department, and HR self-service portals. However, native social features (likes, comments), employee directory, and dedicated mobile apps are not part of core — they require integrations or custom development.

Jahia's intranet solution supports company news feeds, departmental announcements, and audience-segmented content delivery via Marketing Factory personalization. Content can be targeted by department or role. Read receipts, mandatory-read workflows, and acknowledgment tracking are not documented as native features.

Basic employee directory pages are buildable via Jahia content modeling and Portal Factory. HR system integration is possible via StackConnect (Workday, BambooHR). However, native org chart visualization, manager hierarchy views, and skills/expertise profiles are not documented as out-of-box features. Requires custom development for a full directory experience.

Jahia's core CMS provides version control, approval workflows, and content lifecycle for document management. HR documentation repositories with approval chains are confirmed for intranet use. Mandatory acknowledgment tracking, automated review/expiry reminders, and formal policy management distinct from general content are not documented as native capabilities.

Portal Factory with role-based content delivery enables new-hire portals with department-specific content paths. Progressive content disclosure can be configured via Marketing Factory personalization rules. Structured onboarding journeys with task checklists, 30/60/90-day progressive disclosure, and HR-triggered enrollment are not documented as first-class features.

Augmented Search 4.0 (released November 2025, powered by ElasticSearch 9) provides federated search across Jahia CMS and connected systems with improved performance and reduced memory footprint. Faceted filtering and relevance tuning are confirmed. Cross-system search (SharePoint, Confluence) is possible via connectors but not native out-of-the-box.

Jahia intranet portals are responsive web applications — mobile access is available via browser. Headless GraphQL/REST APIs enable custom mobile app development. No native Jahia employee mobile app is documented. Push notifications and offline support require custom app development. Responsive web without native mobile is the current capability.

No native LMS or micro-learning features found in Jahia documentation. Learning content hosting is possible via general CMS capabilities. StackConnect may provide LMS connectors but no documented native integration with Cornerstone, Workday Learning, or similar is found. Portal Factory does not include learning-specific modules.

No native social layer confirmed for Jahia intranets. Comments, reactions, discussion forums, employee recognition, and polls are not documented as out-of-the-box Portal Factory capabilities. These features require custom development or third-party widget integration. The platform is content-delivery focused, not collaboration-focused.

StackConnect provides 1,000+ no-code integrations including workplace tools. Salesforce, Adobe, and AWS are explicitly listed. No explicit native Microsoft Teams or Slack connectors are documented. Basic webhook-based integration with workplace tools is achievable via StackConnect, but embedded content cards, bots, and deep Teams/Slack integration are not confirmed as native.

Jahia supports content workflow states, approval chains, version history, and content scheduling (time-based publishing). Publication dashboard in Page Builder provides lifecycle visibility. Automated date-based content expiry/archival and stale content flagging are not documented as native features — lifecycle management relies on workflow configuration.

Marketing Factory provides intranet analytics: personalization engagement data, content performance by audience segment, and failed-search analytics via Augmented Search. Google Analytics and Matomo integrations provide standard page view metrics. Department-level analytics exist within Marketing Factory reporting. Not a purpose-built intranet analytics tool but adequate.

Jahia's multi-tenant architecture provides database-level isolation per site/tenant. The PaaS offering enforces strict data segregation between tenants. Each virtual site has independent content models and API access, scaling from 1 to 1,000+ sites. Genuine multi-tenant isolation for a traditional DXP.

Jahia enables cross-site content reuse natively — content objects from one virtual site can be referenced in others via Local Site Manager. Shared templates, global design tokens, and reusable components are maintained centrally and consumed across brand instances. Site Factory enables component library propagation to new sites at creation time.

Jahia implements federated governance: centralized homepage approvals while regional teams manage local campaigns independently. Fine-grained role management, cross-site JBPM approval workflows, multilingual governance, and complete audit history are native. Well-suited for multi-brand enterprise governance with local team autonomy.

Jahia's PaaS/cloud model uses shared infrastructure for hosting multiple sites/tenants, potentially providing per-brand cost efficiency versus license duplication. Pricing is enterprise/custom with no public volume tier commitments. Asia-Pacific cloud region added in 2025-2026 expands geographic reach but not pricing transparency.

Site Factory model enables per-brand visual identity — each site instance can have its own theme tokens, CSS, typography, color palettes, and logo treatment while sharing underlying component structures. With Jahia 8.2 JavaScript Modules, per-brand styling can leverage CSS modules and React component theming; standardized page models enable brand-level customization with shared architecture. Not as strict as a formal design token API but solid for a traditional DXP.

Jahia supports per-brand multilingual governance through combined site isolation and workflow management. Translation workflows can be configured per site/brand. Marketing Factory provides locale-specific campaign variants per brand. Regional cookie consent (Unomi) and GDPR compliance are manageable per site.

Marketing Factory provides per-site analytics dashboards for each brand. Individual brand performance (campaign analytics, A/B testing, personalization engagement) is available per site. An aggregate cross-brand portfolio analytics dashboard with publishing cadence benchmarking or content velocity comparison across brands is not documented as a native feature.

Jahia supports independently configurable JBPM-based approval workflows per site/brand. Each brand can have its own review stages, approval chains, and scheduling policies while the central audit trail remains shared. Genuine per-brand workflow independence within a centrally auditable framework.

Local Site Manager enables corporate-to-brand content syndication — content from a central/corporate site can be referenced or shared across brand sites. Press releases, legal disclaimers, and product announcements can be managed at corporate level and consumed by child brands. Controlled override points for local adaptation exist but require configuration.

Jahia's Unomi-based CDP provides GDPR-compliant consent management and privacy settings configurable per site/brand. Regional cookie consent and privacy policies can be managed per brand instance. Per-region data residency settings are available in Jahia Cloud. No automated compliance guardrails preventing non-compliant publishing are documented — compliance is configuration-driven.

Site Factory maintains a central component library and site templates that propagate to new brand instances. The open-source Luxe reference project (github.com/Jahia/luxe-jahia-demo) demonstrates a React/TSX design system, content modeling, and island architecture blueprint under the Jahia 8.2 JavaScript Modules model. Component versioning and update propagation across existing tenants are possible but require coordinated deployments rather than an automated versioning system.

Jahia provides a centralized admin dashboard across all sites and brands with granular RBAC. Central administrators can manage all brands while brand teams retain autonomous local management. SSO and 2FA are supported centrally. Cross-brand contributor roles and cross-site permissions are configurable. Strong enterprise user management for multi-brand.

Jahia supports cross-site shared content types that each brand site can extend with local customizations via JCR content type inheritance. Site Factory enables deploying base content models to new brand sites. Per-brand extension of shared content types without forking requires careful JCR configuration and is not a documented first-class authoring feature.

Per-brand analytics are available via Marketing Factory dashboards for each site. An executive portfolio dashboard aggregating content freshness, publishing SLA adherence, cost allocation per tenant, and capacity planning across all brands is not documented as a native feature. Manual aggregation from per-site reports would be required for portfolio-level insights.

Jahia offers native GDPR data-subject-rights tooling out-of-the-box — right of access, right to be forgotten, and data anonymization are handled without custom development or third-party tools, per jahia.com/solutions/security-and-compliance. Consent management is built into forms, social logins, and behavioral tracking; jExperience/jCustomer Privacy Manager gives visitors self-service profile access/deletion; Jahia authored Apache Unomi (the OASIS CDP reference implementation) as a privacy-by-design engine. Combined with EU/Swiss residency (AWS Ireland, AWS Switzerland, OVH France) and a dated public sub-processor list (2025-03-27, 12 vendors with per-vendor customer-data flags), Jahia has a strong EU posture. Held below 85 because a public DPA template or SCC text is not published — only Cloud T&Cs, Privacy Policy, and a security@ contact are publicly available.

Jahia completed a HIPAA Security Rule compliance assessment by Coalfire Inc. with a 100% score on the auditor's scorecard, and the Certificate of Completion is published publicly — a stronger signal than most tier-3 DXPs offer. However, per the scoring guidance and 2026-07 trust-center verification, no Business Associate Agreement (BAA) offering is publicly documented; the prompt reserves 70+ for platforms with an explicit BAA. Score sits in the mid-configurable-support band: solid HIPAA posture demonstrated by an independent assessment, but the contractual instrument covered entities require is absent.

Jahia covers GDPR (EU) with native data-subject-rights tooling, PCI DSS SAQ A 3.2.1 with yearly evaluations (the narrowest PCI scope, for merchants using third-party processors), and the Coalfire HIPAA Security Rule assessment. Product materials also reference CCPA support via the same right-to-erasure/anonymization tooling. Missing: FedRAMP, IRAP, C5, ENS, HITRUST, UK GDPR/IDTA, PIPEDA, LGPD. Score reflects GDPR + CCPA + lightweight PCI + HIPAA-assessed coverage without broader regional-framework depth — respectable for a tier-3 Swiss/French vendor but well short of federal/APAC-ready peers.

No SOC 2 Type 1 or Type 2 attestation is listed on Jahia's trust center or referenced in any Jahia security material. Verified absent as of 2026-07. Jahia's assurance stack is ISO 27001-centric (European approach) rather than SOC 2-centric; the gap is material for North American enterprise procurement where SOC 2 Type 2 is typically required, and there is no evidence Jahia is pursuing SOC 2.

Jahia holds a current ISO/IEC 27001:2022 certification (AFNOR certificate N° 2022/101121.3, COFRAC-accredited, valid 2025-09-06 through 2028-09-05). Scope covers Jahia Solutions Group SA as a 'Web Content Management and Digital Experience Software Editor' across Geneva (HQ), Paris, and Lyon — including product development, cloud, IT, support, professional services, legal, HR, and administration, which is broader than infrastructure-only certifications from many peers. Statement of Applicability v4.0 dated 2025-02-25. Held below 80 because no ISO 27018 (cloud PII processing) is documented.

Beyond ISO 27001:2022, Jahia holds PCI DSS SAQ A 3.2.1 with yearly evaluation, the Coalfire HIPAA Security Rule assessment (100% scorecard, certificate published), and has completed the AWS Foundational Technical Review (FTR) as an AWS partner. PCI + HIPAA-assessed are meaningful for regulated industries; AWS FTR is a modest partner-program assurance signal, not a security certification. Verified absent 2026-07: CSA STAR (Level 1 or 2), FedRAMP, IRAP, ENS, C5, Cyber Essentials Plus, HITRUST. Score sits in the mid-band appropriate for two meaningful additions on top of ISO 27001.

Jahia's sub-processor list confirms five hosting regions — AWS USA, AWS Ireland, AWS Switzerland, OVH France, and OVH Canada — giving buyers EU vs. US choice plus two genuinely sovereign EU options (OVH France, AWS Switzerland). Each Jahia Cloud customer receives dedicated single-tenant infrastructure (no multi-tenancy), which is unusual for a SaaS DXP and materially simplifies isolation. Jahia is also available fully self-hosted or in private-cloud deployments, giving regulated buyers complete data-plane control. The sub-processor table's per-vendor customer-data flags are an above-average transparency practice. Held below 78 because no APAC production region is documented and contractual residency guarantees are not published in primary materials.

Native right-to-erasure and data anonymization are built into the platform per jahia.com/solutions/security-and-compliance, requiring no custom development or third-party tools. The jExperience/jCustomer Privacy Manager gives visitors self-service profile access, anonymization, and deletion; admin-managed consent policies are documented on academy.jahia.com. Apache Unomi (Jahia-authored, OASIS CDP reference implementation) provides API-based profile deletion, anonymization, and data portability. Comprehensive content export options are documented: XML/ZIP from page and content folders, an 'Export content to CSV' module, HTTP POST to an export servlet for automation, and Groovy-scripted scheduled exports. Held below 75 because a documented post-termination retention period for Jahia Cloud is not published (though dedicated single-tenant infrastructure simplifies data destruction).

Contrary to prior scoring, audit logging is well documented. jContent content history records content operations including deletions with user, date, type of action, and affected property (accessible via 'Advanced Options → History' in the Content Editor). A native jahia_contenthistory database table stores content-change entries with configurable purging. Jahia 8.2 added an OSGi service listening to login, logout, and download events, extending audit coverage to access events. Native JCR 2.0 versioning provides rollback and version comparison. Datadog live log access is bundled with all Cloud plans, with logs indexed in USA and EU per the sub-processor list. Held below 70 because native SIEM push connectors are not documented (Datadog can forward, but that's a customer-side configuration), and per-tenant configurable log retention is not surfaced beyond database-table purging.

Jahia's own blog acknowledges the authoring UI is only 'approaching' ATAG conformance rather than certifying it, and no formal WCAG 2.1 AA or ATAG 2.0 conformance report has been published for the Content Editor / jContent authoring surface. The CKEditor Accessibility Checker and built-in WCAG rich-text validation help authors produce accessible output (Part B of ATAG) but are not evidence of authoring-UI conformance (Part A). The dedicated /accessibility page returns 404, and no keyboard-navigation or screen-reader statement is published. Small bump above prior 30 for the ATAG-approaching self-assessment but still low.

No VPAT, ACR, Section 508 conformance statement, or ATAG 2.0 formal assessment has been located for Jahia. The dedicated accessibility page (jahia.com/accessibility) returns 404, and no accessibility statement exists in the trust center or legal index. This absence blocks procurement by US federal agencies and many state/regulated public-sector buyers. Verified absent as of 2026-07.

Jahia AI (jahia.com/ai-powered-enterprise-cms) ships a first-party AI Content Creation offering in which agents generate copy, metadata, and translations 'within editorial rules,' with in-editor generation via the CKEditor 5 AI Assistant. Every AI output is routed through Jahia's existing approval workflows, giving implicit brand/compliance guardrails without dedicated brand-voice controls or prompt-template libraries. Held below the 70+ tier by the lack of native brand-voice/tone tooling and reliance on CKEditor for the actual editor UX.

Jahia AI's migration flow rebuilds alt text (alongside SEO metadata and Schema.org structured data) during automated CMS migration, indicating some AI-driven alt-text generation exists in the migration agent pipeline. No native AI image generation (DALL-E/Firefly/Stable Diffusion), no smart focal point, no AI-tagging in DAM (Keepeek/Cloudinary connectors are storage integrations, not AI media tooling), and no alt-text-on-upload for day-to-day authoring were found in official sources. Score reflects marginal media AI confined to migration.

Three converging AI translation pathways: (1) Jahia AI agents perform bulk multilingual translation across large content sets as a first-party feature; (2) native DeepL integration in the Jahia Store for in-context page translation with workflow review; (3) CKEditor 5 AI Assistant provides instant translation inside the editor. Bulk cross-locale operations, workflow integration, and multiple pathways justify a score at the top of the mid-tier band. Still lacks explicit brand-voice preservation metrics or MT quality-scoring dashboards, keeping it below 70+.

Jahia AI ships a named SEO/GEO capability that performs automated meta description generation, SEO audits across the full page catalog, and Generative Engine Optimization (GEO) for visibility in ChatGPT/Perplexity — plus AI-driven taxonomy tagging. The migration agent rebuilds SEO metadata and Schema.org structured data at scale. Held below the 70+ tier because on-page SEO scoring dashboards for editor-time optimization were not explicitly documented.

Jahia AI's core positioning is exactly this dimension: agents handle 'tasks that content teams repeat at scale: bulk updates, SEO audits, multilingual translation, metadata generation, taxonomy tagging, and compliance checks,' with every action running through existing workflows and audit trails. Multiple AI automations are woven into the editorial surface (activation from CKEditor 5, workflow triggers, permission-aware, journal-logged). Held below 70 because smart scheduling and duplicate detection were not explicitly named.

Jahia AI is a named, GA agentic product with 18 specialized agents that operate simultaneously for migration and content operations (bulk updates, SEO audits, translations, metadata, taxonomy, compliance). Agents are governed via Jahia's existing approval workflows — natural approval gates within agentic runs — and every operation is journaled. The MCP server (see 10.4.1) opens the door to external agents (Claude, Cursor, Copilot) driving multi-step workflows in natural language. Below the Contentstack Agent OS tier because a named agent marketplace and public catalog of pre-built agent recipes were not surfaced.

Jahia AI agents 'read signals and surface optimizations' and produce full metadata/compliance/content audit reports across sites, adding a real AI insight layer on top of jExperience/jCustomer (Apache Unomi) behavioral analytics. jExperience continues to provide A/B and personalization dashboards (updated March 2026). Still no AI-driven content gap analysis, topic clustering, or dedicated stale-content detection dashboards — the AI operates on audit-style flows rather than editorial insight dashboards.

Jahia AI performs 'metadata, compliance, and full content audits across all sites in minutes, with a report for the team' — a first-party AI audit capability. Compliance-focused auditing is called out explicitly alongside content operations. Sits in the mid-tier because brand-voice compliance scoring, dedicated accessibility scanning, and duplicate/thin content detection were not confirmed as first-party features.

Augmented Search continues to run on Elasticsearch 7.17.x per current documentation, with the Elasticsearch 9 LLM/vector integration still flagged as 'evaluating' in Jahia's March 2026 update. No production vector search, NL query, or RAG-ready embedding pipeline was found. The MCP server (see 10.4.1) does expose GraphQL content to external LLM agents — a functional RAG-adjacent path — but that is agent-driven retrieval, not native semantic search.

jExperience personalization remains rules-based (segmentation, A/B tests, session/profile targeting via Apache Unomi) with no shipped ML decisioning engine. Jahia AI's 'personalization' capability generates personalized content variants and journeys, but execution is served by the traditional rules engine — the archived unomi-predictionio-plugin has not been superseded by a first-party ML personalization product. Reflects rule-based personalization with modest AI assist in variant generation, still below the ML-engine bar.

Official Jahia MCP server (github.com/Jahia/jahia-mcp-community-server) is an OSGi bundle exposing Jahia's GraphQL API over stateless MCP JSON-RPC 2.0 with full read/write/publish: introspectSchema, executeGraphQL, listSkills, getSkill; API-token auth with graphql + community-mcp scopes; per-user JCR permission enforcement; an admin UI (Administration → MCP Server) to whitelist permitted operations; blocked-operation logging. Referenced on ai-powered-enterprise-cms as accessible to Claude, Cursor, GitHub Copilot, or custom agents. Sits at the top of the 50-70 band — the 'community' framing and GraphQL-passthrough (vs. a bespoke commercial MCP product) keep it below the top-tier Contentful/Hygraph/Storyblok bar.

Jahia AI explicitly positions itself as model-agnostic: 'No model is locked in; organizations can connect the LLMs, API keys, and infrastructure that fit their needs, then assign each task to the right model.' Eight supported LLM models across OpenAI, Anthropic, Google, Mistral, DeepSeek, plus self-hosted/own-infra options; teams can 'switch models by updating an API key — no contract renegotiation,' and can deploy on their own infrastructure for data residency. A first-tier BYOK product with multi-provider choice and residency controls.

Developer surface for AI has three concrete pieces: the official MCP server exposing full GraphQL introspection/execution as agent tools; a Skills system storing reusable Markdown-based agent prompts/instructions in JCR (listSkills/getSkill); and JavaScript/TypeScript module development (since Jahia 8.2) usable for AI-integrated components. Content is delivered via GraphQL (well-suited for LLM context) and REST. Above the standard-API tier because MCP + Skills + agent-ready GraphQL constitute purpose-built AI developer tooling, though official LangChain/LlamaIndex integration guides and a branded AI SDK are not yet published.

Jahia routes every AI operation through the same governance layer as human editors: 'AI-generated content follows the exact same approval path as content written by a team member — including sign-off steps, notifications, and compliance checks. All Jahia governance rules (approvals, access controls, audit trails) apply to every agent operation.' MCP operations enforce JCR permissions per authenticated user and are constrained by an operation whitelist with blocked-operation logging. Every AI action lands in the activity journal. In the 50-70 band because hallucination detection, IP indemnification, and prompt-template governance were not surfaced as branded features.

Every AI operation is journaled and appears in Jahia's activity trail, and the MCP server logs blocked operations with user/path/client IP — providing basic per-user AI usage visibility. However, no dedicated AI usage dashboard, LLM token/cost tracking, per-model consumption metrics, or quality-trend analytics were found in official sources. Because BYOK routes AI calls to customer-owned model endpoints, token/cost telemetry naturally lives at the model provider rather than in Jahia. Reflects basic activity logging without purpose-built AI observability.