Anyone who knows Liferay only as portal software will take a second look at this release. With 2026 Q2, Liferay is charting a course that goes far beyond feature lists.
In the enterprise software world, quarterly releases sometimes have a reputation for being little more than changelog documents: new settings here, an improved UI there, a few more API endpoints. That’s not the case with Liferay 2026 Q2.0. Anyone who reads the release notes closely will recognize three strategic decisions behind them that will define the platform in the coming years.
As an expert who works with Liferay projects every day, I’m interested not only in what was delivered, but why it was delivered. That’s the angle from which I’d like to view this release.
1. Product-Led Growth: Liferay Opens the Door
With the new CMS Free Tier, Liferay is doing something remarkable for a classic enterprise product: prospective customers can try out the new headless CMS without a purchase decision, without a sales pitch, and without negotiations.
That sounds simple, but it’s a fundamental shift in go-to-market strategy. Traditional enterprise software typically has high barriers to entry: demos, proposals, lengthy evaluation processes. Product-Led Growth flips that on its head. The product itself does the work of initial persuasion. Anyone who tries the Headless CMS for free and understands what it can do is already halfway convinced by the time the upgrade discussion comes up.
For partners like us, this means: We can now introduce customers to Liferay with a low barrier to entry, without an immediate licensing decision hanging in the air. This changes how we conduct initial meetings and how we set up proof-of-concepts. Of course, there are limits in the Free Tier: number of structures, fields, and stored content. But these limits are set wisely. They provide enough leeway to understand the platform, but not so much that productive use without an Enterprise license would make sense.
2. Cloud Native: Liferay is serious about AWS
Anyone who has followed enterprise software decisions in recent years is familiar with the pattern: every provider talks about the cloud, cloud-native, and Kubernetes-ready. The question is always what that actually means.
Liferay answers this with this release on two levels. First: A new AWS deployment toolkit built on Amazon EKS that provides customers with a complete, preconfigured infrastructure for Liferay on AWS. Second: The OpenSearch 2 Connector is out of beta and has reached GA status.
Together, these two things are more than the sum of their parts. The AWS toolkit solves a real problem: running Liferay on AWS used to be complex, error-prone, and required deep Kubernetes knowledge. With the new toolkit, there is standardization, better visibility into the EKS cluster, and a more reliable deployment pipeline.
The OpenSearch Connector is the other half of the story. For a long time, Elasticsearch was the only serious search option for Liferay in production. OpenSearch, the AWS-maintained fork, is now a full-fledged alternative with GA status. This is practical for customers who rely on AWS: they can use the AWS OpenSearch Service, thereby significantly reducing the operational overhead for the search infrastructure.
Taken together, Liferay is signaling: We want to be a first-class citizen in the AWS world. This is relevant for anyone who runs Liferay in the cloud or wants to migrate there.
3. Digital Sales Rooms: A New Playing Field
The most surprising feature in this release is still in beta, but it deserves special attention: Digital Sales Rooms.
The idea behind this is that sales reps can create branded deal portals directly from within Liferay. In these rooms, documents, presentations, and multimedia assets can be shared. Buyers get structured, secure access. And sellers can see in an engagement dashboard who viewed which documents and when.
That sounds like sales enablement software, and that’s exactly what it is. Liferay is entering a market where providers like Seismic, Highspot, and Showpad are active. That’s no coincidence.
Many Liferay customers operate B2B portals: partner portals, customer portals, and reseller portals. In these contexts, the actual deal process often runs in parallel via email threads and shared Dropbox folders because there isn’t a good digital tool that integrates closely enough with the portal platform. Digital Sales Rooms is Liferay’s answer to this. Whether it works in practice as promised remains to be seen in the GA version. But the direction is clear: Liferay wants to be not only the platform on which portals run, but also the tool used to conduct real business within these portals.
CMS Platform Maturity: The Details That Make the Difference
In addition to these three major strategic shifts, this release includes a number of CMS improvements that will make the biggest difference in day-to-day use.
Editable Content Structures
Until now, editing a content structure after initial publication was risky or even impossible. Anyone who wanted to add or reorder fields had to delete existing content first. From now on, administrators can modify structures and their fields retroactively without affecting existing entries. This may sound obvious, but it has been a real pain point for growing content models until now.
Bulk Search & Replace
Content teams can now replace text, URLs, or terms across the entire platform in a single step. With a mandatory preview before committing, automatic versioning, and a rollback option. Anyone who has ever coordinated a corporate rebranding via a Liferay-based website knows what this means.
Referenceable Entries: From Document to Data Model
With the new "Link Content Fields," content can establish relationships with other entries instead of retyping values over and over again. An author, a product category, or a location is maintained once and referenced everywhere. If the entry changes, the change propagates through all dependent content. This is the step from a document-centric CMS to a true content graph.
CKEditor 5 Becomes the Default
CKEditor 4 is deprecated. CKEditor 5 is now the default editor in Liferay DXP. This was long overdue: CKEditor 4 was technically outdated and was causing increasing problems with modern browser features. For customers with custom plugins in CKEditor 4, there is a migration path and a temporary feature flag that reactivates CK4. But the switch is inevitable, and it’s the right move.
Operational Maturity: What’s Improving Behind the Scenes
Two features in this release fall somewhat outside the scope of the major announcements but deserve special mention.
Site-Level Maintenance Mode allows individual sites to be taken offline for visitors while administrators can continue working and checking the status. Visitors see a clean 503 page, which signals to search engines that the outage is temporary. For deployments and major migrations, this is a real quality improvement in operations.
The improved Publications review experience is the second operational highlight: Content Pages now show exactly what has changed in a diff view before a publication is approved. Anyone working in teams that use Publications to manage content approval processes will immediately appreciate this.
Breaking Changes: A Sign of Healthy Platform Hygiene
A word about the breaking changes in this release, as they are characteristic of a platform that is seriously modernizing.
Among other things, Liferay removed all PrevAndNext methods from the Service Builder in Q2 2026. That sounds dry, but it was a measure that eliminated over 600,000 lines of generated code that were used in three places in the codebase. Such decisions aren’t made out of convenience, but because technical debt becomes too high.
The same applies to the cleanup of duplicate utility classes between the portal-kernel and the Petra libraries, and to the simplification of the indexer implementations. These aren’t glamorous features. But a platform that consistently reduces technical debt is more reliable in the long run, faster to upgrade, and easier to extend.
Liferay’s statement: “Don’t use Service Builder—use Objects” remains in effect.
For development teams managing Liferay projects: The breaking changes are well documented, and the migration paths are clearly described in the release notes. This should be reviewed before any upgrade to 2026 Q2.
Conclusion: Where Liferay is headed
Liferay 2026 Q2 is not a release that should be summarized with a bullet-point list. There are three strategic decisions that become apparent at once.
First: Liferay wants to be easy to try out. The Free Tier is the answer to a world where purchasing decisions are increasingly driven by personal experience with the product, not by sales pitches.
Second: Liferay wants to be a first-class citizen in the cloud. The AWS toolkit and OpenSearch’s GA status are no coincidence, but part of a consistent cloud-native strategy.
Third: Liferay wants to be not just the platform on which B2B portals run, but the tool used to conduct real business within these portals. Digital Sales Rooms is the first concrete step in this direction.
Anyone who has Liferay in their strategy or is evaluating it should not view this release as a routine update. This sets the course.
If you want to assess this for your company or implement it concretely—we at Portalworks are happy to help, whether it’s strategy, architecture, or implementation.
For those who want to dive deeper: In the coming weeks, we’ll be publishing a multi-part series here, in which we’ll examine the individual topics—from the new CMS to Digital Sales Rooms to the breaking changes—in detail.
