Acquia Digital Experience Platform vs. Amaxus CMS (discontinued)

Acquia Cloud is well suited for organizations and teams without the ability to support their own hosting, such as on AWS, Digital Ocean, etc. If a team has the ability (and desire) to manage it themselves, I'm not sure I would recommend it. However, if your team needs reliable, hands-off Drupal hosting, I would definitely recommend Acquia Cloud. Once a deployment pipeline is configured, it's very nearly set-and-forget as far as server configuration is concerned

Amaxus is well suited as a development platform and content management system for companies who have a dedicated, experienced development team because it has such complex functionality. It is not well suited for companies whose main content updater will be a person with limited development experience, because it is so hard to learn and understand how to use.

• Easy to manage multiple environments and a team of Site Developers and Site Administrators
• Easy and intuitive to conduct deployments, back-ups, rollbacks of code, databases, and files
• Useful add-ons such as Solr Search, Security, Site Monitoring, Migration tools, etc.
• Excellent and responsive support

• There is a lot of flexibility and power with what you can do.
• The client has a lot of power to make changes on their own without needing a development team.

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

• There is a huge learning curve for developers. All our new website builds were going beyond the timeline because of the learning curve.
• It is very complex and teaching our clients how to use it required several training sessions.

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.

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

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.

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

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 level of concierge service that I have appreciated when it comes to running a highly available web application.

I have used an in-house CMS which was very simple and only allowed the user to update very basic templated content, and I have used Sitecore, which is sort of like a middle-of-the-road. Sitecore is great because it allows for the user to have a lot of control over templates and updating content, but it's not so complex that it is very difficult and time-consuming to learn how to use, like Amaxus.

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.

• It's done a really nice job of allowing us to focus on business-specific needs as opposed to infrastructure/security issues. The platform is rock solid from a support and security standpoint.
• The ability to add automation and levels of personalization without having to break the bank has been a big boost to clients.
• Unfortunately, our adoption of Site Studio was short-lived due to some inherent restrictions that limited the level of customization we were able to do.

• It has a negative impact because it put us back on our timelines.
• It had a negative impact because our customers didn't like the learning curve to use it.
• It had a negative impact because it caused so much stress among our team to learn it.