Liferay DXP Cloud Native Experience

Commercial digital experience, content management and digital asset platform deployed into customer cloud infrastructure with Liferay's Cloud Native Experience toolkit.

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Provider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment

  2. Operated by

    Your team

    Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodProvider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment
InfrastructureServers / containers
Provider-ready CNE provisions managed Kubernetes and supporting stateful services in the customer's cloud. Liferay runs as persistent workloads managed through Helm and Argo CD.
Licensing modelCommercial Only
This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key.
LicenseCommercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 6 documented · 6 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

CNE licensing refers to Liferay Marketplace add-ons, not a provider billing offer. A current cloud Marketplace offer for the selected CNE Enterprise path was not established.

Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

DXP Enterprise activation and add-on delivery do not establish cloud-provider Marketplace commitment treatment.

Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The DXP compatibility matrix documents SAML 2.0 and OIDC provider standards. Match the IdP and certified runtime components to the actual DXP release used by CNE.

Self-hosted DXP identity compatibility; reviewed 2025.Q2 matrix · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

DXP SCIM was introduced behind a flag in 2024.Q1, moved to a release flag in 2024.Q4 and became GA in 2025.Q1. Verify the deployed release and supported RFC operations; it does not implement arbitrary vendor schema extensions.

DXP subscription/version-specific provisioning · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed Liferay DXP Cloud Native Experience material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The CNE deployment requires controlled GitOps access, cloud credentials and activation keys. Configure secrets, network boundaries and the certified identity/runtime components rather than treating cloud provisioning as hardening.

AWS Ready deployment access and secrets · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

CNE documents offline activation bundles for AWS/GCP Ready, but Azure Ready 0.3.0 lacks the required Marketplace volume. This establishes offline licensing for selected paths; complete dependency mirroring, updates and integrations still need validation.

Path/version-specific offline licensing, not unconditional air-gap support · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

CNE Kubernetes Ready supplies the liferay-default Helm chart; supporting Kubernetes, database, search and object storage are customer-managed. This complements provider-specific Ready automation. Pin a chart compatible with the chosen DXP release.

Official Helm artifact for customer Kubernetes · Source ↗ · Deployment artifact ↗ (master (moving branch; select a compatible chart/image release)) · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The Kubernetes Ready Small tier uses two Liferay replicas, each requesting 2 CPU/12 GiB (limits 4 CPU/16 GiB), 20 GiB PVC per pod, an HA database, three search nodes and object storage. It targets up to 500 concurrent users but requires workload load testing.

Kubernetes Ready Small production starting tier; AWS Ready infrastructure defaults may differ · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key.

Liferay DXP Cloud Native Experience: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

The Small tier supplies app/search/HA-database starting requirements, but the complete provider bill of materials, DXP entitlement and measured content/search workload still need confirmation. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
Not confirmedEvidence and scope for Release snapshot / cadence

CNE supports DXP 2024.Q1+ and provider tooling has independent revisions. The complete latest supported DXP/chart/operator/provider-Ready combination and publication dates were not established.

Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Scope & considerations

Cloud Native Experience supports Liferay DXP 2024.Q1 and later. Provider architectures differ: AWS Ready integrates RDS, S3 and OpenSearch; Azure Ready uses AKS, Azure PostgreSQL Flexible Server, Blob Storage and Elasticsearch through ECK; GCP Ready uses GKE, Cloud SQL, Cloud Storage and ECK. The customer must provide cloud permissions, a Git repository, secret storage, compatible tools and a valid activation key. Starting with DXP 2026.Q1, all installations require an activation key.

Category fit

Content management & CMS
Liferay DXP provides web and headless content authoring, publishing, sites and digital-experience delivery on customer infrastructure.
Digital asset management
The DXP includes digital asset management for organizing and reusing documents and media; exact entitlement follows the selected subscription.

Compare within Content management & CMS

  • ApostropheCMSCustomer-operated content management and website application framework.
    • Heroku
    Customer-operated · Open Source / Open Core
  • Cockpit CMSSelf-hosted structured content and API management application.
    • Railway
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CrafterCMSSelf-hosted content authoring and delivery platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • Directus Self-HostedSelf-hosted content and data management with APIs over your SQL database.
    • Railway
    Customer-operated · Source Available
  • dotCMS Cloud AnywhereVendor-operated content platform deployed into a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • DrupalOpen-source content management system for building and operating websites.
    • AWS
    Customer-operated · Open Source / Open Core
  • Ghost Self-HostedOpen-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.
    • DigitalOcean
    • Linode
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Content management & CMS. These products address related workflows; read their category-fit notes before comparing scope. See all of Content management & CMS →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Liferay DXP Cloud Native Experience AWS Ready ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Liferay documents automated deployment in the customer's AWS account with EKS, RDS, S3 and OpenSearch. Enterprise Subscription entitlement and customer cloud permissions are required.

    • Liferay DXP Cloud Native Experience Azure Ready ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Azure subscription, including AKS and managed data services.

    • Liferay DXP Cloud Native Experience GCP Ready ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory