Acquia Digital Experience Platform (DXP) Reviews

Our main use case for Acquia Digital Experience Platform (DXP) is hosting our Drupal projects, covering a range from Drupal 7 to Drupal 10 or even 11. We used it for hosting and ensuring that our services are available 24/7 all over the world.

We work with a rather big engineering company presented in about 50 countries with thousands of people in their workforce. We focused on their main marketing site that provides information on their services and products, which has been hosted on Acquia for quite a long time.

I should clarify that I probably was not using directly Acquia Digital Experience Platform (DXP) in the way it is marketed at the moment on Acquia's site, which seems to be a no-code, low-code solution. We have been hosting our own Drupal websites that were specifically built for Acquia platform hosting, and we have extensively used Acquia services, which were rather good in general. However, at some point, we had to shift to another platform.

At some point, the pricing was higher than what our customer was willing to pay for the quality of service at that moment.

Based on my experience with their services, Acquia Cloud that we have been using, or Acquia hosting, is next to a native solution for Drupal projects, making it probably one of the best hosting solutions available, even though it has its flaws and we eventually had to shift to another one.

What makes Acquia hosting next to native for Drupal projects is basically the ease of integration, as Acquia and Drupal are very densely interconnected.

Acquia Digital Experience Platform (DXP) has positively impacted my organization primarily by ensuring that our services based on Drupal were available 24/7 in all countries that are a priority for our customer. I believe they provided a really good service, with some exceptions.

We have had almost all the metrics in the dashboard to measure this positive impact, including how many visitors we have over time, how big the load is on the infrastructure, and how the whole thing works. We have been monitoring this.

The support usually worked quite well, but the problem that led us to shift to another platform was also in support, as the quality of service degraded at some point, which became a bit of a problem. Initially, we received really good support in various cases, but it became unsatisfying when we couldn't find clues on particular issues, repeating multiple times. That was the reason to move away at some point, or at least one of the reasons.

Our customer project had to be moved from Acquia Cloud to another service, which was dictated by multiple reasons, with one being the price and another being a degrading quality of service. I wish that this quality wasn't falling down and that we would continue the partnership.

I am talking mostly about Acquia Cloud and I am not quite sure if it overlaps with Acquia Digital Experience Platform (DXP) because when I see what is mentioned as DXP on Acquia's website, it seems to be a bit different kind of thing, reminding more of no-code, low-code solutions. For Drupal, I believe it is one of the best solutions you may have if you have a considerable contract with Acquia and you agree on the price.

We have been using Acquia services for quite a long, at least with the current project. The partnership started with Acquia long before I joined the project. So basically, it's been there for years.

Acquia Digital Experience Platform (DXP) is mostly stable most of the time.

I believe that Acquia Digital Experience Platform (DXP) has scalability that is quite good, maybe not perfect, but really quite good.

The customer support used to be good, but as I mentioned earlier, this was one of the problems we had with our project. Maybe it was just some temporary issues with the team, but we had problems with the support, and that was the reason to move to another platform.

For the projects that have been in Acquia, I believe it was initially built in Acquia, and we moved to another service. I have also been using other services that provide the same kind of service, usually requiring a bit more custom work on our side. Acquia itself is basically a kind of native solution for Drupal projects.

The project started before me, so I am not quite sure exactly what options were evaluated.

On a scale of 1 to 10, I would rate Acquia Digital Experience Platform (DXP) overall around eight, as I said before, as it is mostly about Acquia Cloud, not DXP as it is marketed at the moment. The results on our project affected the grade quite a lot, making it lower, but for a Drupal site, it is still a very good solution.

I choose the number eight because we had to move from this platform, which was something that convinced us to make that decision, and this is why I cannot say 10. Considering all other projects that succeeded on their platform, I believe that it is still a good solution, specifically for Drupal-based projects.

My overall rating for Acquia Digital Experience Platform (DXP) is 8 out of 10.

My main use case for Acquia Digital Experience Platform (DXP) includes code deployment using Acquia Cloud. I have used it for Acquia DAM to manage my assets and Site Studio to manage my multiple sites.

A specific example of how I used Acquia Cloud for deployment is that Acquia Cloud handles code deployment. We have dev, stage, and prod environments. To deploy properly from local, we deploy to dev, and then we manage it across these environments. In that way, we use the pipelines. It becomes quite easy when you use Acquia Cloud that way.

My main use cases with Acquia Digital Experience Platform (DXP) are DAM, Acquia Cloud, and Site Studio.

In my opinion, one of the best features Acquia Digital Experience Platform (DXP) offers is Site Studio. Because for every new site that I have to spin up, it uses the same governed components. It makes it faster, launches with zero brand drift, and editors never need a developer for day-to-day page building.

Site Studio helps my team launch sites faster because, for example, when I have a new site from the client that needs to be added as a sub-site into the main branch, I don't have to do much. I can use the existing base and speed up the process by using it. It makes it really easy for me to do that with Site Studio. Sometimes it can be a little tricky, but in my case, it makes the process a little bit faster.

Acquia Digital Experience Platform (DXP) has positively impacted my organization because it eased the process.

Acquia Digital Experience Platform (DXP) can be improved because sometimes it takes a lot of time. It needs a little bit of optimization. That is what I have faced some of the time, and that can be improved.

Regarding the needed improvements, I would say speed and page load time. Page load time is an area that can be improved.

There are other improvements I think Acquia Digital Experience Platform (DXP) needs. Regarding optimization, there is room for improvement. The UI can be improved at the end-user end as well.

I have been using Acquia Digital Experience Platform (DXP) for around three to four years.

Acquia Digital Experience Platform (DXP) is stable 90 to 95 percent of the time.

Acquia Digital Experience Platform (DXP) is scalable.

The customer support for Acquia Digital Experience Platform (DXP) is good. Most of the time they are really easy to approach. Sometimes it gets a little tricky.

