Akamai Connected Cloud (Linode) Reviews

The primary use cases involve renting virtual private servers for our infrastructure, which is used for the development of software, website databases, websites, and some infrastructure such as for audio and video conferencing.

The main purpose for using their virtual private servers is for our in-house development program.

We use a Linux environment for our website database applications.

Linode has done a lot of help to us when it comes to streamlining anything where we need a server. Whether it is development servers or even servers for clients, Linode has helped us a lot.

It has helped us to accelerate our innovation, although there are similar services available so we didn't choose Linode mainly for that. Nonetheless, it certainly has helped because we don't have a core infrastructure. Obviously, all of the development that we do internally is happening on their server. This means that it's very important for our innovation and development, but other services would be able to compete with them, so it's not an exclusive advantage.

We choose Linode because they are very Linux-focused with their operating systems. It is very Linux-friendly and Linux-oriented. Mainly, in the end, it's all about vendor lock-in. If I compare it to Amazon and Google Cloud, they have a vendor lock-in, and we want to avoid that. This is something that Linode is very helpful with. They have a very standardized open system, which is easily configurable.

It is difficult for me to assess the price to performance ratio of Linode compared to other product providers because I don't have much experience with them. But, at least compared to our self-hosted servers, I think they have very good uptime and response time.

The DNS management tool is helpful. 

The virtual machine configuration tool is very helpful for setting up a new server or for modifying an existing server. It works very reliably.

It is very important that Linode offers a well-focused set of cloud computing services. They have a lot of options for different products which work well together. I saw the extended steps that products provide in the past, but I don't see a need to expand it anymore. I think it's perfect as it is right now.

I find it important that they offer worldwide coverage using multiple data centers, but from my point of view, they already have very good coverage. For example, here in Thailand, which is in the Asia region, it could cover Singapore, Japan, and also a little bit of Europe. It's important because we deal with a lot of international clients, but there is no need to extend these exhaustively. They are very well set up already.

They recently changed the web interface and although the older one did not look as good, the new one is less responsive. For example, when you changed something, it was instant. The new interface was really bad when it was first released, and it has improved, yet it is still not as responsive as the older one. I have considered whether being in Thailand makes a difference, although it is still a relative comparison. This is something that I have written an email to them about, and they are working on improving it.

I have been using Linode for two and a half years.

We use the Virtual Private Server (VPS).

In general, the stability is very good. However, there was recently a nasty problem in Singapore, and it seems to have service interruptions more now than in the past. I think that at some point in time, they will upgrade the Singapore data center and the stability will improve. For us, it's not really relevant because we don't have large scale, or clients in large numbers, and not around the clock. Ultimately, the interruptions don't affect us too much.

Our company's scalability is perfect because we can just upgrade to the next level of server available. Within 10 to 15 minutes, it will upgrade and everything is there. Even if we grow a lot over time, their servers are still big enough for our requirements. We wouldn't need anything on the level of Amazon or Google Cloud.

There are only two people in the company who are involved with the servers.

We use Linode for all our servers, with respect to ones which we host in-house or host for clients in-house. So if we need a commercial VM, we will set up a new Linode. From that point of view, it is sufficient for our use case.

In the future, if we increase usage it will be mostly for new clients that need database applications, cloud space, servers, or more resources. I expect it would be a steady but low increase in the resources that we need.

In terms of end-users, it is difficult to estimate how many use it because there are several websites and databases. There are probably no more than 100 in total, which includes all of our customers.

I have been in contact with technical support a few times. It was always via email and they were very responsive. There is nothing to complain about when it comes to their support.

I'm certainly thankful for their support, which always has a human answering my inquiries. I find that Linode is very good because when I've sent an inquiry, it's almost always dealt with by a human and it doesn't involve working with FAQs or automated responses. I find that very good. It is important because, with most issues, I can resolve them myself. It is only the very high-level technical issues that I have no idea about and need support for. It is very good compared to other services, especially Google. With other services, it is sometimes very difficult to get a human to respond to your inquiry.

Prior to Linode, we only had in-house servers. I started using Linode more intensively when we opened the company in Thailand, almost three years ago.

The initial setup is very straightforward. It is perfect, although I might ask for more configuration options, making the setup a bit more complex. For now, however, it is fine.

Normally, the initial deployment takes between five and ten minutes. Using the web interface, it is very fast to deploy. However, afterward, I need to check the parameters. This is something that I think could be improved if they allow a few more options through the web interface.

In terms of an implementation strategy, we didn't really have one because we don't have many servers. We only have a handful, so at this point, we just get a new Linode when we need a new one because our capacity is full. There are a few things that need to be done such as changing the root password, setting up additional system users, installing a few packages, and setting up standardized software for our company. However, we don't have any official documentation for the steps we follow.

I take care of the deployment for each Linode, and I have another person who supports me with the maintenance. We try to optimize everything as much as possible, especially in the maintenance phase. I also set up the updates as part of this effort.

The maintenance involves just logging in, doing some checks, and running some maintenance scripts. It's a new product, so this is part of our manual monitoring.

We see a return on investment in terms of time saved for managing our infrastructure.

If I compare to in-house servers, we don't save a great deal of time. I would estimate a 10% time savings in general and slightly more for setup and maintenance. Over time, it would become pretty substantial.

