nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Introducing the Alfresco Compatibility Matrix

angelborroy

One of the most common questions in the Alfresco ecosystem is simple:

Which version of ACS works with this version of Search?
Can I use this module with Java 21?
Which database or browser combinations are supported?
What versions of ACA, ADF, Share or Transform Service are compatible?

Historically, this information has been spread across documentation pages, release notes, support matrices and GitHub repositories. While official documentation already provides supported platform information for many products, navigating all those sources can sometimes be time-consuming.

To help simplify that experience, the community has created the Alfresco Compatibility Matrix.

What is the Alfresco Compatibility Matrix?

The Alfresco Compatibility Matrix is a community-driven web application that centralizes compatibility information across the Alfresco ecosystem in a single searchable interface.

The goal is straightforward:

Provide a quick way to validate version compatibility
Reduce deployment and upgrade uncertainty
Help developers, architects and administrators design supported stacks
Offer a cleaner navigation experience compared to manually checking multiple documentation pages

Simple and lightweight

The project follows the same philosophy as other community-driven initiatives from the AlfrescoLabs organization:

Static website
No backend infrastructure
Easy contribution model
GitHub-based collaboration
Fast iteration cycle

If you are already familiar with the Alfresco Addons Catalog, the overall approach will feel very familiar.

Open Source and community-driven

The full source code for the project is available on GitHub:

https://github.com/AlfrescoLabs/alfresco-compatibility-matrix

Contributions are highly encouraged.

If you notice missing compatibility information, outdated combinations, incorrect mappings or new platform support details, you can help improve the matrix by submitting issues or pull requests.

Try it now

You can explore the Alfresco Compatibility Matrix here:

https://alfrescolabs.github.io/alfresco-compatibility-matrix/

Feedback, ideas and contributions are welcome.

Hopefully this becomes another useful community resource that helps make Alfresco deployments and upgrades easier for everyone.

Find more posts tagged with

Alfresco Content Services

Comments

yuhei

Hello

Thank you, it is very easy and simple to read !

We are looking forward to having all versions included.

Do you know when this will be done for Enterprise versions 23.6 and 23.5?

Thank you !

lcolorado

Hi Angel,

That's much clearer, thank you!

However, I have to point out that the documentation for ACS 26.1 still shows Alfresco Search Services 2.0: Content Services 26.1 • Alfresco Supported Platforms • Reader • Product Documentation

That is a bit confusing. I know that in other places it has been mentioned that Alfresco Enterprise is moving away from Solr, but that page is still consulted by customers and us, and it's what pops up when we Google for "Alfresco supported platforms".

Perhaps that part of the documentation should be updated?

Thanks for your amazing work!

Luis

angelborroy

Hi, Luis.

This is what I see in the page you mentioned:

Do you feel it right?

Thanks

lcolorado

Hi Angel,

Thanks for replying! So, as it is, the documentation indicates that:

Alfresco/Hyland supports Search Services 2.0 for ACS 26.1,
...but ASE is recommended.

I just wanted to confirm that this is Hyland's actual support posture for ASS.

If ASS is not supported with ACS 26.1, I think it should not be listed on this page of the documentation.

Thanks!

Luis