I have not previously used a different solution because we are using Acquia for the time being. I was not a part of it when it was selected, so I cannot say much.

With Acquia Digital Experience Platform (DXP), I can say that it definitely saved time. With time, it saved our money.

Regarding my experience with pricing, setup cost, and licensing, I will say I don't have experience with that because I think the sales team and the higher-ups were mostly looking into it. I was not a part of it and joined much later.

Before choosing Acquia Digital Experience Platform (DXP), I evaluated other options because there were options, such as Pantheon and others. However, I think Acquia was a good choice, so we opted for that.

The advice I would give to others looking into using Acquia Digital Experience Platform (DXP) is that it's a positive experience. If you have large, enterprise-based websites, you can opt for it, and it will be a good purchase. However, if you have a very small site or a smaller solution, I don't think it's optimal given the price, as it's a little steeper. I would rate this product an 8 out of 10.

My main use case for Acquia Digital Experience Platform (DXP) is managing and delivering digital content across our institutional website and stakeholder-facing portals. On a day-to-day basis, I use it to publish and update placement-related information, employer engagement content, recruitment announcements, internship opportunities, communication, and student resources. The platform helps us maintain consistent content and improve user experience to ensure that students and recruiters have access to up-to-date information through our digital channels.

I also leverage its content management and personalization capabilities to better engage different stakeholder groups. A recent example of how I used Acquia Digital Experience Platform (DXP) is during our campus recruitment season. We used the platform to manage and publish placement-related content for students and recruiters, including company visit schedules, eligibility criteria, application deadlines, and event updates. One challenge was ensuring that information was updated quickly and consistently as recruitment schedules changed. Acquia Digital Experience Platform (DXP) helped us streamline content updates and maintain a single source of information across our digital channels, which reduced confusion among students and improved communication with recruiting organizations participating in the placement process.

Acquia Digital Experience Platform (DXP) is very useful software, and one thing that stands out is the platform's ability to support different stakeholder groups through a single content management environment. In our case, students, recruiters, faculty coordinators, and placement team members all need access to different types of information. Acquia Digital Experience Platform (DXP) helps us organize and deliver content more efficiently. Another benefit is the flexibility to make content updates quickly during high activity periods such as campus recruitment drives or internship seasons, keeping information current and reducing the manual effort required to coordinate communication across multiple channels. While we initially viewed it primarily as a content management solution, we found it valuable as a broader digital engagement platform that improved communication and overall user experience for our stakeholders.

Acquia Digital Experience Platform (DXP) features are truly great. First, the content management capabilities are very strong, making it easy for non-technical users to create, update, and publish content without relying heavily on IT teams. Second, I appreciate the platform's ability to deliver a consistent digital experience across different channels and audiences, which is particularly useful when communicating with diverse stakeholder groups such as students, recruiters, and faculty members. Another feature I value is the flexibility and scalability of the platform. As our content requirements evolve throughout the academic year, the platform supports changing needs without significant disruption. I also appreciate the workflow and governance capabilities that help ensure the content is reviewed and approved before publication, which is important when sharing time-sensitive information related to placements, internships, or recruitment activities. Overall, the combination of content management, personalization, governance, and scalability are the features that provide the most valuable support in our environment.

While Acquia Digital Experience Platform (DXP) works beautifully and provides an overall positive experience, there are areas where it could be improved. One area is the learning curve for some advanced features; while basic content management is straightforward, certain configuration and advanced functionality can require additional training or technical expertise. I would also appreciate seeing some administrative tasks and workflows simplified because making changes to more complex content structures can sometimes feel more involved than expected, particularly for business users who are not highly technical. Another opportunity for improvement is reporting and analytics; while the platform provides useful insights, having a more intuitive and customizable dashboard for business users would make it easier to track engagement and content performance without relying on additional tools.

A key point that has arisen within our team is the desire for more business user-friendly analytics and reporting features. While the available data is useful, having a more customizable dashboard and easier access to key engagement metrics would help non-technical users derive insights more quickly. We have also discussed making some advanced features easier to discover and configure since, while the platform is quite powerful, newer users may not always be aware of the capabilities available to them without additional training and support. Recently, as digital engagement expectations have grown, we have found ourselves looking for greater flexibility in personalization and audience segmentation. Although Acquia Digital Experience Platform (DXP) already provides strong capabilities in this area, continued enhancements would allow us to deliver even more targeted experiences to different stakeholder groups.

I have been using Acquia Digital Experience Platform (DXP) for approximately more than two years as of now, as part of our institution's digital engagement and content management activities.

Before using Acquia Digital Experience Platform (DXP), we primarily relied on a more traditional content management approach that involved a combination of standard CMS tools and internally managed content processes. The main reason for moving to Acquia Digital Experience Platform (DXP) was the need for a more scalable and centralized platform that could better support content governance, workflow management, and digital engagement across different stakeholder groups. As our requirements grew, particularly around efficiently managing content and ensuring consistency across digital channels, we needed a solution that offered stronger workflow capabilities, improved management, and greater flexibility for future growth. This transition has helped us consolidate content management activities and provided a more structured approach to publishing approval and stakeholder communication, driven more by the need for enhanced capabilities and scalability than dissatisfaction with the previous solution.

We have noticed several positive impacts since implementing Acquia Digital Experience Platform (DXP), focusing more on improving digital communication and content operations rather than tracking formal ROI metrics. Most benefits are operational; for example, we find that content updates that previously required coordination across multiple teams can now be completed much faster through a centralized workflow. During peak recruitment periods, this efficiency has helped us publish schedule changes and announcements more effectively. We also see fewer instances of outdated or inconsistent information being published because the approval workflow introduces an additional layer of review before content goes live. From an engagement perspective, students have easier access to placement-related information through a single digital experience, which reduces the volume of repetitive queries received by the placement team and improves overall communication efficiency. While I do not have specific percentage improvements to share, key outcomes include faster content publishing, improved content accuracy, and a smoother experience for both students and external stakeholders.