Linode has very good pricing. There might be something a little bit cheaper but I find it very fair and competitive, and nothing to complain about. Given the broad set of choices and options, I wouldn't ask for cheaper prices.

I find a simple pricing model important, and I think that's also one of the reasons why we decided on Linode. I'm paying a simple, per-hour rate for the service, with no automatic scaling-up of the pricing. This is extremely important because, with Google Cloud and Amazon, part of their infrastructure does bill based on usage. We didn't want this but instead, wanted to be billed on a fixed monthly rate. This allows us to keep an eye on the monthly fixed costs. It puts us more in control.

We have a few instances where we use a lot of resources on a few servers, and with the fixed price, I think that we save money compared to other cloud-hosting providers who bill according to usage. Even if we don't save much money, it allows us to plan very well ahead.

When we set up the company, we took a look at the options for commercial providers and we decided on Linode. These included Amazon, Google Cloud, DigitalOcean, and a new, smaller local one, based in Switzerland in Europe, which is where our mother company was created. The one that compared most closely was DigitalOcean.

I don't recall all of the details but we found from reviews that Linode had better support for Linux, and it is more developer-friendly. This may have changed over the past three years, but when it was time to choose, these were deciding factors.

We also knew about Microsoft Azure, but they didn't have good Linux support at that time. As such, we didn't look at them further.

The biggest lesson that I have learned from using Linode is the importance of stepping up production-ready infrastructure.

My advice for anybody who is implementing Linode is to start with a small server, work with it, and then scale up later. This works well because scaling up is really easy. If you plan on very large infrastructure, conduct a PoC first. In the case where you are just hosting websites, you can start with the resources for 100 or 200 users, and then scale up as the demand increases or the size of your company or user base increases.

In summary, this is a product that meets all of my expectations for a cloud service in terms of functionality, scale, and pricing. It is perfect for our scale.

I would rate this solution a nine out of ten.

I have a single 4GB model Linode and I use it as a personal server. I originally set it up to act as an email server, just for my own personal vanity domain. I don't use it for that anymore, but it's proved to be useful for many other things.

Right now, I run a Minecraft server on it and I also use it for a little bit of software development. I also use it as a jump host, if I need a stable place to SSH from my laptop to get to other online resources. It means that I only have a single point that I go through to get to the other stuff that I need.

I would say it's very important that Linode offers a relatively small, but well-focused set of cloud computing services because it differentiates them from AWS, Azure, and Google Cloud by being focused and by having a more personal touch. I could probably get the same compute power for a little bit less from other providers, but the value of the continuity and the high quality of support is worth it. It's rare that I need to reach out to support, but when I do, the support is great.

Even though I use it for personal use, some of the things that I use it for are in a software development capacity. For example, the ability to experiment with running my own Mercurial server, Git server, and source control servers on this machine have leveled up my own knowledge of those products in a way that I think a more managed solution wouldn't. Having the tools in-hand of just a Linux box that I can play with, and that I can wipe and reimage at will, is more useful than a physical machine by virtue of that virtual rewriting. It is also more useful than a more abstracted managed service, just in that I can get my hands dirty and do rapid experimentation.

Linode has helped me to accelerate innovation and even though I'm not using this in an enterprise way, it has improved the way I innovate with respect to personal stuff. For example, it has helped with the things that I'm trying to learn and the things that I'm trying to do. Setting up a Minecraft server is a good example of that. Being able to read some of the documentation that Linode has about setting up a Minecraft server on your VPS, and just learning and figuring stuff out, has been valuable.

The most valuable feature is the static IP address, which has been very helpful for being able to log into the same address over the course of more than a decade.

Another useful feature is being able to have multiple system images that I can play with. I mostly use Ubuntu Linux, but if I want to play with a new version of Ubuntu, I can pretty easily add that. It's been super useful to upgrade my system over the years.

I just recently started using the Object Storage and Backup features, as well. Having good backups for peace of mind and disaster recovery is very nice as well.

Object Storage has been key, for me. I don't have a strong notion of exactly when Linode introduced Object Storage, but it's been very useful for me, for instance, in backing up my Git server, in addition to the whole node backup. The fact that I can interact from the command line with the Linode Object service to back up specific datasets, is super cool. I know they didn't have it when I first started using Linode and I think it's been introduced fairly recently, within the last couple of years.

The Linode documentation is superb. 

I would like to see more seamless integration with backup, although it's pretty easy to do.

Having more on-demand features would be helpful. For example, if for a little while I wanted to have four Linodes instead of just a single one, it seems like it's a little bit more difficult than spinning up an EC2 instance in AWS. It isn't a lot harder, but it could be improved nonetheless.

I have been using Linode for more than a decade, since 2008 or 2009.

The stability is excellent. It's very rare that there is an interruption in the service. I think that the reboot notices that I get, that aren't related to me doing stuff, are less than one a year. I think, in some cases, it's been four or five years between needing to have any kind of stability-related events on the machine. I can't think of any outages in the entire course of me using it, that anything with any kind of significant impact.

Part of the thing that I value about the single Linode that I have is that it is a very steady, stable known quantity. I don't have to worry about all the institutional weight that I do with interacting with AWS, which I do a lot from work.

Thinking about it from an operations point of view, I think that I would have a bit of a harder time scaling in Linode than I would in AWS, but not a whole lot harder. Given the Kubernetes support, I would imagine that that makes the process even easier. That said, I have not tried Kubernetes so I really have insufficient data to be sure.

