Overall Satisfaction with Linode
Linode is basically our provider for VPS solutions. Whenever we build a web application, we host it on Linode servers. It is used by the tech division of the organization. It basically takes our mind off the complexity of aws(ec-2 instances) and their not so transparent billing. I find Linode to be very simplified, clean and gets the job done with very transparent billing.
- The documentation to get you started is very good. Detailed enough to get you off the ground and not too bulky to bog you down.
- Pricing and Billing very clear and fair.
- The Linode platform is not complicated. You are just shown what you need to see at any point in time.
- I get a ton of emails about Linode server issues and because of the quantity of notifications, it's hard for me to sift through them to know what one is related to my server or which of them I should be concerned about.
- I need a notification that tells me my server is not being used and it's one wasting money. I don't get that notification.
- Apart from these two, I don't really have any cons for Linode. It's great for the things I do.
- Overall business objectives have had positive impacts from Linode.
- With just one server, I can host multiple projects for multiple clients lowering cost over time.
- Linode has got a good ROI.
- Amazon Elastic Compute Cloud (EC2)
I find using Linode easier to use when your use case is what you would do on an EC2 instance. I try to avoid AWS all together because of the complexity. Spinning up a server on Linode is pretty easy and clear as opposed to an EC2 instance. The charges/billing is also clear.
I have not really interacted with the customer support so it is going to be hard for me judge the overall support for Linode. This form however makes it compulsory for me to fill so I’m going to assume the customer support is great.
Total cost of ownership has been really affordable. The ability to host multiple project on one server is really a cost saver.
Linode is best suited when you are deploying a solution for a client and the client has no constraints concerning where it is deployed. The place where it is less appropriate is suggesting it to someone who is coming from an AWS background with a lot of buttons and knobs to turn.