I advise others looking into using Acquia Digital Experience Platform (DXP) that it is a great platform, and they should start by clearly defining their business objectives and the digital experience they want to deliver before implementing this platform. Acquia Digital Experience Platform (DXP) is a powerful solution, and organizations tend to get the most value from it when they have a well-defined content strategy, governance model, and user engagement goals. I also recommend involving both business and technical stakeholders early in the process. The platform offers a wide range of capabilities, and collaboration between content owners, administrators, and IT teams helps ensure effective use of those capabilities. For organizations considering the platform, it is worth investing time in user training and adoption. While the basic functionality is straightforward, understanding the broader feature set can unlock additional value over time. I would encourage organizations to think beyond content management alone.

Acquia Digital Experience Platform (DXP) has been a solid and reliable platform for managing digital experiences and content at scale. Its strengths lie in content management, governance, scalability, and supporting consistent stakeholder engagement across digital channels. While certain areas exist where user experience or advanced feature accessibility could be further enhanced, these are opportunities for improvement rather than significant concerns. Overall, the platform has met expectations and provided meaningful value to our organization.

My main use case for Acquia Digital Experience Platform (DXP) is as the founder of intelligency.ai, where we build AI-driven integrations across CMSs and digital experience platforms, and we have evaluated Acquia Digital Experience Platform (DXP), particularly in the context of Drupal-based enterprise environments.

A quick, specific example of how I used Acquia Digital Experience Platform (DXP) in one of my projects is that we built an instance of it that is marketing-specific and then we used some of our applications to interact with that particular instance.

My applications interacted with Acquia Digital Experience Platform (DXP) in that marketing-focused instance by sending content and images that we have generated from one platform to another.

In my experience, the best features Acquia Digital Experience Platform (DXP) offers include being a strong enterprise platform, especially if you are already in the Drupal ecosystem, with solid governance, scalability, and structured content capabilities, particularly for organizations with multiple teams and sites, and I really enjoyed the multi-use aspect of it, as that is where it really comes into its own.

What I appreciated most about the multi-use aspect is that you can work on the same project together and collaborate, which is really useful.

Acquia Digital Experience Platform (DXP) has positively impacted my organization primarily through its ease of use, making it easier to generate content and pages, especially from a marketing perspective, so entry-level people can access it and utilize it as well as advanced users, appealing to a range of people.

That ease of use translated into tangible benefits for my team in terms of improved productivity because you can create a whole marketing campaign really quickly, making marketing happen very effectively.

The main improvement needed for Acquia Digital Experience Platform (DXP) is related to its complexity, as it is not that lightweight with a surfeit of features, requiring users to read up on all the myriad of features, and while it is a sophisticated enterprise product that necessitates that complexity, the learning curve can be a bit steep for less experienced users needing quick task completion.

The needed improvements for Acquia Digital Experience Platform (DXP) include that the product is evolving in the right direction, and the AI aspect probably needs a bit more improvement, especially where it aligns with AI-driven content orchestration.

I have been using Acquia Digital Experience Platform (DXP) for about three years.

I find Acquia Digital Experience Platform (DXP) to be fairly stable, with no problems at all.

Acquia Digital Experience Platform (DXP)'s scalability is excellent because it works with small teams and small enterprises, which is one of its core advantages.

The company has actually had multiple solutions previously, experimenting with WordPress, Magento, Joomla, and others.

Regarding pricing, setup cost, and licensing, since we are using an evaluation rather than full versions, the pricing is obviously quite high, so we are not making that commitment because of the pricing aspect.

Before choosing Acquia Digital Experience Platform (DXP), I evaluated other options such as WordPress, Magento, and Joomla.

I use Acquia Digital Experience Platform (DXP) to manage our global website by utilizing its primary hosting environments for Drupal, which is an open-source CMS, partnering with Drupal to provide not just hosting but also additional peripheral services, solutions, and tools. At both companies where we used Acquia, they were our primary host and provider of CDN capabilities in addition to other tools such as heat mapping and marketing automation tools.

Currently, I use Acquia Digital Experience Platform (DXP) as our main host for our content management system as well as our CDN.

Acquia Digital Experience Platform (DXP) positively impacts our organization by providing the tools and capabilities needed for a successful digital presence and digital footprint. However, the real challenge comes down to ensuring we have the right strategy and the right team to drive and enable that strategy on their platform, since they give us the tools but we have to handle the strategy and building.

I have been involved with Acquia Digital Experience Platform (DXP) in two different roles. In a previous experience at a different company, we faced many challenges with their service and support, requiring frequent contact for issues where responsiveness was sometimes lacking. I am not in the same role here, so I cannot speak directly to how challenging it might be for our IT team who manages the tool physically, but I have not heard anything negative, although I know I had a more challenging time previously.

My experience with customer support for Acquia Digital Experience Platform (DXP) was terrible. I would have rated the customer support a five based on my previous experience before joining Bio-Rad.

Positive

I did not choose Acquia Digital Experience Platform (DXP), as the decision was made before I arrived. However, I did evaluate other options, and Acquia was not on my list of recommendations.

When using Acquia Digital Experience Platform (DXP), the outcomes I notice include cost savings since using an open-source platform such as Drupal, which saves us money compared to enterprise options such as Adobe AEM or Optimizely. However, we still face challenges with uptime and page performance.

My advice to others looking into using Acquia Digital Experience Platform (DXP) is that if you are looking to save money without investing in a large-scale enterprise DXP, it is probably a good option. However, you need to understand that the customer service you expect might not meet your expectations even if you pay for the top tier of support. I would rate this review a seven overall.