It's not likely that I'm going to significantly increase my usage in the future. I might bump up to a higher size if I find that I need more CPU or RAM. Or, I might play around with having two to four Linode nodes. But beyond that, it's unlikely that I'm going to expand much.

I will definitely keep using Linode for as long as it is as stable and reasonably priced as it is, but at a steady one machine for my personal purposes.

The support from Linode is great. All of the times that I've reached out, it's been through email or through the web portal. It's always felt good and it felt like the person responding understood what I was asking about and solved it very quickly.

In terms of flexibility and overall responsiveness, the support is very good to excellent. Certainly, everyone that I've interacted with, in the fairly rare occasions that I do need support, have been very knowledgeable about the product and very good at understanding what issues I'm having and how to solve them.

I would say compared to AWS, AWS support varies a lot in terms of responsiveness and whether you've got a paid support plan. Sometimes, it does take a fair bit of back-and-forth with AWS support to get to the crux of the problem. I've never felt that back-and-forth was as necessary, that we get to the crux of the problem and solve it much more quickly with Linode.

Prior to using Linode, all of the machines that I had managed were all physical. I had my own personal machines and machines that I built for work, but they were all physical PCs or other architectures that I had to actually open up a case, and if I needed more RAM, I had to put the sticks in myself.

In comparison to a physical server, Linode has definitely saved me money. I never want to build a server again. Basically, if you build a physical machine and it is obsolete within two to five years, you've got to buy and recreate the whole thing again. Generally, the hardware is going to get cheaper over time, but I think that unless I were really putting a microscope on getting the cheapest components for building, Linode will cost less.

In some contexts, albeit not mine with just one or a few machines, it would make sense to build them. However, not having to worry about it and just letting Linode take care of the hardware upgrades is probably saving me money. I don't know if it would save a very tightly tuned hardware IT team money, but that's a completely different scale than what I'm looking at.

Linode was my first experience with virtual cloud servers and virtual machines, in general. Not too long after I started using Linode, I did start doing more with VMware, with an on-premises, physical server hosting multiple virtual machines. It was not too long after that when I got into AWS for work.

I found the initial setup to be fairly straightforward. It's so long ago that the details are fuzzy but I recall that I set up the account, chose names for things, picked which size I wanted, and then launched it. Within, what at that time, was an astonishingly short amount of time, I was able to log into it. It's just gotten better from there.

I didn't require an implementation strategy, although I think that's peculiar to using it as a single thing for personal use. I had the notion that I wanted a persistent Linux machine that was always on, and that I could get to from anywhere, and Linode seemed to fit the bill.

Over the years, I've used it for a lot of different purposes and it's adapted well to that. So I would say in this case, I didn't need a whole lot of planning. If I were to use Linode for a more complex deployment, I would want to plan it out, figure out what the costs are, figure out the network topology, and the other relevant details.

Linode offers worldwide coverage via multiple data centers, although I don't personally need that. It's a very attractive feature for sure, but since I just have the one virtual private server and it's just for me and for my friends connecting to it, I want it to be geographically close to me to have a low ping. I think it's located in New Jersey, and that's good for me, being in New England. While global coverage is not super important to me, in so far as it contributes to the health of Linode in general, I'm all for it.

The pricing model is simple, and that's one of the reasons that I've stuck with Linode for so long. When I was on the $20 Linode, I knew for a fact that on the first of every month, my credit card would get charged $20. That meant my Linode was available constantly.

At this point, I'm paying more like $35 per month for a slightly bigger machine, and the backup, and the object service. But again, I know that it's exactly $35 every month and I can budget for it. The simplicity and the consistency of that billing and pricing are quite valuable to me. Whereas with AWS, it's a crapshoot. The on-demand pricing means it's flexible and I only pay for what I use, but it's also much less predictable.

It is tough to determine whether using Linode has saved me money compared to what I would pay with other cloud providers. I don't think it has on a pure numbers basis, but in opportunity cost and higher-level budget planning, I think that the consistency probably has saved me money. I would have spent more time trying things, allocating things that I might not need, and so on. Ultimately, it saved me capital in the long run but it is not necessarily something that I can put a dollar figure on.

In comparison to everything else, predictability is the key aspect of the pricing model. With it being a known quantity that I can budget for every month, it frees up brain cycles to do everything else.

In my personal capacity, at this point, I have my Linode and I have a personal AWS account, and I use them for different purposes, but to similar degrees, or similar magnitudes. I find that just looking at it from a strict CPU and RAM horsepower perspective, EC2 is just marginally cheaper, but there are different features that I value in different places.

I took a brief look at some other things like Azure, Google Cloud Engine, and DigitalOcean, and I found that when I was looking, and this was probably about five or six years ago, that a lot of things that I wanted were pretty comparable in terms of capabilities and pricing. A lot of it came down to what I valued, in terms of the positioning, and support, and documentation, where I very much like Linode's documentation, especially, and support.

Of the others that I evaluated, DigitalOcean seemed the friendliest. And then, AWS and Azure were the behemoths, the 800-pound gorillas in the room.

