Liferay Cloud Maintenance and Release Schedule
Liferay SaaS and PaaS both have weekly maintenance and release schedules. Liferay Cloud uses a transparent and predictable release cadence so you can rely on a stable and dependable infrastructure for your cloud projects.
Liferay DXP maintenance and Liferay Cloud Platform maintenance occur independently from one another.
Liferay DXP Maintenance Windows
Liferay SaaS instances have weekly DXP maintenance windows. The maintenance window depends on your deployment region and lasts 4 hours. These maintenance windows include updates to the instance’s database and Liferay DXP instance. One or two short downtimes are expected each week during this window. These maintenance windows cannot be changed or delayed per request.
Liferay strives to test updates in advance on a copy of customer databases to avoid issues and verify update quality. You should establish a predefined test plan with Liferay that covers important business use cases so these can be included when testing updates. If testing succeeds, the update applies to both production and non-production instances.
SaaS DXP Upgrade Scheduling
Liferay publishes quarterly DXP releases on a regular cadence, but SaaS environments are not upgraded automatically when a new quarterly release becomes available.
For example, a release such as 2026.Q1 becomes available in March, but SaaS environments may upgrade to that version later, based on internal rollout planning and project readiness.
SaaS DXP upgrades follow a managed process coordinated by Liferay. Internal upgrade campaigns are generally scheduled separately from quarterly release publication dates.
You can also request an upgrade at any time by opening a support ticket.
Recommended Upgrade Versions
Liferay typically recommends upgrading to the latest patch release instead of the initial .0 quarterly release.
For example, instead of upgrading directly to 2026.Q1.0, Liferay may recommend a later patch release such as 2026.Q1.5, which includes additional fixes and stability improvements.
Typical Upgrade Workflow
Requested upgrades generally follow this process:
-
Upgrade the preproduction environment.
-
Validate the upgrade and critical workflows.
-
Schedule and upgrade the production environment.
If necessary, Liferay may also recommend rebasing existing hotfixes during the upgrade process.
Unlike Liferay SaaS, maintaining and updating Liferay DXP in Liferay PaaS is the customer’s responsibility.
Liferay Cloud Platform Maintenance Windows
Updates you request for the Liferay Cloud platform occur in one of the weekly release windows: Tuesday and Thursday, from 8 AM to 8 PM PST. Any exceptions or updates outside these windows are communicated at least 14 days in advance.
Most scheduled releases are completed with no downtime or outage for customer applications or the Liferay Cloud interface. However, larger updates or changes can cause downtime.
For transparency, releases are categorized as Major, Minor, and Patch types. The risk of downtime for Liferay Cloud and customer systems varies by release type.
| Release Type | Liferay Cloud Console | Liferay Cloud API | Customer Applications |
|---|---|---|---|
| Patch | Low | Low | Low |
| Minor | Low | Low | Medium |
| Major | Medium | Medium | High |
Each type of update follows a regular maintenance schedule:
-
Patch updates are applied on an ad-hoc basis in any release window (Tuesdays or Thursdays, between 8 AM to 8 PM PST).
-
Minor releases are scheduled monthly (on the last Tuesday of the month).
-
Major releases are scheduled quarterly (on the last Tuesday of March, June, September, and December).
These release schedules apply to the Liferay Cloud platform itself and do not indicate when SaaS customer environments upgrade to a specific Liferay DXP quarterly release.
Emergency Maintenance Updates
If strictly necessary, Liferay can install critical zero-day security updates or emergency fixes for reliability at any time without prior notice. Liferay is committed to maintaining uptime for customer environments as a top priority when mitigating security or reliability issues.