I have been using Acquia Digital Experience Platform (DXP) for approximately six to seven years in my institute and across a few collaborative research and digital transformation initiatives.

My main use case for using Acquia Digital Experience Platform (DXP) has been enterprise-level digital experience management and centralized multi-site content governance for my institution and associated collaborative ecosystem. Over time, the implementation evolved far beyond traditional content management and became a core component of my broader digital transformation and engagement strategy. In the higher education and research environment, managing digital experiences is significantly more complex than maintaining a standard corporate website. I have multiple stakeholders with very diverse requirements, including prospective students, current students, faculty members, researchers, administrative departments, alumni, industry collaborators, and internal academic partners. Each of these user groups expects personalized, responsive, and highly accessible digital interaction. One of my biggest use cases is centralized multi-site management. My institute operates multiple department websites, research center portals, conference microsites, faculty pages, administrative portals, and event-specific platforms. Prior to adopting Acquia Digital Experience Platform (DXP), these systems were fragmented and managed independently, which created inconsistencies in branding, governance, security policies, and content workflow. With Acquia Digital Experience Platform (DXP), I was able to establish a more standardized digital ecosystem while still allowing departments enough flexibility to manage their own content. Another important use case has been integration management. My institution already had several existing enterprise systems, including the learning management system, authentication system, student information system, analytical platforms, and third-party communication tools. With DXP API flexibility and the Drupal ecosystem, it made it easier to integrate these systems into a more connected digital environment. Overall, my primary use case is best described as creating a scalable, secure, personalized, and centrally governed digital experience ecosystem that supports academic operations, institutional branding, and stakeholder engagement.

Acquia Digital Experience Platform (DXP) centralized multi-site management has actually been one of the most valuable aspects of DXP in my day-to-day operation because my institution manages a large number and diverse digital ecosystem. In practical terms, I am not dealing with just one institute website. I have multiple department portals, faculty pages, research initiative websites, event microsites, admission platforms, student engagement portals, and innovation center pages. Managing all these independently would create an enormous operational overhead and governance challenges. I have also benefited greatly from the reusable components and shared content models. Many institutional websites require similar functionalities, such as faculty profiles, event calendars, and news sections. I created reusable frameworks and templates that accelerate development and maintain consistency. Overall, on a day-to-day basis, centralized multi-site management has improved my operational efficiency, governance consistency, reliability, and security management.

One of the best features that Acquia Digital Experience Platform (DXP) offers me and my institute is the centralized multi-site management capability because for my institution or enterprise managing the multiple digital platforms or properties, this feature becomes extremely valuable. I was able to manage department websites and institutional platforms under a unified governance model while still allowing centralized content ownership. This balance has made my development flexibility something many platforms struggle to achieve effectively. Another feature which I personally found exceptionally useful for my institution is the integration flexibility because modern digital ecosystems rarely operate in isolation. I was able to integrate Acquia Digital Experience Platform (DXP) with my authentication system, analytics platform, CRM tools, learning management system, and communication tools with various third-party APIs. The platform's API-first and modular architecture made the integration relatively manageable. This interoperability is extremely important for institutions pursuing broader digital transformation initiatives.

One of the most underrated strengths is the maturity of the platform ecosystem itself because Acquia is not just providing a CMS; it also provides an enterprise digital experience ecosystem with hosting, governance, personalization capabilities, dev tooling, support services, and enterprise-focused operational practices. Overall, the best features of Acquia Digital Experience Platform (DXP) in my experience are the centralized multi-site management, enterprise-grade scalability, and cloud infrastructure management.

Another experience related to the authoring experience for non-technical users is relatively strong for my organization because one challenge with enterprise platforms is balancing the technical power with usability. Acquia Digital Experience Platform (DXP) does a fairly good job of allowing content teams, communication departments, and non-technical contributors to manage content without requiring extensive developer involvement for routine tasks.

Acquia Digital Experience Platform (DXP) can be improved in several ways. I believe there is still meaningful room for improvement in several areas. One area where I believe improvement is possible is the overall learning curve and onboarding experience, especially for non-technical users and organizations that are newer to the enterprise Drupal ecosystem. Acquia Digital Experience Platform (DXP) is powerful and highly flexible, but that flexibility sometimes introduces complexity. For technical teams with strong Drupal experience, the platform is manageable. But for a small organization or institute or teams with limited enterprise CMS experience, the initial setup and governance architecture feel overwhelming. I feel more guided onboarding frameworks and simplified configuration are required. Another area that could be improved is the user experience for content authors and business users. While Acquia has improved in this area over time, there are still opportunities to make the content management experience more modern, streamlined, and business user-friendly.

I also believe the platform could further strengthen its native AI and intelligent automation capabilities. As someone working extensively in machine learning and AI, I see enormous potential for deeper integration of intelligent features directly within the platform ecosystem, such as automated SEO optimization suggestions, predictive personalization, behavioral segmentation, content quality scoring, and natural language search and content discovery. Another area where I see future opportunity is composable architecture support. Modern enterprises increasingly prefer flexible, headless, and composable digital ecosystems where services can be swapped or extended easily. Overall, Acquia Digital Experience Platform (DXP) can certainly be improved, particularly in the area of usability, AI-driven capabilities, onboarding simplicity, and many more.

Digital accessibility and compliance requirements continue evolving globally. Stronger built-in accessibility governance and automated compliance monitoring would be highly beneficial. I also believe that documentation and knowledgeable accessibility could continue to be improved. The technical documentation is comprehensive, but sometimes it is highly fragmented or oriented toward experienced Drupal developers. Another area where I feel improvement would be valuable is integration simplification. It supports integration quite well from an architectural standpoint, but enterprise ecosystems are becoming increasingly API-driven and composable.