The biggest lesson that I have learned from using Linode is the oldest lesson, which is just that a virtual cloud server has the availability and the flexibility that I couldn't get from physical at the time, or even now, for that matter. It's a key component in having something that's useful, having a machine that you can log into and do things on, in a consistent way, regardless of where I am or even what machine I'm connecting to it from.

My key advice for anybody who is looking into Linode would be just to dive right in. Pick it up and play around with it and if you find that it's not for you, try something else. But if you find that you love it, keep going.

In summary, Linode is a good product and I've been extremely satisfied with it for exactly the purposes I use it for. I have been pleased with it since I started using it.

I would rate this solution a ten out of ten.

Initially, my use case was to have a server platform running that wasn't tied to the company that I worked for at the time. I wanted a solution where I could access our product and services from a platform that had no relation to our own. I was performing testing, as if coming from the outside as a customer of ours, having no network conductivity on our servers or anything like that. That was the first use case.

We realized that it was pretty handy to have a cloud platform that didn't reside in our network, so what happened next, when we moved our data center from Dallas to Florida, we employed the platform to facilitate it. We used a temporary name server and temporary mail server and another temporary server to keep some of our core services running while we were physically moving servers across the country.

When I moved and thought of this company, I used Linode as a temporary general server, as a holding place for all sorts of things. This included web services, our website, and other similar things. But then when I moved most of that to other providers, I still kept some of the web services running. So, it's like an application server for customers.

Basically, if I provide a service to a company, such as a mapping service for a logistics company, then my domain name can be used to access applications on the Linode server. I have a couple of instances there right now that are performing this task.

Linode offers worldwide coverage in multiple data centers, although this is not important to me because I only use the US data centers. In fact, one of the reasons that I stick with Linode is because of their US presence. Right now, I am only using the data center in Dallas and this specifically gives me a US presence.

Having a long-standing relationship with Linode, it's been easy to develop and subsequently deploy services provided to our customers on their platform. Without it, I would have to use a different platform like Amazon or Microsoft Azure, or something like that. Where this makes a difference is that it would take longer to get to market in the case where one of our customers requires a change or a specific feature that we don't normally provide. The fact that it is easy for us to modify that quickly and without much overhead means we can implement it. Essentially, the flexibility that Linode provides extends through us to our customers, which is a bonus for them.

The most valuable feature is that they are flexible and easy to get a hold of if I need something. For example, if I need to provision a server quickly, or if I need to change something, or if I for some reason need to do something that's outside of my plan that I pay for, I can contact them quickly and always get a hold of someone and always get a solution for it. I don't know if this is typical or if it's just based on having been a customer for a reasonably long time, but that's the main reason that I stick with them. It can be summed up by saying that they provide a much better level of service than a larger company like Amazon. I use Amazon as well, but it's a different experience.

Because they are a smaller company, they do not have, for example, all of the ways for authentication that Amazon or Azure has. However, that's not a downside for me because it means it's less complex to implement for us. So, while it is simple compared to some large solutions, that's a benefit to me and not a drawback.

I began working with Linode in 2004 or 2005 when I was working as a technology officer in my former company in the US. I still use the product but it for my own business in Europe. 

Linode has been very stable. Every time there is an outage, they will always contact me beforehand to let me know that there is something planned. I've never had an unplanned outage, so it's positive.

Scalability-wise, it has improved over time. Initially, it was harder to deploy complex servers and then grow them. What we'd have to do was shut them down and then scale up and then deploy a whole other server and then move whatever we had. This could have been an application or a number of applications, which were all moved to that new instance.

As it is now, you can just do it on the fly. But having said that, I don't really scale up and down very much. I generally know what I need and then deploy it. After that, if I ever discontinue something, we turn that off.

So in summary, I see that it has improved, but I haven't really used it much.

In my company, there are between three and five of us who work on it at any given time. Each of us performs multiple roles but in this capacity, we are system administrators and system engineers.

At this point, probably between 20% and 25% of the server and cloud needs are provided by Linode. As the business grows, the usage will grow, although it's always going to be proportional to what we have now. Given that 2020 was a pretty crazy year, it is very hard to predict growth right now.

I also use Amazon but It's a less personal experience. For example, if I'm abroad and I can't take care of something until I get back, I can't call Amazon and say, "Hey look, can you delay my invoice for two weeks, because I'm in Bangladesh and I have to deal with something," because my company is not big enough for that. With Linode, it's perfectly fine. You can just call them and they'll take care of it, which shows a high degree of flexibility and a high level of service.

The initial setup was not very easy, although when I set it up, it was quite some time ago and things were more difficult on the web at that time. I think that the difficulty of the installation has been commensurate with the level of technology on the web at the time. It is easier to do now than it was when I started.

They have the Linode manager, which is an online interface that works by you starting with selecting a service. You select all of the things that you want to have included in your service, whether it's a bare metal server or a virtual server, or whether it's provisioning new storage for that server that you already have. After it's selected and it's up and running, you have the same KVM that you do on other services. For example, you have a virtual screen as if you were in front of your machine in the data center.

We're such a small company that we don't really do this type of financial breakdown. We're just happy if we make a little bit more money than we did last quarter. Nonetheless, I can say that we have seen ROI because I believe that our flexibility is partially based on Linode's flexibility, which lets us keep and get more clients. I just couldn't give a specific number of how much.

