FAQ & Glossary

Liferay DXP (Digital Experience Platform) is a Java-based enterprise platform for building portals, intranets, customer self-service sites, and headless commerce experiences. It bundles identity management, content management, personalization, and an OSGi module system into one deployable runtime.

Liferay Portal Community Edition (CE) is the free, open-source core. Liferay DXP is the commercially licensed edition built on that same core, adding enterprise features such as analytics, advanced personalization, clustering support, SLA-backed support, and long-term release tracks — which is why most regulated enterprises run DXP rather than CE in production.

Yes, at its foundation. Liferay Portal CE is released under the LGPL license and is fully open source. Liferay DXP extends that open core with proprietary enterprise modules and commercial support, so it is source-available to licensees rather than fully open source.

OSGi (Open Services Gateway initiative) is the modular runtime Liferay DXP is built on. Each feature — themes, portlets, APIs, services — is packaged as an independently deployable bundle, which lets teams hot-deploy, version, and isolate customizations without restarting or destabilizing the whole platform.

It depends on customization depth and data volume, but a structured upgrade generally follows three phases: assessment & planning, schema upgrade & code refactor, and testing & go-live. Straightforward portals can move in a matter of weeks; heavily customized DXP 6.2-era platforms with custom OSGi bundles and legacy themes take longer and benefit from a phased, zero-downtime migration plan.

Yes. Liferay DXP exposes its content, users, and commerce data through REST and GraphQL headless APIs, so teams can keep Liferay as the system of record for content/identity while rendering the frontend in React or Next.js — decoupling the editorial experience from the presentation layer.

Java's mature tooling (Spring Boot, OSGi, JVM observability), strong backward compatibility, and proven concurrency model make it a dependable choice for systems that must run for a decade without a full rewrite — which is exactly the lifespan expected of core enterprise portals, banking systems, and healthcare platforms.

Microservices split a system into independently deployable services communicating over APIs or message brokers (e.g. Kafka), instead of one large monolith. Pairing this with Liferay lets the portal stay the stable experience layer while surrounding business logic — pricing engines, order management, AI agents — scales and deploys independently.

All three are enterprise DXPs, but Liferay is distinguished by its Java/OSGi foundation (deep backend customization without vendor lock-in), a genuinely open-source core, and first-class support for complex B2B portal use cases (partner, supplier, and customer self-service) alongside content management — where AEM leans content/marketing-first and Salesforce leans CRM-first.

MCP is an open protocol that lets AI models and agents securely call tools and query live data from external systems. In a Liferay context, an MCP server exposes DXP content, users, and workflows as callable tools, so an LLM-based agent can read or act on real portal data instead of hallucinating answers.

Yes. Through custom MCP servers and retrieval-augmented generation (RAG) over DXP content, Liferay can power AI assistants that answer questions from your actual knowledge base, automate workflows, and act as agents within DXP — with guardrails scoping exactly what the AI is permitted to read or change.

GEO is the practice of structuring a website — schema markup, clear entity facts, llms.txt, quotable statements — so that AI answer engines (ChatGPT, Perplexity, Google AI Overviews) can accurately parse, cite, and recommend it, the same way classic SEO optimizes for traditional search rankings.