One of the first measurable improvements was the reduction in infrastructure and maintenance overhead. Before centralization, I estimated roughly a thirty to forty percent reduction in operational efforts related to infrastructure administration and routine maintenance activity. In a few cases, I have seen release preparation and deployment time reduced by nearly fifty to sixty percent, especially for routine content and feature updates. I have also seen approximately thirty to forty percent estimated reusable components and standardized frameworks reduced repetitive development efforts by approximately thirty-five to forty-five percent across multiple digital initiatives. These are the rough numbers which I have shared with you related to the positive impact I have seen.

My advice to people who are going to use Acquia Digital Experience Platform (DXP) is to approach it as a long-term strategic digital transformation platform rather than simply a website management solution. One of the first things I would recommend is investing time in defining a strong digital architecture and governance strategy before implementation begins. Acquia Digital Experience Platform (DXP) is a powerful and highly flexible platform, but that flexibility can also create complexity. I would also strongly advise organizations to avoid treating the platform as only a CMS deployment. The real value of Acquia Digital Experience Platform (DXP) emerges when it becomes part of a broader digital ecosystem involving analytics platforms. Organizations should carefully evaluate whether they truly need an enterprise-grade DXP because Acquia Digital Experience Platform (DXP) is extremely capable, but it is most valuable for organizations with complex multi-site ecosystems, high governance requirements, and long-term scalability needs. Acquia Digital Experience Platform (DXP) is a very powerful platform and I suggest everyone who is looking to use the same tool should pursue it. I have given this review a rating of eight.

I have been using Acquia Digital Experience Platform (DXP) for the last two and a half years as part of my role as a QA engineer, and during this time, I have worked on testing web applications, validating deployments across environments, and also performing regression and functional testing, collaborating with the development and DevOps teams to ensure stable releases and smoother experiences.

My primary use case for Acquia Digital Experience Platform (DXP) is supporting enterprise-level website and digital experience testing within our QA environment, where I mainly use the platform for validating web application functionality, content workflow, deployment stability, and overall user experience across multiple environments. As a QA engineer, I work closely with developers, business teams, and content authors to ensure website releases are functioning correctly before production deployments. Another important use case is validating multiple environment deployments and release management processes, since Acquia Digital Experience Platform (DXP) provides structured cloud hosting and deployment pipelines, which we use extensively for testing staging and production readiness, ensuring minimum downtime and a stable release.

One scenario that stands out is in one of our enterprise website projects, where we use Acquia Digital Experience Platform (DXP) to manage and deploy a large customer-facing Drupal-based portal that handles content publishing, user interface, user interactions, and third-party integration. My role as a QA engineer is to validate the complete release cycle before production deployment, including testing newly developed features, verifying the content workflow, and ensuring stability across development, staging, and production environments. During a major website enhancement release, where multiple modules, API integrations, and UI builds were deployed simultaneously, I used Acquia Digital Experience Platform (DXP) environment to manage the deployment pipeline for regression testing, validating cache behavior, and verifying role-based access permissions, ensuring content synchronization was functioning correctly. I also tested integration with analytic tools and external APIs to confirm that customer data and tracking events were working correctly after deployment. The platform provided a consistent cloud environment and monitoring support, allowing me to identify issues early and significantly reduce deployment risk.

I personally appreciate several features about Acquia Digital Experience Platform (DXP), particularly its enterprise-grade cloud hosting and environment management capabilities. The consistency across development, staging, and production environments is extremely helpful for reducing development-related issues and making testing more reliable. The integration with Drupal and flexibility for managing complex digital experiences are also valuable, as the content management workflow, role-based permissions, and publishing controls help my technical and non-technical teams collaborate efficiently. I appreciate the CI/CD and deployment pipeline support, which makes release validation smoother and accelerates the testing cycle. Performance optimization features, including caching mechanisms, CDN support, monitoring tools, and automated backups, are very beneficial for my team. Additionally, Acquia Digital Experience Platform (DXP) security and stability capabilities are crucial for enterprise projects, as the platform efficiently handles high traffic and provides a secure infrastructure, giving us confidence during large-scale deployments and production releases.

Acquia Digital Experience Platform (DXP) has positively impacted my organization by improving deployment stability, streamlining the content management workflow, and enhancing collaboration between technical and business teams. One notable improvement is better release management and reduced deployment-related issues since the platform provides consistent cloud environments and structured CI/CD support, allowing QA and development teams to perform testing more efficiently and identify issues earlier in the release cycle. This reduces production incidents and improves the overall quality of releases. Improved website performance and reliability are also significant, as features including caching, CDN integration, and monitoring tools contribute to maintaining stable performance even during high-traffic periods, leading to fewer downtime issues and better end-user applications. From a business perspective, the organization benefits from faster content updates, improved website stability, and a more scalable infrastructure capable of supporting future growth and digital initiatives. Overall, Acquia Digital Experience Platform (DXP) helps improve operational efficiency, release confidence, and customer experience.

After using Acquia Digital Experience Platform (DXP), I have found a few areas that could improve. One area is the learning curve for new users, as the platform includes many enterprise-level features and integrations, which sometimes makes onboarding complex, especially for those unfamiliar with the Drupal ecosystem and cloud deployment workflows. More simplified onboarding guidance and beginner-friendly documentation would benefit new users. Another important area is the user interface and administrative experience; some sections feel that they require a more modern and intuitive approach, particularly when managing environment deployment and configuration settings, so a modern UI would be useful. Simplifying navigation and improving usability would help my team work more efficiently. From a QA and release management perspective, deeper built-in testing and reporting capabilities could add more value to the system, as enhanced dashboards for deployment tracking, automated test integration visibility, and centralized reporting would improve monitoring and troubleshooting during our release cycles. Additionally, the licensing and pricing may challenge small organizations with limited budgets; offering more flexible pricing models or feature packages could make the platform more accessible to a wider range of businesses. Overall, Acquia Digital Experience Platform (DXP) performs well for enterprise digital experience management, but improvements in usability, onboarding, and reporting would enhance the overall experience.