Being that they are small, their prices are slightly higher than the large providers like Amazon if you compare raw computing power. However, I understand they have to be slightly higher because they just don't have as many customers. If you come from the outside, not knowing how things are going to work, then look at the costs by doing a cost analysis, you might wonder why you should choose them if they're going to be more expensive across the board.

I can say that it doesn't affect me because I know what I'm paying for. It is easy to say that any solution can be cheaper and it could be better, but I know what Linode does, I understand the service I'm getting, and I know what it will provide me. As such, I think that it is fair and I am willing to pay the premium.

If you have a situation where you just want to spin up a server and run a test, without actually having a client and you don't want to incur too many costs, it's not been bad at all.

Considering support, response time, uptime, and price, I think that the price to performance ratio is pretty good. They've been very responsive whenever I have had questions, so from that point of view, I'm very satisfied.

I have experience with AWS and Azure but when it comes to evaluating other products, we haven't sat down and had comparison meetings or anything like that. Everybody that works in the company has been with me for a while, so they're very familiar with which servers and services work based on our needs.

There are obviously reasons to use, for example, Microsoft Azure because perhaps one of your services uses one of their services that they provide intimately. In a case like this, it's just easier to deploy on their platform because maybe you use one of their endpoints that are already on Azure.

I haven't seen any reason to compare the products because whatever service we create and develop to offer to our customers dictates where we put it.

Linode offers a smaller, but well-focused set of cloud computing services to customers, which I think is important because they are able to provide a very high level of support. If they did everything, if they were much larger, maybe they couldn't maintain that level of support because it wouldn't work if all of their customers asked for special treatment.

My advice for anybody who is considering Linode is to start very small and become a customer of theirs, just so you get used to and familiar with the way that you deploy servers and services. I suggest this because of the fact that they are not a Microsoft or an Amazon, but rather they're a much smaller company.

Again, become familiar with it, and even if it seems a little basic at times, allocate a small part of your development budget to just becoming a customer. This involves creating an account and playing around a little bit, and you'll see that you have most of the features that you need.

That is what the experience has been like for me. Maybe it's not like that for everyone, but try it out. You will probably see that it's more than you might think initially, at least that's the reason that I stuck around and stayed with them for so long.

I would rate this solution an eight out of ten.

I use it to host websites, including WordPress, Laravel, and Lumen.

I have hosted my website on Linode and my clients' back-end applications are running on it. One of them has a website on Shopify, and they needed an automation tool to upload products to Shopify. I developed an application that is hosted on Linode servers. It runs daily and synchronizes products with their suppliers.

The creation of instances is very good, as is their interface which is not complex and is easy to use. With the dashboard, it is easy to create a new instance and add your favorite things. You can add Debian, Ubuntu, or CentOS, or any flavor of the operating system. You can select the RAM for your instance as well.

The fact that Linode offers a small but well-focused set of cloud computing services is very important for me and for my clients. I have referred three or four clients to Linode and they are still using Linode to host their websites.

Everything is up-to-date for a small business. But for big business, they need to improve certain things. For example, there should be better security.

They also need to provide the ability to set limits. I should be able to turn off an instance at a given percentage of its capacity.

I have been using Linode for about a year.

It is very stable. It's mature now. I haven't had any issues with the services.

I love their support. If I have any issue or if my client has an issue, I just click to create a message for support and they resolve the issue or provide relevant guidance. Their support is 24/7/365.

I also use AWS and their support is very good. But Linode's support is quicker and better compared to AWS or other cloud providers. They take my problem as their problem and provide a solution very quickly.

I click on the required instance. They may have a special which only costs $5 per month. If I need that, I click on that instance. Then I choose the OS like Debian, Ubuntu, or CentOS. I then add a data center location, and then, if I need my personal PC access to the server automatically, I add that and click "next." Within 30 seconds, it is ready.

It's very cheap. The pricing model is very simple. If you have very small applications, you can use the plan which costs $5 per month. That gives you 50 GB of memory and almost 1 GB of RAM. If you need more than you have to select the next plan which is $10 per month, which has about 70 GB of data and 2 GB of RAM. I build small applications and that provides more than enough for small applications.

Taking everything into account, it has a very good price-to-performance ratio. If I use AWS, it costs more than Linode. It saves me $5 per month compared to AWS.

Many of the competitors, like AWS, have an interface that is slightly complex compared to Linode. There are no authentications or other things required in Linode. You just create your account, add your card, and do what you want to do. A non-technical person can't do AWS; you need some technical expertise to use it. But with Linode, you don't need such expertise. You can easily use and create anything on Linode.

I would recommend Linode. If you need to configure or implement applications, it is very good and fast, and saves you a lot of work compared to AWS or Azure. The interface is very simple.

We use Linode in our projects. We have one Linode, and it is quite straightforward. We have one Linode provisioned, which is running on the LAMP stack.

We are using the latest version.

It makes the LAMP stack easier to manage. We just send one command, then automatic updates and security patches happen. We then just use some source code control, like GitHub or Bitbucket, which has helped us because I feel their prices are quite competitive. Sometimes, we need a lot of test applications to show things, do PoCs, and have test sites. So, it doesn't make sense for us to go with the big cloud solution, which is expensive. This way, you don't need to spin up some test sites or test applications for PoCs for just some UAT type of things. This has helped.

I like how if you are an older developer and have some development experience, then it is very easy to get to the foundation, which is cool. Then, you have complete freedom to configure it the way you want. Also, Linode is fast.

