DreamHost vs. Percussion CMS

If you're not too technical, don't want to spend time managing a server and want something quality while sticking to a budget, DreamHost is the best it can get. We may be able to save money by switching to something like AWS, but for our usage it doesn't totally make sense even with potential cost-savings and improved speeds. The support and ease of use cannot be overstated here.

Incentivized

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

• Dreamhost has very good hosting plans that can be matched for different levels of hosting needs and expected web traffic bandwidth.
• The hosting service is very friendly for coders and those needing to tinker "under the hood" with their sites.
• Great uptime service with limited technical issues.

Incentivized

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

Incentivized

• There was one instance where DreamHost support caused unnecessary downtime because they misread my request. Unfortunately I don't have access to that account anymore (it was an old employer) so I don't remember the details. To avoid this, make it very clear whether you're just asking a question or want support to handle it (they can be quite eager to fix the problem even when you've just asked a question), and be VERY clear what you need when doing the wrong thing may cause serious problems.

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

We have every intention of staying with Dreamhost, but we are a tad concerned with the company's recent involvement in high profile litigation and controversial topics. While we don't take a position one way or another on what type of content they should host, one concern we have is that repeated attacks on their infrastructure have caused significant downtime during business hours for us, and that's something we'll have to take into consideration going forward.

Incentivized

Whether we're calling in on the phone, live chatting or emailing, we get immediate high-quality, native English-speaking support. This cannot be overstated when it comes to hosting, because support tickets are usually time sensitive and high stress. I've always had great experiences with the limited times we've needed to use DreamHost support. We've dealt with support for many other providers and no one comes close to DreamHost.

Incentivized

We've tried a few other WordPress-specific hosts, as well as other shared hosting providers (Rackspace, WPEngine, and others). We have found that DreamHost gives the best balance of cost, performance, and features, for our needs. All vendors have their own pitfalls and shortcomings, and DreamHost isn't without its own, but it works for us.

Incentivized

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

Incentivized

• It's a great product for a relatively cheap price
• We can offer a simple hosting solution for our clients
• Even the VPS (virtual private servers) are very affordable and you can manage it as you wish (SSH access)

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