I have been working in my current field for the last five and a half years.

Acquia Digital Experience Platform (DXP) is stable for me, and I have not personally seen any downtime, even during high traffic in our systems. In my experience, it is quite stable, and Acquia Digital Experience Platform (DXP) provides very useful tools. One of the key strengths of the platform is its managed cloud infrastructure and environment consistency, which help maintain stable deployments across development, staging, and production environments. The platform also performs very well under normal and high-traffic conditions due to features including caching, CDN integration, performance optimization, and scalable hosting architecture, and we have observed only a few production incidents and better uptime compared to more manually managed infrastructure setups.

Acquia Digital Experience Platform (DXP) is quite scalable; we find it efficient whenever we encounter high traffic or need to support growing digital operations and multiple web properties. The platform's cloud-based architecture allows the organization to scale infrastructure resources more efficiently based on traffic demands and business growth. In my experience, the platform reliably handles increased web traffic and large content volumes without major performance degradation.

I have interacted with the customer support team, and they are very knowledgeable and always ready to help, especially during our initial setup days. Due to regional time differences, sometimes their responses are delayed, but overall they are very knowledgeable and willing to assist. I would rate the customer support ten out of ten.

I have definitely used a different solution before adopting Acquia Digital Experience Platform (DXP). The organization was using a more traditional self-managed content management and hosting setup based primarily on Drupal and separately managed infrastructure and development processes. Compared to the previous setup, Acquia Digital Experience Platform (DXP) provides a much more centralized and enterprise-focused platform with better cloud hosting, development, deployment management, scalability, and operational support. Earlier teams had to spend more effort managing environments, handling development coordination manually, and troubleshooting infrastructure-related issues. One main reason for switching was the need for a more scalable and reliable enterprise digital experience platform that could support growing business requirements, faster release cycles, and improved website performance.

We have definitely observed a positive return on investment after using Acquia Digital Experience Platform (DXP), particularly in terms of operational efficiency, deployment stability, and reduced manual efforts. One of the biggest improvements is the reduction of deployment and environment-related issues because the platform provides a more stable and standardized environment. Our QA and development teams spend less time troubleshooting configuration inconsistencies and release failures, which helps reduce overall testing and release validation time by approximately twenty-five to thirty percent. We have also seen improvements in release efficiency and collaboration, as development-deployment coordination between development, QA, and content teams has become more streamlined, shortening the release cycle and allowing faster delivery of website updates and new features. While the organization may not have directly reduced headcount, the platform has definitely improved team productivity, reduced the time spent on repetitive operational tasks, and increased confidence during enterprise-scale deployments. Overall, the ROI is visible through time savings of around fifteen to twenty percent, and it has also improved release quality and efficient cross-team collaboration.

I considered other platforms, including Adobe Experience Manager and Sitecore, as well as other Drupal-based management hosting solutions.

As an experienced user, I have a few recommendations for others considering Acquia Digital Experience Platform (DXP). First, they should evaluate their long-term digital experience and scalability requirements before implementing Acquia Digital Experience Platform (DXP), as the platform is particularly well-suited for enterprise environments that need strong content management capabilities and scalable cloud infrastructure. I also recommend investing time in proper planning, architectural design, and onboarding during the initial implementation phase. Since Acquia Digital Experience Platform (DXP) offers many enterprise-level features, having a well-defined workflow for development and establishing strong testing and release management processes early—especially around environment management, CI/CD pipelines, regression testing, and performance validation—are essential because the platform performs best when organizations follow structured deployment and governance practices.

I want to highlight Acquia Digital Experience Platform (DXP) ability to support collaboration across multiple teams, including developers, QA engineers, content editors, and business stakeholders. The platform's structured workflow improves coordination during releases and content updates, and I appreciate its flexibility and extensibility, as enterprise projects often require custom integrations and evolving business requirements. Acquia Digital Experience Platform (DXP) makes it easier to scale applications and adapt to new functionalities without major disruption. The monitoring and reporting capabilities help the team quickly identify performance or deployment-related issues, improving troubleshooting efficiency and maintaining overall application quality. The platform offers a good balance of content management, cloud infrastructure, deployment automation, security, and scalability, making it well-suited for enterprise digital experience projects.

Regarding governance and security, I think that the capabilities are quite strong, especially for enterprise environments where compliance, access control, and content security are critical. The platform provides structured role-based access control, permission management, and environment-level security, helping organizations maintain proper governance across development, QA, content, and production teams. This is particularly useful in large projects where multiple stakeholders are involved in content publishing and development workflows. Acquia Digital Experience Platform (DXP) focuses on secure infrastructure and centralized management, which helps organizations maintain better control over data access and content handling. The platform's cloud hosting, monitoring, backup management, and security practices contribute to overall operational reliability and risk reduction. As AI capabilities continue evolving across digital experience platforms, there is still room for enhancement in areas such as more advanced AI governance visibility, centralized AI activity reporting, and deeper transparency into AI-driven recommendations or automation behavior.

The accuracy and reliability of output related to AI capabilities and automated recommendations are generally reliable and helpful for improving digital experience management and content operations. The outputs are usually accurate for common use cases such as content personalization, recommendations, search optimization, and customer experience enhancement. The platform performs effectively with structured data and properly configured workflows, and AI-driven features help teams improve content targeting and user engagement efficiency. From a QA perspective, I find that AI-assisted functionality is reasonably consistent and stable during validation and testing activities. The recommendations and automated behavior generally align with configured business rules and expected workflows, maintaining predictable application behavior. I also believe that there is room for improvement in transparency and explainability of AI-generated outputs; more detailed visibility into how recommendations are generated and stronger reporting around AI decision-making would help my team validate results more confidently. Overall, I would say that the AI capabilities are dependable for enterprise-level digital experience use cases, especially when combined with proper governance, testing, and human oversight.