It is very focused and doesn't have a lot of features. For example, it doesn't have the complete DevOps pipeline. You can configure it directly using UIs, configuring the entire pipeline and even your project management, which is what we get in something like Azure. It is good to have that focused approach. 

For small businesses and people who have some technical skills and are good with Linux command line, this solution is great. I love Linode because it is very fast. Whereas, the same configuration on Azure and AWS will be so slow. The best thing is that their pricing and speed are great.

While Linode works well for people who have some technical experience, e.g., I am good with Linux and very comfortable with the command line, I can understand how people who are not so comfortable with the command line probably prefer a lot of feature-based cloud services.

I would like Linode (without cluttering things) to provide some type of DevOps workflow where people are configuring their pipelines from running their tests and deploying to their test server. Once approved by clicking a button, it just gets deployed to production. I would like something like Azure DevOps, which we use for large applications, and would be something nice to have in Linode.

I have been using it for the last two years.

It is very stable. We haven't had any issues.

Scaling up has been easier. We just scale up the node, then it scales up. One thing is if you want to scale up, then you cannot scale down. I have tried that a few times because we have certain seasons in the year where no one is using the application. So, I tried to scale down, but Linode doesn't allow that. However, scaling up was quite easy and fast.

Our applications are currently being used in Southeast Asia. Our clients are region-focused and very rarely will we have an application used outside this region. Performance-wise, it is more important how you build your application than having data centers everywhere unless it is a very high-end application. However, we don't have those kinds of applications, where thousands of users simultaneously work across the globes. 

We are set for scalability because we have small businesses and don't need a very high scalability, where we have something like Kubernetes or one of those high-end, complex scaling pipelines. We have not needed those things. We just have to scale the node, going from two CPUs to four CPUs and upgrading the RAM.

We are using it for small applications and are happy with that. However, there are no new projects on the horizon, so we are just maintaining the solution.

The couple of times that I have raised tickets, they replied within a day or two, but I never had an emergency situation. Their support is good.

We came across the solution through Linode's advertisements. We used it for the free trial period, liked it, and purchased it.

I didn't have any problems with the setup. It was quite straightforward and easy. Basically, you select what you need, then they give you access and you go on from there. It took 10 to 15 minutes.

Once you set up Linode, then you have to install some basic things. You install your source code software, like GitHub, with your application source code. It was quite straightforward.

I did the deployment.

I am the only person who uses and maintains Linode currently. Someone else looks at the other cloud solutions.

I have been using it for two years. Linode compared with other solutions must have saved us around $300 to $400, max.

The pricing and licensing are good. It is very straightforward and simple. I would like more options, e.g., if I want to upgrade my Linode right now, then I have to double it. I would like another option than that.

Linode is not as expensive as Azure and AWS. I feel that Linode is able to give very competitive rates. I find other providers, like Google and AWS, expensive.

Its price-to-performance is better than other big cloud providers, like Azure, Google, and AWS. It has saved us money. While their rates might look the same, their servers tend to be slow. So, if you want the same speed as Linode in other big providers, then you need to go for a higher end solution and the costs will double. I think Linode's rates are good because the performance of their servers are good.

I just pay for the server and other things that I use, like their object storage. There are no hidden costs.

Once you open a new account, they give you some free credit. We used that free credit and liked the solution. So, we went ahead with it.

We use Azure a lot for our big business applications. Usually, we end up comparing and seeing things over there, determining how Linode would have handled this. I have tried out Linode analytics. Mostly, for innovation, we look for that in Azure with their side pipelines and DevOps. 

We looked at DigitalOcean, but never used it.

They try to give you the basics, They try to remove complexities, keeping the platform as basic and simple as possible. That is why the system works very quickly. This is a good model to take forward and better than going with the shared systems, like GoDaddy, because you have total control of what you want to install, upgrade, and where you want to apply security. You have total control over the server. Other shared systems don't have this because they are slowing due to sharing your sources. So, I really liked this model of Linode.

If you have some confidence or experience using the command prompt, then this is the best thing to go for. If you have the technical expertise to manage the server directly, then this is the best thing because you will save a lot of money, not going for a higher end, like Google or Azure. You will save money and get better performance. However, if you don't know how to manage the server directly, then you might have a hard time and need better support from Linode to set up your servers. Other than that, it is the best choice.

I would rate Linode as a nine (out of 10).

I am generally using them for bringing up websites and servers for customers. Oftentimes, a company will want their own mail server and/or web server, and I will use Linode for that. It is extremely convenient and easy for me to do this. I really like how they are set up. They just seem to do everything right.

It is a very cost-effective solution. It allows me to give high availability. Having it be a VM instead of a dedicated piece of hardware is extremely valuable in the fact that they are very proactive about their monitoring. There have been several times where I have seen them migrate a VM from a server that was having problems onto a new server. I have had that happen a couple of times over the years that I have been with Linode.

The service has helped our organization accelerate innovation because, in certain cases, I have wanted to try something new. So, I would just spin up a VM briefly for a short period of time to try some things on it and see how it worked, then I could just turn it off again. It basically made me a rapid prototyping environment so I could try new things and get stuff working pretty quickly.

Linode offers worldwide coverage via multiple data centers, which is very important to me. I would like to see more European offerings. I know they have Frankfurt available right now. I would personally like to see more data centers throughout Europe or Eastern Europe available.

