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.
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.
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.
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.
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.
Software Developer at a outsourcing company with 1,001-5,000 employees
Real User
Top 20
Mar 30, 2026
I have been using Acquia Digital Experience Platform (DXP) for approximately one and a half to two years. I typically use Acquia Digital Experience Platform (DXP) for tools such as Acquia Cloud, Site Studio, and website hosting, as well as for development practices including CI/CD pipelines and automated testing. Most of my use with Acquia Digital Experience Platform (DXP) is with Site Studio, where I use it to build prototypes and web pages. My full website revolves around Site Studio. I also use the CI/CD and hosting capabilities so that I can deploy website changes, and Acquia takes care of all the CI/CD, testing, and hosting. Since my website is 100% built around Drupal, Acquia Digital Experience Platform (DXP) is the best place to host my website. One of the platform's key strengths is its ability to unify content management, personalization, and customer data into a single experience layer, enabling my team to build highly tailored digital journeys across multiple channels for enterprise websites like the one I work for, as well as e-commerce integrations and customer portals.
Learn what your peers think about Acquia Digital Experience Platform (DXP). Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
My main use case for Acquia Digital Experience Platform (DXP) is to manage our public-facing global website at both Bio-Rad and a previous company.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.
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.
Founder at a wholesaler/distributor with 51-200 employees
Real User
Top 10
Mar 10, 2026
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.
I use Acquia primarily for front-end development and building reusable components. We employ a model approach with the paragraph model to build reusable components and layout builders. We also utilize micro front-end concepts, tweak templating, and dynamic themes with personalization features, allowing users to configure their themes.
We primarily use the Acquia Digital Experience Platform (DXP) to develop sites and apps in the financial customer and retail sectors. We also work with big brand sites. We use the platform to build websites, mobile applications, solutions for digital asset management, and marketing campaigns.
Acquia Digital Experience Platform (DXP) is a comprehensive suite designed to facilitate content management, site building, and digital marketing. It integrates various tools to deliver personalized customer experiences across different digital channels.
What key features does Acquia DXP offer?
Content Management System (CMS): Built on Drupal, it offers robust content management capabilities that enable users to create, manage, and optimize digital content easily.
Personalization: Acquia...
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.
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.
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.
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.
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.
I have been using Acquia Digital Experience Platform (DXP) for approximately one and a half to two years. I typically use Acquia Digital Experience Platform (DXP) for tools such as Acquia Cloud, Site Studio, and website hosting, as well as for development practices including CI/CD pipelines and automated testing. Most of my use with Acquia Digital Experience Platform (DXP) is with Site Studio, where I use it to build prototypes and web pages. My full website revolves around Site Studio. I also use the CI/CD and hosting capabilities so that I can deploy website changes, and Acquia takes care of all the CI/CD, testing, and hosting. Since my website is 100% built around Drupal, Acquia Digital Experience Platform (DXP) is the best place to host my website. One of the platform's key strengths is its ability to unify content management, personalization, and customer data into a single experience layer, enabling my team to build highly tailored digital journeys across multiple channels for enterprise websites like the one I work for, as well as e-commerce integrations and customer portals.
My main use case for Acquia Digital Experience Platform (DXP) is to manage our public-facing global website at both Bio-Rad and a previous company.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.
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.
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.
I use Acquia primarily for front-end development and building reusable components. We employ a model approach with the paragraph model to build reusable components and layout builders. We also utilize micro front-end concepts, tweak templating, and dynamic themes with personalization features, allowing users to configure their themes.
We primarily use the Acquia Digital Experience Platform (DXP) to develop sites and apps in the financial customer and retail sectors. We also work with big brand sites. We use the platform to build websites, mobile applications, solutions for digital asset management, and marketing campaigns.