The Acquia Digital Experience Platform is an "Open DXP" with its two core pillars being content and data. Built on top of one of the largest open-source content management systems, Drupal, it aims to provide the flexibility and interoperability a modern organization needs. With its customer data platform, it allows organizations to understand who their customers are and deliver personalized experiences. Acquia's DXP offers variety of other tools including digital asset management,…
Acquia Personalization integrates well with Drupal CMS and is more straightforward to implement than Salesforce Marketing Cloud Interaction Studio (Personalization). WordPress as a CMS hosted on WP Engine is useful, but much more limited than Drupal CMS hosted on Acquia Word…
Drupal is Wordpress on crack. And using Acquia Digital Experience Platform is like using a managed Wordpress site: Most of the installation and maintenance is done for you.
We stay with Acquia because they offer managed updates to Drupal core. Not everyone does. And, they are experts in supporting Drupal. They can often get a little closer to the developer side of things than other companies. Prices and support are similar for similar services …
Acquia coupled with their easier interface and 24 x 7 customer service can outweigh its competitors anytime. Acquia provides a full end to end solution for Drupal websites.
The flexibility aspect of Acquia Site Studio is unmatched and WordPress does not provide it on a large scale. The ability to perform bulk operations and security are also the factors in favour of Acquia Digital Experience Platform as compared to WordPress. They also offer …
Although Acquia Digital Experience Platform is an Enterprise solution like the others, it stands from competition because it relies on Drupal's Open Source community and is one of the first Cloud-native solutions so they're building on experience.
We decided to switch as Acquia/Drupal looked to have a better library of 'off the shelf' modules that could easily be integrated into the platform. The hosting and CDN options were comparable however I was personally happier with Acquia's close relationship with Cloudflare.
Acquia Cloud is more of a hands-off approach to Drupal hosting - get the code on the server and that's basically it. AWS on the other hand requires more specialized server and networking knowledge to support a site. Our company wants to focus on content deliver and not on being …
Can't compare apples to grapes. But in terms of "Drupal specific" hosting at enterprise level as a PAAS solution I think Acquia is the only one doing it at this scale.
Actually, Acquia Digital Experience Platform did not stack up against them, rather it was a great combination to implementing and configuring Cloudflare, the next generation Content Delivery Network (CDN) and different caching Architecture to embed with the Drupal Platform such …
We had some limitations with another provider: for example, multisite was not possible. We did not encounter any particular constraints with Acquia Cloud.
Compared to other products used, Acquia Digital Experience Platform offers a good balance between configuration flexibility and hosting implementation. Some platforms provide a similar service where it takes away the need to build the hosting yourself, however, they don't allow …
Acquia offers a much better page builder and personalization tool as native features than WordPress. Translation management is also a good feature from Drupal/Acquia, that is not managed well on WordPress.
The documentation that both Acquia and Drupal provide are vastly and immediately noticeably superior to Cascade. The customizability of the platform with drupal modules means that enhancements can be made very easily instead of painfully and by digging into a language there's …
It was not me who made the choice to use Acquia, but I understand the choice that was made. Acquia are expert at hosting Drupal sites, and developers don't need to worry about server maintenance, which removes a lot of work and allows them to focus mainly on code.
We use AWS (a variety of services inside AWS) to host our less than mission-critical sites. These are great options for sites that are relatively simple, technically, and/or that can tolerate occasional problems. However, Acquia Digital Experience Platform does provide a …
We went with the platform that the state already had a contract with to save time with deployment, and it has worked out. It had been used and vetted by the Executive Branch.
Acquia was chosen for its expertise in Drupal hosted websites. Our website however is either so simple, so dependable or both that we've never leaned on that specific trait to solve issues or iterate new website improvements.
If you use Drupal CMS, whether a simple or complex site, Acquia seems like a great partner. If you are considering moving to Acquia and Drupal, I would probably only go this route if you have Drupal development support. While the simple sites are easily maintained through Acquia's RA branch, I think that there are cheaper options for basic sites. Acquia is strong at supporting Drupal hosting, but since there will likely be a separate development team, it creates a bit of a challenge when something goes wrong to figure out if it is an Acquia problem (typically not) or a development problem (usually the case for our issues).
Acquia keeps the site up and available. I don't think we've had a second of downtime caused by Acquia.
Their administration UI makes it pretty easy to manage the websites at a high level. Check stats, change key configuration values, backup code and databases, manage SSL, create support tickets and manage development teams (users).
Their support team can do performance reviews of your website and give you tips for improving performance.
the support portal can be hit and miss. sometimes there are very helpful people who get back to you in a timely manner, but more often there's a lot of lag time for the ticket to get picked up and in between responses, which can also be less than helpful.
it seems like the different departments within acquia (support, management, build teams) don't communicate with each other.
because features are so dense and granular, sometimes the workflow or how they are connected can be really complex to access.
We're moving away from Drupal as a platform. Drupal 8 and 9 were simply too overburdened and difficult to maintain compared to other offerings. PHP seems like a dying language so we are currently in the process of migrating all of our Drupal 7 functionality and custom modules to a Python/Django/Wagtail platform. This doesn't mean Acquia isn't a great service, they are professional and top-knotch, but the only way we'd say with them is if I didn't complete the migration.
They are absolutely fabulous and have never dropped the ball in 8 years of us being on the platform. If it wasn't for Drupal 8/9 being unrealistically complicated compared to other offerings like Django/Wagtail we'd be still with Acquia and Drupal.
Acquia Cloud is more of a hands-off approach to Drupal hosting - get the code on the server and that's basically it. AWS on the other hand requires more specialized server and networking knowledge to support a site. Our company wants to focus on content deliver and not on being a "server support" organization, so Acquia makes more sense for us
Since the beginning of the website rebuild project, our agency gathered our needs and expectations. We also shared several technical or SEO specifications, and they have been able to fully adapt the software to our needs, in order to create a custom interface that we can easy use on a daily-basis.
When our site first launched, we had some negative experiences with throughput on our site. Eventually, this was resolved, but it took a lot of work with Acquia engineers.
Acquia Digital Experience Platform has helped us with a few situations where our in-house tech expertise needed the advice to solve a problem, even though this wasn't really within the purview of their support contract with us.