If you only know Liferay as portal software, you will take a second look at this release. With 2026 Q2, Liferay is heading in a direction that goes far beyond feature lists.
In the enterprise software world, quarterly releases sometimes have a reputation for being mainly changelog documents: new settings here, an improved UI there, a few more API endpoints. Liferay 2026 Q2.0 is different. If you read the release notes carefully, you 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 am interested not only in what was delivered, but why it was delivered. That is the angle from which I want to look at 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: prospects can try out the new headless CMS without a purchase decision, without a sales conversation, and without negotiation.
That sounds simple, but it is a fundamental change in go-to-market. Classic enterprise software has traditionally had high barriers to entry: demos, quotes, long evaluation processes. Product-led growth turns this around. The product itself does the work of initial persuasion. Anyone who tries out the headless CMS for free and understands what it can do is already halfway convinced by the time of the upgrade conversation.
For partners like us, this means: we can now introduce customers to Liferay with a low threshold, without a licensing decision being on the table right away. This changes how we conduct initial conversations and how we set up proofs of concept. Of course, the Free Tier has limits: number of structures, fields, stored content. But these very limits have been set wisely. They give enough room for understanding, but not so much that productive use without an enterprise license would make sense.
2. Cloud native: Liferay is serious about AWS
If you have followed enterprise software decisions over the past few years, you know the pattern: every vendor talks about cloud, cloud native, Kubernetes-ready. The question is always what that means in concrete terms.
Liferay answers this with this release on two levels. First: a new AWS deployment toolkit that builds on Amazon EKS and provides customers with a complete, preconfigured infrastructure for Liferay in AWS. Second: the OpenSearch 2 Connector is leaving beta and reaching GA status.
Together, these two things are more than the sum of their parts. The AWS toolkit solves a real problem: running Liferay in AWS used to be laborious, 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 second 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. For customers who rely on AWS, this is practical: they can use AWS OpenSearch Service and thus significantly reduce the operational effort 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 everyone 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 it is that sales staff can create branded deal portals directly from within Liferay. Documents, presentations, and multimedia assets can be shared in these rooms. Buyers get structured, secure access. And sellers see in an engagement dashboard who viewed which documents and when.
That sounds like sales enablement software, and that is exactly what it is. Liferay is entering a market here in which vendors such as Seismic, Highspot, or Showpad are active. That is no coincidence.
Many Liferay customers operate B2B portals: partner portals, customer portals, dealer portals. In these contexts, the actual deal process often runs in parallel in email threads and shared Dropbox folders, because there is no good digital tool that sits close enough to the portal platform. Digital Sales Rooms is Liferay's answer to this. Whether it works in practice as promised will have to be shown by the GA version. But the direction is clear: Liferay wants to be not only the platform on which portals run, but also the tool with which real business is done in these portals.
CMS platform maturity: the details that make the difference
In addition to the three major strategic shifts, this release includes a number of CMS improvements that will make the biggest difference in day-to-day work.
Editable Content Structures
Until now, editing a content structure after its first publication was risky or even impossible. Anyone who wanted to add or reorder fields first had to delete existing content. From now on, administrators can adjust structures and their fields after the fact without affecting existing entries. That sounds obvious, but it was a real pain point with growing content models.
Bulk Search & Replace
Content teams can now replace text, URLs, or terms platform-wide in a single step. With a mandatory preview before the commit, automatic versioning, and a rollback option. Anyone who has ever coordinated a corporate rebranding across a Liferay-based web presence knows what this means.
Referenceable Entries: from document to data model
With the new “Link Content Fields”, content can build relationships to other entries instead of retyping values over and over. An author, a product category, or a location is maintained once and referenced everywhere. If the entry changes, the change carries through to all dependent content. This is the step from a document-centric CMS to a real content graph.
CKEditor 5 becomes the standard
CKEditor 4 is deprecated. CKEditor 5 is now the default editor in Liferay DXP. This was long overdue: CKEditor 4 was technically outdated and increasingly caused 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 is the right one.
Operational maturity: what is getting better behind the scenes
Two features in this release fall somewhat outside the pattern of the big announcements, but deserve special mention.
The site-level maintenance mode makes it possible to take individual sites offline for visitors while administrators continue working and can check the state. Visitors receive a clean 503 page, which signals to search engines that the shutdown is temporary. For deployments and larger migrations, this is a real gain in operational quality.
The improved Publications review experience is the second operational highlight: content pages now show in a diff view exactly what has changed before a publication is approved. Anyone working in teams that map content approval processes via Publications will appreciate this immediately.
Breaking changes: a sign of healthy platform hygiene
A word on the breaking changes in this release, because they are characteristic of a platform that is seriously modernizing.
In 2026 Q2, Liferay has, among other things, removed all PrevAndNext methods from Service Builder. That sounds dry, but it was a measure that eliminated more than 600,000 lines of generated code that were used in three places in the code. Decisions like this are not made out of convenience, but because the technical debt becomes too high.
The same applies to the cleanup of duplicated utility classes between portal-kernel and the Petra libraries, and to the simplification of the indexer implementations. These are not glamorous features. But a platform that consistently reduces technical debt is more reliable in the long term, faster to upgrade, and easier to extend.
Liferay's statement “Don´t use Service Builder - use Objects” still stands.
For development teams that maintain Liferay projects: the breaking changes are well documented, and the migration paths are described concretely in the release notes. They should be worked through before every upgrade to 2026 Q2.
Conclusion: where Liferay is heading
Liferay 2026 Q2 is not a release that should be summarized with a bullet-point list. These are three direction-setting decisions that are becoming visible all at once.
First: Liferay wants to be easy to try out. The Free Tier is the answer to a world in which purchasing decisions are increasingly driven by first-hand experience with the product, not by sales conversations.
Second: Liferay wants to be a first-class citizen in the cloud. The AWS toolkit and the OpenSearch GA status are no coincidence, but part of a consistent cloud-native strategy.
Third: Liferay wants to be not only the platform on which B2B portals run, but the tool with which real business is done in these portals. Digital Sales Rooms is the first concrete step in this direction.
If Liferay is part of your strategy or you are evaluating it, you should not read this release as a routine update. This is where the course is being set.
If you want to assess this for your company or implement it concretely – we at Portalworks are happy to help, whether with strategy, architecture, or implementation.
If you want to go deeper: in the coming weeks, we will publish a multi-part series here in which we examine the individual topics in detail – from the new CMS to Digital Sales Rooms to the breaking changes.
