My main use case for Acquia Digital Experience Platform (DXP) is enterprise web services to support multiple countries, including UK, France, Germany, and the USA.

A specific example of how I'm using Acquia Digital Experience Platform (DXP) for these enterprise web services is that the goal was to migrate from a ccTLD model to a gTLD model to support multiple countries where previously there was only one website. In addition to that, it was also to embed a PIM and a DAM, which we also did.

The best features Acquia Digital Experience Platform (DXP) offers in my experience were the synergy with the PIM and the DAM that appealed. The integration there was the main thing for me. Again, from my point of view, I was more about strategy as opposed to implementation.

The integration between the PIM and DAM worked for my organization by creating an ecosystem where you plug the data into the PIM and it's syndicated across Acquia Digital Experience Platform (DXP). It was almost having one entry populate the various repositories that makes a global approach simple.

Acquia Digital Experience Platform (DXP) has positively impacted my organization by improving speed to market. Opening up a new country allowed us to put the content together very rapidly.

The speed to market improved significantly in that it would have taken a good three months to get going previously. With Acquia Digital Experience Platform (DXP), I would say that was reduced down to six to eight weeks.

One area where Acquia Digital Experience Platform (DXP) can be improved is the cost structure, as it's quite an expensive solution for what it is.

In my experience, Acquia Digital Experience Platform (DXP) is stable.

Overall, customer support with Acquia Digital Experience Platform (DXP) was positive; we received rapid responses to queries and account management support as well.

I would rate the customer support on a scale of one to ten as a nine.

Positive

Before Acquia Digital Experience Platform (DXP), I previously used a very simple WordPress solution, and I needed something more dynamic and enterprise-based.

My experience with pricing, setup cost, and licensing was pretty seamless. It was all clear, it was very transparent, and we signed up to a three-year deal.

Before choosing Acquia Digital Experience Platform (DXP), we did evaluate other options, including Optimizely.

Regarding my main use case with Acquia Digital Experience Platform (DXP), the only issue around migration was a technical error which was admitted, and that was the SSL certificates weren't managed effectively, so some of the sites weren't live and they couldn't migrate with ease. They weren't a seamless transition, but it was quickly detected.

My advice to others looking into using Acquia Digital Experience Platform (DXP) is that if you want something that has a simple, seamless, feature-rich solution, Acquia Digital Experience Platform (DXP) would be it. I actually delegated the decision making to my team and that was their decision.

The usual use case is for the customer to have a centralized way to manage their websites. We manage multiple websites, sometimes with different types, plus some customers also have products they want to showcase. We manage these websites using Acquia DXP.

Acquia DXP offers the tools to make it easier to maintain, manage, and deploy websites in a centralized way for multiple channels.

The features of DXP that are most valuable include Acquia Site Factory, which allows for the management and creation of websites, offering a UI for managing the process of creating and deploying the websites. Additionally, Content Hub provides a centralized way to manage content.

There are areas where Acquia DXP could be improved. For example, in Site Factory, the provisioning of environments can take time. You often need more environments than what's available by default, which requires going through support and sales processes. Having more stacks available by default would be beneficial. With Content Hub, there are issues with certain types of design and content incorporation, so more flexibility is needed.

We have been using DXP from 2020 to 2024.

There are not many issues, and Acquia uses a mailing list to communicate when there are problems. They also provide a status page to check the availability of solutions. They communicate about platform maintenance, and typically there is no action needed on our side.

Acquia DXP has high scalability because it is built on AWS. It allows you to scale the solution according to your needs. You can configure some aspects yourself on the cloud platform, and for specific needs, you might need to go through support.

The support is normal, offering standard SLAs. When creating critical issues, a follow-up is needed on your side. Sometimes there are difficulties when dealing with critical issues due to the lack of a 24/7 available team. However, they are responsive and provide guidance.

Neutral

The initial setup is not the easiest stack to set up initially. That said, it is well documented. For an experienced developer, the setup would be relatively straightforward and rated as a nine.

For anyone evaluating this solution, it's important to have senior developers and senior people working with it, as junior developers may struggle with the setup. Having the right people on board is essential for enterprise projects. 

I'd rate the solution nine out of ten.