Percussion CMS vs. WP Engine

Best suited for large organizations where everyone knows how to deal with Java in an increasingly Java unfriendly world. Said organization should be willing to pay a huge price for a piece of dinosaur technology

Incentivized

New users to WordPress can rejoice with a very hands-off hosting approach. If 100% uptime is not essential, you can get breakneck speeds with minimal tinkering using their platform. If you need to get up and running quickly and scale as required, the cost-benefit is here, although you need to pay a lot to get the most from it.

Incentivized

• Separate CMS environment publishes to remote server environment - great for security
• Highly scalable
• Full scale workflow allows for custom routing, approving, etc..

Incentivized

• I love the database backups and how quickly & easy it is to restore from an old backup point. This gives me & my clients confidence that any change can be rolled back.
• The built in caching & CDN mean that I have to spend less time worrying about the speed of the server & site. The caching has some side-effects that take getting used to (on-page dynamic PHP code sometimes needs to be moved to API endpoints), but this is true for most caching systems.
• They have really good support for multiple environments. It's very easy to have separate production & staging environments. It's also very simple to deploy from staging to production, making product launches and large scale website copy changes much easier to coordinate.

Incentivized

• One word: JAVA! We don't live in the 1990's anymore! An AJAX/DHTML environment seems a long time coming.
• Horrible end-user experience, learning curve. Our end users' inability to easily use the archaic, Java-based interface, means they send the web developer their content requests. This creates a huge bottleneck and completely defeats the purpose of a CMS.
• Image mangement and integration with content is aweful and time consuming. An image processing tool called ImedImage was developed for Percussion at one point, and left completely stagnant with very little support.
• Implementation is extremely complicated, given the complexity of the system. Sure, scalability is a good thing, but there is very little out-of-the box function. Don't expect to implement a site as quickly as with other CMS platforms.

Incentivized

• The user interface is not very intuitive, which means new staff members require more training than I'd like.
• The way they manage production/development servers and FTP access is somewhere between nebulous and tragically unique.
• Their premium pricing is surely worthwhile, but it is significantly higher than virtually all of their competitors, without much obvious distinction in feature sets.
• Some very basic features like spinning up a second instance require a PHONE CALL to their BILLING department to enable. What is this, 1990?

Incentivized

I was in a situation where I had to bolt Wordpress on to an existing infrastructure that could not support it. If I ever end up in that situation again, please kill me. Other than that reasonably common use case, I don't think it offers a lot of value over robust shared hosting, virtual private server (VPS) or dedicated servers.

It took very little time to learn their dashboard for managing WordPress sites. Their built-in tools are really well done, and the addition of security and CDN tools is great.

Incentivized

Support is generally great. Enterprise support is fantastic, with little to no wait times. I find that chat support can almost always take care of the problem without escalating to a ticket for a higher level of troubleshooting. The chat support for many other hosting providers can only handle basic issues. This is a big bonus for us to get quick and helpful answers.

Incentivized

No contest. I can't wait to get off of Percussion CMS.

Incentivized

For Acquia and AEM the major differentiator was the cost for WPEngine was significantly lower and we could use the more common WordPress CMS. AEM is better for large marketing sites that integrate with the Abobe Marketing Cloud and we didn't feel we could support Drupal on Acquia. AWS EC2 is a viable option if you are going to self support and maintain your own WordPress experts. We felt that the value from WPEngine was they handled the support and the WordPress security patches and knowledge beyond simple theme usage. Pantheon was the closest in matching but we felt with our large installs that the hosting model for WPEngine was more cost-effective than the Container architecture for Pantheon

Incentivized

• We are locked into Percussion CMS simply due to the expense and complexity of migrating to another solution (and the lack of time and budget to do so). I long for the day when I am no longer required to support Percussion CMS, to say the least.

Incentivized

• Positive: We've been able to scale up more easily as adding new sites has been easier.
• Positive: The load speed improvements we saw were immediate and have not let up.
• Negative: Adding advanced security and other tools to a multiple sites is expensive.

Incentivized