Acquia Digital Experience Platform vs Kentico Xperience

• The Acquia Cloud Hosting (enterprise) provides a three-server solution. You have a Development, Staging (or UAT), and Production servers with a clear path of deployment straight up the chain. You may use Acquia's own Cloud Hooks, or their web admin UI interface to deploy to any or all of the servers.
• Git is one of the foundation services built-in to the management of the website codebase. Allowing a developer, or well-trained end user (university employee) to easily deploy a tag or branch to any one of the servers, makes it very easy for us to offload the server / account management to the school, while we focus on improving their site.
• Not only does Acquia Cloud provide a multi-datacenter failover disaster recovery solution, but they also maintain a multi-region failover as well, which allows for a fully redundant enviroment to be maintained in two geographic regions. No fear of losing any database changes or form submissions from students.
• Lastly, the onboarding process is constantly being improved, and as I have been a third-party vendor involved in many of our hosting negotiations, I have seen it firsthand. Each enterprise client is assigned a small team of engineers, technical leads, and a pseudo-project-manager to explain the process in layman's terms to the client (university / college for my example), but they also perform a number of code reviews and best-practice analysis of a site prior to launch.

Read full review

• I love the intuitive top and left navigation within the content management platform. I can easily find what section, sub-section, and page I'm looking to edit
• For creating content, the WYSIWYG editor is so intuitive; it feels like you're working on an MS Word doc!
• The tab for adding metadata in simple fields takes away the headache of having to hunt and peck through code to add H1 tag, page description etc.
• The image library is easy to edit and manage

Read full review

• Responses from tickets aren't always from the same person, and can vary in effectiveness of solving your problem
• While documentation is robust, it can be difficult to find exactly what you need
• Provided forums are not monitored frequently, and are not as useful as they could be

Read full review

• Kentico needs to invest in more enterprise class environment management utilities -- example: global CDN support via the CMS is sorely lacking. There are work-arounds, but it should be more elegant.
• The Kentico staging module could be improved to support the concept of bundled releases. Current staging module functionality is good, but could be improved.
• Kentico ecommerce support is a touch immature. While content management is superb, Kentico lags in this area when compared to many open source ecommerce engines.
• Kentico is lacking MVC support. 99% of the time this isn't an issue for the end-user or business user, but can be a hurdle for technology teams depending on the team's makeup.

Read full review

• Our website isn't a revenue generator, so we don't have specific ROI calculations.
• The new website is helping us move off of a legacy on-prem server environment. The reduction of cost in maintaining those will be beneficial.
• We have had to invest in some training for our developers to learn Drupal.

Read full review

• Kentico has enabled faster speed to market for SMEs. They are empowered to enter content them selves while still having that content go through editorial review to ensure tone of voice and brand are maintained.
• Deploying Kentico has freed up web developer resources from manual content entry enabling them to build more useful solutions to support the business efforts
• Tapping into the Kentico event pipelne allows us to trigger external system events when product content is published.

Read full review