Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Liquid Web
Score 8.0 out of 10
N/A
Liquid Web is a fully managed hosting service, boasting VPS hosting on the Storm Platform, and cloud dedicated hosting on the Storm Platform. Liquid Web supports managed WordPress, managed WooCommerce, VMware Private Cloud, as well as HIPAA and PCI compliant hosting, high availability database hosting, and dedicated or server clusters available for a variety of purposes, as well as websites.
$19
per month
Pricing
Drupal
Liquid Web
Editions & Modules
No answers on this topic
Managed WordPress
$19
per month
Managed WooCommerce
$19
per month
VPS
$35
per month
Magenta Cloud
$49
per month
Cloud Dedicated
$149
per month
Private VPS Parent
$149
per month
Dedicated
$169
per month
Cloud Servers
$265
per month
HIPPA
$343
per month
Server Clusters
$743
per month
High Performance
1,127
per month
High Availability
1,448
per month
Database Hosting
1,498
per month
VMware Private Cloud
1,599
per month
Offerings
Pricing Offerings
Drupal
Liquid Web
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Liquid Web
Features
Drupal
Liquid Web
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Liquid Web
-
Ratings
Role-based user permissions
8.174 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Liquid Web
-
Ratings
API
7.264 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Liquid Web
-
Ratings
WYSIWYG editor
6.171 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
00 Ratings
Admin section
6.878 Ratings
00 Ratings
Page templates
5.577 Ratings
00 Ratings
Library of website themes
5.468 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
00 Ratings
Form generator
6.372 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Liquid Web is suitable for serious users who have high end web applications or critical business oriented websites. cPanel and WHM comes out of the box with almost every server you buy. And if you don't have time to manage your own server, Liquid Web will suit you well. Their support is awesome. They help beyond the scope of the support. I had to migrate almost 25 big sites to another Liquid Web server, the support guys made it so easy for me.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
We evaluated Kinsta and WPEngine. Both offer great platforms but the lack of solid phone support and the substantial difference in server resource allocation made Liquid Web a clear winner.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Liquid-Web has made it easier for me to take my focus away from handling constant server issues to being able to focus on my actual job in managing our websites. While there may not be a concrete number for this scenario, being able to perform my tasks more efficiently definitely helps company growth in the long run.