I advise other organizations to fully utilize Acquia Digital Experience Platform (DXP) monitoring, caching, security, and supporting features, as these provide significant operational value and help maintain proper stability and performance for their organizations. I would rate this product an eight out of ten overall.

My name is Sujin Tommy, and I was a web developer at TCS. I left TCS in January 2026 and am now looking for opportunities in the United Kingdom. My experience comes under Drupal CMS, and we were using Acquia for our back-end cloud technology. We used Acquia-supported front-end components such as Site Studio for our front-end built-in components. We built sites for a pharmaceutical company called Bayer Germany.

I worked for five years at TCS, and during that entire period, I worked under the same project for the pharma company. We managed their product sites, which totaled around 800 sites built in Drupal CMS. We used JS frameworks such as React and some decoupled architecture components in the front-end to overcome the limitations of Acquia-provided Site Studio components.

I used Acquia Digital Experience Platform (DXP) throughout my entire experience. When I joined the company, I learned that Acquia was a cloud tool. We were able to log into Acquia cloud and see the back-end in a UI manner. We could delete, clone, and perform cache clearing through a simple interface, which was very beneficial. For the front-end, we used Acquia-supported Site Studio components, which were drag-and-drop components that we could easily use to build our web pages, such as image components, header components, and paragraph components. Building pages using Site Studio components was very easy, and using Acquia Digital Experience Platform (DXP) for our website and project was really great. It reduced our effort significantly.

We used Site Studio components as our main use case. We used Site Studio components for creating pages. They were reusable components that we could use for creating pages easily.

We faced some issues with Site Studio components, such as loading time and performance issues. We solved these issues using some Drupal fixes, and it worked well afterward. The main thing about Site Studio was its compatibility with Drupal. The overall functionality and user experience with Site Studio components was great, and it was really very compatible.

I have only used the Site Studio component product of Acquia Digital Experience Platform (DXP). I know Acquia has other digital experience products, but I am only familiar with Site Studio.

The main advantages include usability and the ability to make changes and create custom components. Acquia provides elements that allow us to create custom components to meet our needs, and the customization is also a positive aspect of Site Studio components.

It helps a lot because managing 800 to 1,000 sites is not an easy task, and Acquia products always help us to manage those effectively.

Considering the back-end with Acquia cloud that we used, it was very scalable and we were able to run our 800 sites smoothly for users. We needed quite a large server and needed to scale it for our new needs, so it was very compatible for us. Considering the front-end, the reusability saved a lot of time and effort. From the customer point of view, they could reduce the number of employees because using this feature, everybody can make pages using the drag-and-drop functionality. They do not need technical knowledge or development experience, so it was very easy for them as well.

The integration capabilities were really good and were really compatible with other features and integration tools.

I only have product knowledge about Site Studio, and the only missing thing was some kind of performance issues. We faced loading issues, performance issues, and some kind of optimization issues on some pages. Acquia may have optimizations that we have not purchased, but for our case, we faced some performance issues.

Since I do not exactly know if there are any existing solutions for the performance issues which we were not subscribed to, I am not an expert to comment on that. The only issue I faced was what I already mentioned, and the fix I can suggest is that they can improve performance. That thing might already be there, but I am not sure about that.

I used Acquia Digital Experience Platform (DXP) for almost five years.

Acquia Digital Experience Platform (DXP) was really stable in my experience and worked reliably most of the time.

Considering the back-end with Acquia cloud that we used, it was very scalable and we were able to run our 800 sites smoothly for users. We needed quite a large server and needed to scale it for our new needs, so it was very compatible for us.

It was easy to scale up Acquia Digital Experience Platform (DXP) as our needs grew.

Sometimes we felt downtimes, and then we needed to log a ticket to Acquia. The Acquia support team would fix that, and they were really prompt.

As I already mentioned, customer support for Acquia Digital Experience Platform (DXP) was really great, and the customer service was really prompt, even during downtimes.

Positive

It is very easy for beginners to get started with Acquia Digital Experience Platform (DXP) and Site Studio.

I would rate this solution a seven on a scale of one to ten. The things I have already told substantiate this score.

It was a private cloud, and you have to have login credentials to log into Acquia cloud.

It was really helpful, and it was really easy to access from Acquia documentation.

It was really great in terms of user interface and overall user experience of Acquia Digital Experience Platform (DXP); it was easy and intuitive to use.

It met all our needs, and the customization feature was really helpful, even for beginners.

Since I do not know the exact figures, I cannot provide a detailed answer because I was only a developer.

I cannot share any particular exact values, but I can only share around data because it obviously saves time, reduces costs for customers, and also fewer employees are needed to complete all tasks.

I have not used any security features of Acquia because we were using Drupal, and Drupal has its own security features, so we did not use any security features of Acquia.

Our main use case for Acquia Digital Experience Platform (DXP) is to build our company's marketing website in the previous two organizations, where we built components that the marketing team can use to create landing pages and all types of pages.

One specific project that stands out is my company's marketing website, where we had various content types including news, articles, and insights. Acquia Digital Experience Platform (DXP) was very helpful in managing different types of content with separate fields so that the non-technical marketing team could easily use the components we built and create the landing pages and features they wanted.

Acquia Digital Experience Platform (DXP) has positively impacted my organization by simplifying deployment processes and reducing the time required to build new features, thanks to features including pipelines and Acquia Site Factory.

Since moving to Acquia Digital Experience Platform (DXP), we have saved approximately three times the amount of time in deployment and site creation processes.

Acquia Digital Experience Platform (DXP) is unique in my projects because it easily integrates with Acquia Site Factory and the cloud, making hosting simpler and allowing us to create and launch new sites easily.