They could have more international servers. There are certain places throughout Europe and Eastern Europe which are very open to doing a lot of technology business, such as Romania. Romania is very open to technology. At other service providers, I have stuff in Romania. I think there are some Eastern European locations that would be more open to it. So, if they could have more European points of presence, that would be more helpful.

I have been using them for quite some time, at least five years.

They are very stable. I am very pleased. I have always experienced good stability with their stuff. For the servers that I have used, they have always been very stable. I have always noticed them to be very proactive when they do detect a problem. Migration from there to a different server has always been rather quick. 

The scalability is very easy because I can pay some money, reboot the machine, and now I have the upgrade. It is done. It is very simple. I am always pleased with that.

There are about 10 machines or so that are currently running. I have some customers who have two servers and others with one server.

I don't often have to use their support because the machines are so stable. I may have to talk to support once a year, which is not very often at all. When I do deal with them, having it be 24/7 is not terribly critical to me because I usually only do this work during regular work hours anyway. I have noticed there have been times where towards the end of the day, I would create a ticket or be in a conversation with one of them, then they would answer me well after business hours and be available for that. However, in general, I haven't had to use their support a whole lot in the first place because it just runs and works.

I have used a company in Europe called IntoVPS. Some of my colleagues have used Vultr. So, my friends and I have used a couple other services, but I keep coming back to Linode.

IntoVPS had offerings that were just incompatible. They were using Zen Solutions for a while, and I found compatibility issues with it. When I used them, they didn't seem to have a mature product offering that did what I wanted. I felt like I was always working around one of their limitations.

My other friends have used Vultr, and they're pretty happy with it. I have not set up anything personally for my own customers on Vultr yet, but from what I see and heard, they seem to like Vultr a lot too. Vultr has a lot of European points of presence. If I was going to sign up for a Vultr account, it would be because they have more locations in Europe than Linode does. That would be my only motivation at this point, since I don't have personal experience with them.

Setting up with Linode is very easy. I will pick the size of the VM that I want and usually use a CentOS 7 distribution. Once I have that, I will usually just be able to run. If I am bringing something up that is sort of a cookie-cutter server, then I can run my Ansible scripts against it, then it is very rapid. In a matter of minutes, I can go from having nothing to having a functional server that I can log into and start putting the customer's data onto it.

The setup process is usually either:

• Simply select the distribution and start using it.
• Run some Ansible scripts to do some of those tasks ahead of time. 

It is extremely simple. One of the big things that I really like about Linode is how simple, quick, and easy the solution is to get working.

It takes less than a day to spin up an environment. I will go from having nothing to having a fully functional customer website or mail server. It takes less than a work day. In fact, it is usually about half a work day. I will do it in the afternoon. I will start the machine and configure it, then it will be done in a very short time. By the end of the day, it is done and working. I am ready for the customers' users to start using it. It is very quick.

Linode is a very high value for what you are paying. I have brought up a number of the $5 and $10 a month servers, and customers have generally been very happy with those. I am not expecting the world from the servers because they are only $5 or $10 a month servers, but I am not asking for too much from them. It really works out well. Even on low-end systems at $5 and $10 a month, it is very well done.

Because of the way that their pricing model is set up, I can scale up or down the size of a customer's server very easily. It makes life very easy for me when they run out of space, need more speed or RAM, etc. I can very easily pay the difference and reboot the machine, and now I have the upgrade that I wanted. That just makes it extremely simple.

It is important to me that the provider offers a relatively small, but well-focused, set of cloud computing services. I can start off a very small customer at $5 a month, then scale them up from there. I have done that numerous times. I started off a customer on a $10 month server, and now they are on a $80 month server. Being able to scale up like that is very valuable to me.

The pricing model is very simple. I like the simplicity of it, starting at $5, then doubling as it goes up from there. That is a brilliant idea, and it is not complex at all. It is about as dead simple as you can imagine. So, if you want to double what you have, then you double your price, pay the money, and reboot. It is done. It's that simple. You can't beat that.

At this point in the game, Linode is pretty much the only VM provider that I recommend for my customers to use. It is the only place where I put stuff that I have out there for different customers. So, I am pretty sold on Linode. I have tried a couple of other services, but Linode is the one that I keep coming back to right now.

Looking at IntoVPS and what they provide, Linode is saving me money. I have found that IntoVPS has some strange pricing because they have a diverse offering of different virtualization technologies; there is too much to pick from. I would rather just have one thing that works properly, like Linode, and just use that. Compared to IntoVPS, Linode is much better. 

Compared to Vultr, it is pretty much almost exactly the same. The only thing that might be a difference is Linode has a range of compute servers where the Vultr offering for high-frequency compute nodes has a different pricing scheme. That is about the only difference.

A lot of these other providers out there really do not have their acts together. Linode has done a great job in simplifying everything to the point where it is just simple and easy. I learned to stick with what works, which is Linode.

Go for it. I would recommend Linode. Don't be afraid to try out the cheaper, smaller systems for whatever you are running. Pick the system that meets your system requirements as best as possible, but you really can save. I would recommend it because you can save a lot of money as well as time and hassle.

