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,…
N/A
Drupal
Score 6.8 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Pricing
Acquia Digital Experience Platform
Drupal
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Acquia Digital Experience Platform
Drupal
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Acquia Digital Experience Platform
Drupal
Considered Both Products
Acquia Digital Experience Platform
Verified User
Anonymous
Chose Acquia Digital Experience Platform
Acquia is the go-to platform for hosting drupal sites.
Much easier, less costly, and more value for the money. The support for the Acquia tools platform and operation are outstanding. Acquia has been a partner rather than a vendor.
We chose Acquia for a much better UI that gave non-analytical marketers and easy to use tool where they could create their own reports. The campaign side of things also had an easier to use UI as well, that made the targeting of audiences much easier.
Platform.sh is cheap and relatively easy to configure. The challenge they have when it comes to competing with Acquia is that they aren't a Drupal centric service, and don't have the same bench of Drupal products to offer, and don't have turnkey Drupal pipelines and support …
Very convenient because it's a suite of products built to work together and Drupal is open-source. The AWS products are very similar, but I really appreciate the Cloud IDE.
we have used pantheon in the past for some use cases but now we prefer Acquia over it the reason being the availability of different products to allow us to provide a complete digital experience. A product like a site factory, Acquia personalization, site studio, etc has really …
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 …
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.
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.
Drupal excels at allowing seasoned programmers to really get creative with marketing initiatives in terms of working with a theme and the core code. That being said, it is definitely much more challenging for average developers and front-end builders to use, especially at …
Drupal has some advantages and disadvantages when stacked up against Wordpress,, including that Wordpress is easier to user for beginners and requires less training to get started. I noticed that while using Drupal, more help and assistance was needed from developers to make …
Director of UX development, social media and SEO/SEM
Chose Drupal
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, …
I inherited Drupal from a developer who made the website for our nonprofit many years ago. It was increasingly obvious that it wasn't a fit for our organization, which has multiple staff and volunteers who need to edit or update the website but don't have coding experience. Wix …
Drupal requires less to no coding abilities to spin up sites. Even if someone is preparing to develop sites that require technical know how then Drupal provides role based systems to seperate developers from content writers. Drupal 8 and 9 now have a vast array of plugins. Now …
WordPress for sure has a bigger community, a lot of paid extensions which sometimes is easier to purchase and get started, a lot of pre-designed templates to get you going, but nowadays with the scale of the projects we've been working with, and the need for custom-tailored …
We use both, for different projects (Joomla and Drupal). Drupal proved to be more robust, more secure and more integrable with PHP applications. Drupal requires a more senior technical team but allows for more complex activities. It's great if you have a medium to a large …
We first had a WordPress-based website, that evolved to a custom third-party developed content management system. In both cases, that involved additional costs for any change request, any security or any scalability need. WordPress didn't meet enterprise requirements. That also …
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Drupal is far more usable and stable than Joomla!, and the developer community support is significantly stronger. While Drupal is often compared to WordPress, they are fundamentally different platforms, and in most projects, it's very clear when the requirements are beyond what …
We have used many content management systems — WordPress, Wix, Squarespace, ExpressionEngine, and more. Drupal is more powerful and flexible than most.
We did a comparison of Drupal against Joomla, WordPress, and Ingeniux. We found that its multiple themes available for web pages, user management, comment management, and form generation stands apart from its competitors.
I've used Wordpress sparingly when helping a client with an existing website. I find it much less powerful and robust, and frankly confusing. The way Wordpress websites are set up in the backend doesn't make sense to me after getting used to how Drupal is set up. They're …
Drupal is really the only well-supported open-source CMS that is designed for large, data-rich websites. There just really weren't any good alternatives. There are plenty of CMSs that excel at small to medium-sized websites. But for a large website with lots of structured data, …
Although Drupal is not the most used, it has great performance and is more used in professional projects. It allows us to expand without starting from scratch.
Security-wise and traffic-wise Drupal is built to handle a lot. While the other platforms mentioned ( mainly Wordpress ) are great and have a large community, I would only use Drupal for an Enterprise level platform to build a website on. I first learned about Drupal about 10 …
Drupal supports lots of devices like Mac, Windows, Linux etc. easily, and it is an open source product so there's no cost required. Lots of other products require purchasing, costing a high amount. The support system of Drupal is also good in comparison to other products. The …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
I selected Drupal because of the simplicity upon going live. "Simple" is not the word I would use prior to the site going live though. I have used Jumla (which I believe was part of Drupal as one CMS about 12 or 15 years ago). Jumla is almost identical in capabilities to …
In my mind, Drupal and WordPress are the top open source CMSes, and I rarely recommend not going with an open source CMS. WordPress can be great, especially for single developers, but I find that the code structure and extensibility of Drupal makes it superior for many use …
I've used Squarespace and Wordpress for other businesses, and Drupal was honestly selected due to cost. It does a good job of scaling across our organization - and many units have benefited from having a space to provide content. Squarespace is more modern, and Wordpress may …
Drupal has strong role-based permissions for users, powerful content blocks for editing, and granular customizing options in their views. For a company or organization requiring a lot of customization, Drupal can be a really powerful tool. However, Drupal does require …
It made it super easy to upgrade 300+ Drupal sites to the latest major version in 12 weeks, end to end. It is easy to deploy legal changes and updates to components at scale. Turnkey service to deploy new environments and to clone sites. There are no ecosystem lock-in principles for Customer service/success services and professional services for new approaches.
We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.
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.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
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.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.
It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Every time we have had an issue, Acquia support has responded promptly and worked with us as a team to solve the problem. The Acquia support team is global and we have literally had interactions with all of their support offices, yet the experience has been the same - top notch
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
We chose Acquia for a much better UI that gave non-analytical marketers and easy to use tool where they could create their own reports. The campaign side of things also had an easier to use UI as well, that made the targeting of audiences much easier.
Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.
The DXP tools can handle millions of requests and can scale automatically to fit your needs. We have clients that use only part of the DXP tools and have a small usage, but even in these cases they see great value in using tools like personalization and CDP.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Ours is a non-profit service, we are happy that people appreciate and recommend the site for its content.
FLEXspace.org rapidly grew to over 6,000 users from 1,400 educational institutions across 75 countries - it is a joy to watch educators contributing content and sharing ideas.
Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
Drupal allows us to rely on secure and consistently updated core code.
Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.