The best feature Acquia Digital Experience Platform (DXP) offers is Acquia Site Studio, which provides drag-and-drop features with inbuilt components we can use to build pages, add styles and JavaScript, and various elements based on our requirements.

Out of all the features, my team and I find ourselves using Acquia Site Studio the most, and it makes our day-to-day work easier as we use it almost every day.

Acquia Digital Experience Platform (DXP) could be improved by allowing more customization options, as it currently has limitations with hooks in its core Drupal system that prevent us from making custom modules easily.

I have been using the solution for about three to four years.

Acquia Digital Experience Platform (DXP) is stable.

The scalability of Acquia Digital Experience Platform (DXP) is great; it can handle increased workloads easily, as we have load balancers and multiple web server instances, allowing us to scale up with traffic.

The customer support for Acquia Digital Experience Platform (DXP) is excellent; we have weekly calls with a technical account manager who addresses any queries, and for urgent problems, we can raise issues through a portal that gets resolved promptly.

Before using Acquia Digital Experience Platform (DXP), we used plain Drupal and faced hosting issues.

In plain Drupal, the hosting problems were significant, but after moving to Acquia Digital Experience Platform (DXP), we have access to Acquia Cloud and pipelines, making deployment easier and faster, with continuous testing and useful tools including modules and Acquia Site Studio.

I am uncertain whether Acquia Digital Experience Platform (DXP) was purchased through the AWS Marketplace, as it was already acquired before I joined the organization.

We have seen a return on investment with Acquia Digital Experience Platform (DXP), as we now need fewer employees; our HTML team has been reduced from three people to one due to increased efficiency.

The advice I would give to others looking into using Acquia Digital Experience Platform (DXP) is to utilize all its inbuilt features and additional products for content and asset management to enhance website performance.

Acquia Digital Experience Platform (DXP) was used as an enterprise-scale platform for CMS work, especially Site Studio for low-code site building and segregating customer data into unified customer profiles and segmentations for marketing purposes.

I worked on the personalization part of the content in B2C, specifically for a financial services company that uses Acquia CDP to unify customer data from the website, mobile app, call center, and email interactions.

One of the best features Acquia Digital Experience Platform (DXP) offers is Site Studio, which provides low-code site building for content editors without having to rely on back-end developers, and the Acquia Cloud Platform that it is hosted on.

Site Studio has specifically helped my team by being a very good low-code builder that provides a drag-and-drop visual builder that lets non-developers create pages using pre-built components, and it maps very nicely with the SDC component library approach, allowing marketers to assemble them. Site Studio is Acquia's answer to the criticism that Drupal's authoring experience lags behind competitors.

Regarding the cloud platform, it is built on the Open API framework, and performance monitoring and enterprise caching are available at all layers of the stack, with CI/CD and deployment automation via pull requests, as well as CLI tools for terminal access to every API endpoint it provides. As a Drupal developer, this is where I spend most of my time, and the branch-specific environments for PRs are particularly useful for the kind of Bitbucket pipeline workflows we build.

The positive impacts from the organization using Acquia Digital Experience Platform (DXP) are notable. After migrating to DXP, the results were dramatic, including a 70-plus percent increase in conversion rate and a 30-plus percent increase in online booking revenue. Most impressively, the drop-off rate plummeted from 82 percent to 28 percent, and content updates that previously took weeks now happen in seconds.

The increase in conversion rate and reduction in drop-off rate can be attributed to the new features and the improved user experience, with most of it being about marketers being able to assemble the pages on their own.

One of the improvements needed for Acquia Digital Experience Platform (DXP) involves platform sizing and pricing transparency, which is the most consistent complaint I have seen across various clients. The way Acquia sizes its platform for customers is described as ambiguous and often results in penalties after doing business. Users also note that overall cost can be high and limits accessibility for smaller businesses. Additionally, the Site Factory provisioning environment takes a lot of time, and often more environments are needed than what is available by default, requiring you to go through support and sales processes. For teams handling CI/CD pipelines and needing fast environment spin-ups, this lag is a real bottleneck.

Support gaps exist since support follows standard SLAs, and sometimes there are different difficulties when dealing with critical issues due to the lack of a 24/7 available team.

In my current field as a Drupal developer, I have been working with Drupal development since 2014, so overall it has been around 12 years into Drupal.

Acquia Digital Experience Platform (DXP) is stable.

Acquia Digital Experience Platform (DXP) offers pretty good scalability because it provides high scalability.

Customer support for Acquia Digital Experience Platform (DXP) is good, but I think it could be improved in terms of 24/7 availability due to the people being spread across different regions.

We previously used Layout Builder, and we eventually moved to Acquia Digital Experience Platform (DXP) for a better enterprise experience.

I did not purchase Acquia Digital Experience Platform (DXP) directly through the AWS Marketplace. There was a sales team involved, and they contacted the Acquia team, which seems to be the channel used for the sales process.

We evaluated other options before choosing Acquia Digital Experience Platform (DXP).

I have seen a return on investment since earlier we relied heavily on developers on an ongoing basis. When we wanted to rearrange components within the templates, we had to rely on tickets, and more developers were needed. Now, it is a one-time activity, allowing more marketers to simply assemble the components as they need.

Regarding my experience with pricing, setup cost, and licensing, I do not have a clear idea since it is more around the sales team's questions, and because I worked on the enterprise platform, it was not clear with the technical team about the pricing.

We evaluated other options before choosing Acquia Digital Experience Platform (DXP).

My advice for others looking into using Acquia Digital Experience Platform (DXP) is to definitely use it if they have an enterprise customer or client who wants to get real usage from the CMS work along with the CDP and low-code site building, which will be beneficial for them if they switch to Acquia Digital Experience Platform (DXP). I have rated this product an 8 out of 10.