Quick Summary & Main Answer

Main Answer: Liferay Experience Cloud (LXC) is a fully managed cloud platform that deploys portal instances in a SaaS model, relying on Client Extensions for customizations.

Audience: Cloud architects, IT directors, and systems administrators.

Applicable Use Cases: Deploying secure customer portals on managed infrastructure, migrating local portals to SaaS, and automating DevOps workflows.

LXC PaaS vs. SaaS: Deployment Blueprints
LiferayX Category Reference Guide cover illustration for LXC PaaS vs. SaaS: Deployment Blueprints.
LXC Mode Deploy Restrictions Best Use Case
LXC SaaS Client Extensions only, no OSGi Low maintenance portals, seamless platform upgrades
LXC PaaS Custom OSGi bundles permitted Complex legacy portal migrations with deep Java customizations

LXC SaaS Features

LXC SaaS is Liferay's fully managed software offering. Liferay hosts the system, maintains uptime, and applies monthly service pack updates. Since customizations are limited to Client Extensions, upgrades are automatic.

LXC PaaS Controls

LXC PaaS gives you dedicated containers. You compile code inside Liferay's cloud environment, letting you run legacy OSGi modules, but you are responsible for testing platform upgrades.

Cloud Deployment Pipelines

Deploy to Liferay Experience Cloud using automated build pipelines. Code committed to GitHub trigger cloud compilations, creating containers and publishing packages with zero downtime.

Frequently Asked Questions

Does LXC SaaS allow custom Java code?

No. LXC SaaS restricts customizations to Client Extensions, keeping the core clean and upgrading automatically.

Is CDN caching included in Liferay Cloud?

Yes. Liferay Experience Cloud includes built-in Fastly CDN caching rules out-of-the-box.

Cloud LXC PaaS SaaS
Portrait of Ankita Varani

Written by Ankita Varani

Ankita Varani is a certified Liferay Solutions Architect with 12+ years of experience in enterprise portal migrations and decoupled system designs.