Acquia Digital Experience Platform vs. Platform.sh

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.

Incentivized

In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.

Incentivized

• 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.

Incentivized

• As this is a PaaS it mitigates the complexities of a Cloud infrastructure like Acquia
• We are easily able to integrate our sites with different technologies like Python and Rest
• Helps us in providing Continuous Development cloud deployment hosting solution

Incentivized

• 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.

Incentivized

• Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
• As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
• During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.

Incentivized

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.

Incentivized

It's a great user interface. It's always being updated and I've never noticed a bad update that increased the complexity or reduced

Incentivized

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

Incentivized

It was implemented when I got there. I don't know how it was prior.

Incentivized

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.

Incentivized

In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.

Incentivized

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.

Incentivized

• A reliable platform = happy user base!
• 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.

Incentivized

• Continuous development for sites in build has been fluid
• Platform.sh is really cost effective when comparing to AWS or Acquia Cloud
• On the other side, lack of server side support demands a big learning curve from its users in my opinion.

Incentivized