I would rather pay just a little bit more and have a hassle-free operation than to pay less and be faced with support issues. I don't like having to deal with support. I don't like having to bring in anybody else to help me debug something. So, I look at Linode as everything just works. It is a very cheap price, depending on what you're getting. It can be scaled up and down very easily. So, it has exceptional value.

I would rate this solution as a 10 (out of 10).

We are hosting Linux virtual machines and load balancers over there. This is the infrastructure we have over there. Apart from that, we are using a firewall from the Linode side. These are the three Linode components that we are using.

We have not explored Linode too much. We are just restricted to VMs, load balancers, and the firewall. We are currently not hosting a lot over there. We are not facing any challenges with it. We are looking into hosting some replicated storage there.

It has helped to minimize the risk and scale services at large in virtually no time. This is how the cloud supported us. Earlier, we were in our own data center. It was in-house infrastructure, but we moved over to the cloud. It allows us to scale services as the demand increases over time.

Its cost can be improved.

I have been using Linode for almost four to five years.

We never had any problem with scalability while using AWS, Azure, or Linode.

I would rate their support an eight out of ten.

Positive

Before Linode, we used Azure. We have used AWS. Both Azure and AWS have too many offerings. They have different types of offerings in terms of PaaS, SaaS, and many other solutions, but Linode focuses more on the open-source technology side and the infrastructure as a service side. It has less capability when it comes to the PaaS and SaaS Platforms.

Overall, it is cost-effective. They offer flat, no lock-in pricing. We also get discounts.

As compared to its competitors, it is costly, but at the same time, it has many features. In terms of functionality and features, it offers more capability, but it is also costly.

With any cloud computing product, the foremost requirement is performance, and along with that, there should be cost-effectiveness. These are two major factors for us to decide whether we should have the service of a cloud service provider or not.

Go for Linode if you want to host the infrastructure as a service. It is much cheaper than AWS and Azure. For SaaS and PaaS services, you can explore AWS and Azure. For infrastructure as a service, Linode is a lot more cost-effective than AWS and Azure.

I would rate Linode a nine out of ten. It is a leader. We have used other products as well, and it has much more capability as compared to them.

We primarily use Linode for our company website. We run a pretty large knowledge base on the site for our products. We also use it for our order email processing. All that's done on a Linode-based virtual machine.

The biggest result is that it performs very well. Our website is quite responsive. Our knowledge base, which has a search engine, is extremely responsive. We do email order processing as well and there has never been an issue with that. We look to it to process things essentially in real-time, perform well, and give users using our site a good experience. That's what we get from Linode.

The number one thing we like about Linode isn't necessarily a service, it's their support. We've found their support to be absolutely fantastic. They've been so outstanding with their support. Every single time we call them and we ask for advice or help, they go above and beyond and it's really made us appreciate what they do.

Linode offers a relatively small but well-focused set of cloud computing services. We've never been able to stump support with a question. My experience has been that they're very knowledgeable on the systems they run. When we call and ask for advice on configuring something or setting something up, even though that's not part of their mission, they still are always very helpful and get us up and running.

It is important to us that they also offer worldwide coverage via multiple data centers. Having multiple data centers not only gives them coverage for backing up data across the world so we know that our data is not necessarily just in one place but it can be backed up in several locations. In addition, as so many companies now are international, we can get better performance in different parts of the world by having data centers spread around.

It's not really an issue with Linode itself but upgrading Linux major versions can be challenging. It would be be fantastic if Linode developed a way to ease transitioning to a major new Linux upgrade.

I have been using Linode since 2016.

It's all cloud. We have monitors on our site that let us know if the site goes down for any reason, which would include Linode having a problem. I can only remember one instance where a network segment went out. This occurred years ago. We had a little bit of downtime but they were on it and fixed it quite quickly. Linode is extremely reliable.

They make it very easy to add additional services if we need to. It could be either additional nodes or moving to another node that has more space, more memory, or whatever it is we want. There are quite a few offerings and they're pretty easy to set up. If we ever need to do that, it's certainly there waiting for us.

We can call Linode and immediately be connected with someone who's very knowledgeable.

We found the initial setup to be pretty straightforward. They have a fantastic set of documentation that will guide you through setting up almost anything. Between that, and then if something's not clear, you reach out to support who are very helpful. It's really pretty straightforward.

The setup took less than a month, and that was moving from dedicated hardware on a completely different type of Linux over to the Linode on a newer version of a different flavor of Linux. It took less than 30 days.

We did the deployment ourselves but we got advice along the way from Linode.

We have definitely seen a ROI. The cost of running on virtual services, like Linode, is so much less than running on dedicated hardware.

The pricing is quite good. We are paying a fraction of what we did when we were running on actual hardware, where we had a machine dedicated just to us. Their pricing is quite competitive from what I've seen.

Their pricing model is straightforward. From looking at their pricing page, it's pretty simple to figure out what it's going to cost.

We did evaluate other solutions on the surface. Although, at the time, we had a referral. Someone else that we knew quite well was using Linode and really liked it, so that gave Linode an edge. There are definitely other good providers out there. Linode's support was so overwhelmingly good that that's really what convinced us that we made a good choice.

My advice would be to reach out to Linode, ask questions, and get comfortable with how they're going to support you moving over there. Check out their documentation, which is excellent. That will enable it to be a very smooth transition. They seem to be very willing to help people, even upfront. That would be the way I would do it.

I would rate Linode a ten out of ten.