Akamai Cloud Computing (formerly Linode) include scalable and accessible Linux cloud solutions and services. These products and services support developers and enterprises as they build, deploy, secure, and scale applications.
$5
per month
Drupal
Score 7.0 out of 10
N/A
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
Webflow
Score 8.7 out of 10
N/A
Webflow is a Website Experience Platform for modern marketing teams, used to visually build, manage, and optimize websites that offer both the consumer experience teams expect and enterprise-grade performance and scale.
$18
per month
Pricing
Akamai Cloud Computing
Drupal
Webflow
Editions & Modules
No answers on this topic
No answers on this topic
Basic
$18
per month
CMS
$29
per month
Ecommerce - Standard
$42
per month
Business
$49
per month
Ecommerce - Plus
$84
per month
Ecommerce - Advanced
$235
per month
Offerings
Pricing Offerings
Akamai Cloud Computing
Drupal
Webflow
Free Trial
Yes
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
—
Up to a 22% discount available for annual pricing.
While SiteGround, GoDaddy, and DreamHost all offer ease of use and work OK when they're working, their performance is not consistent. All three can become very slow for even very low traffic sites. Linode, in comparison, offers much more consistent performance and any issues …
Akamai Connected Cloud Linode would be a good service to host a content delivery network (CDN) because of its edge network but I'd prefer not to use Akamai Connected Cloud Linode for tasks that need GPU power such as Machine Learning or Artificial Intelligence (AI) because Akamai Connected Cloud Linode lacks deep GPU compute compared to AWS or Google Cloud or Microsoft Azure
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.
Since the purpose in my case is to build a small professional looking site to present project outcomes and other research, I can create custom fields and design experimentations. Webflow builds sites that are super professional, with many amazing templates that don't look cheap. Additionally, I can test responsive layouts. Apart from this, I used 1-2 static pages to illustrate key findings for example what a multilingual site could look like with screenshots without needing CMS in free version, which are all the valuable skills to acquire. Compared to WordPress, Webflow is expensive with limited free features, although it has really cool additional features that will make the site I build stand out.
Saves time- because I don't have to do double entry of content.
It saves money. I like that it is an all-in-one system, so I don't have to host elsewhere.
Flexibility - Webflow provides me with a lot of flexibility in my webpage design, allowing me to adjust pages as needed, depending on the content types.
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.
Brand recognition is still behind WordPress, which can make it a challenging sell for clients looking to play it safe in their CMS decision.
The CMS is ideal for smaller datasets, but higher content sites introduce some minor challenges.
Alignment between designers and developers is key prior to implementation. The flexibility of the platform requires careful planning to avoid over-engineering.
I've been with them a long time. They provide me with the capabilities I need coupled with knowledgeable support that's not pay-for-extra. However, if I move to a non-Linux OS, the level of support by necessity will drop off. I can still ask questions about the infrastructure but I my ability to ask about OS features will decrease.
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.
Simple and clear, no BS interface. From a design perspective it's no Apple or Stripe, but it does what it needs without making me want to stick a fork in my eyes, like when being forced to use Azure, AWS or GCP.
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.
Webflow is very easy for a beginner to get started with and achieve good results, but to achieve an expert level of understanding requires experience and some web development knowledge. HTML5, CSS3 and JavaScript knowledge aren't required to use Webflow, but an expert will know BEM class naming patterns, be able to create reusable elements and design systems, and add 3rd party integrations that require custom code.
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
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).
In my experience, their customer service is an absolute joke, I tried reaching out to them they took forever. I had to keep following up with them as if they never received it in the first place. It’s a new platform, so guidance is needed. Tried the university they offer, in my opinion, it is completely useless, I would just completely move on from this website.
Servers are well dimensioned and price performant. Of course one always wants more, so if they were to upgrade their hardware for the same price I'd consider moving more workloads. Networking - never had an issue. Hardware speeds - disks are fast and can grow to great size.
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.
In my opinion, it is horrible, the rendering takes forever. I have the newest MacBook and the platform will still lag and slow down on me. I’m not a developer, I am a designer which makes it worst because I am using the features they are providing not extra coding features. In my opinion, it is a horrible platform really, stay away.
Support was excellent and fast. The documentation is extensive and helpful. I learned many things from their online documentation. I did not contact them by phone, but email took a day or less. Complex problems would probably need a service contract. I liked the friendly and polite tone of the support.
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 haven't had to engage them from a support perspective; however, there is a considerable user community for tips/ideas/troubleshooting and the like. I believe the Pro plan supports additional resources but we didn't find that the cost justified the outcome. Overall the need for support has been relatively minor.
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.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
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.
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
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%
We switched to Linode from Namecheap due to poor uptime, and never had any issues with stability ever again after switching. We also cut our costs in half by switching. We compared Linode to DigitalOcean and Vultr, with the primary factor that caused us to go with Linode initially being their documentation. After using Linode for 3 years, their amazing support is another reason why we wouldn't consider anyone else at this point.
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.
A lot more design control and easier to create a custom site, and then also to scale that site going forward. There's a lot about WordPress I miss, though, when it comes to managing a blog—user permissions, SEO control, edit HTML version of posts.
Although I use only a fraction of their product offerings, the total set makes scalability an easy goal to shoot for. As I said, I have a few customers that use the services my Linode provides...and I like it that way. However, should I need to scale up, I can...without incurring any more cost than I need to.
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.
I feel it doesn’t perform the way it’s supposed to and it doesn’t have any beneficial factors to it. In my opinion, there is no reason to use a platform like this when Wix and Shopify, and WordPress exist. I believe Webflow is a platform that shouldn’t exist and it’s only popular because of the hype it received. I tried it and hate it completely.
