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.

Linode is a service that hosts virtual machines for you.

I was using it primarily for virtual private servers. But recently they came out with the Kubernetes platform and most of what I do at my day job is Kubernetes engineering. I'm very familiar with it. I had wanted to switch all my personal projects over to Kubernetes, and it was really great when Linode finally came out with it. Now I'm using Linode for Kubernetes clusters. I still do hold some VPSs, but most of my stuff is on Kubernetes now. I don't use Linode at my day job. We use Azure for the same thing there, but I choose to use Linode for all my personal projects.

I have my own social media system called bolixo.org, and I am hosting it using Linode.

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.

I run a small company as well as my own personal website. I am using their cloud servers for managing websites and the web applications that I develop applications. So, I use Linode both for development and hosting public applications on my website. I also use their object storage to store things, like backups and files, which I want to keep for safekeeping, but not on my personal laptops. 

Our customers use the product for non-core critical applications, email applications, and for catering to internal IT teams.

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.

We're a software company that uses a 1980s American product called Appgen, as an application generator. We've got accounting, finance materials, and information packages running under Appgen and we have a number of hospitals in Victoria, Australia using that for their finances. They tend to run on SCO Unix or UnixWare, but our own version of it, which we use for developing is SUSE Linux.

We've got an in-house virtual machine running there, but I was concerned about backup. My original reason for choosing Linode was it was an affordable Linux cloud node system that could run both Fedora and SUSE Linux.

I just chose on those grounds initially and we didn't do much else with it. But in fact, one of the services that we provide is called Medicare Online, for the Australian government health billing service. In this system, doctors and hospitals bill patients and then claim the expenses back from the government. That's been running the product's security system. Moving on to the web services, I thought when we started developing them, we'll try using Linode.

I think it's very affordable and although my initial intention was just to use it as a backup, I'm mirroring our machine with it. When we go ahead and develop the web services interface, we'll use Linode to do it.

I use Linode primarily as a backup for digital ocean services. I also host websites for clients in London on Linode servers for better proximity but managing DNS and domain records is easier on Digital Ocean compared to Linode. I haven't used Linode for managed databases or cloud storage.

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.

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.

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.

We are using Linode for hosting a website.

In the beginning I needed something to host domain name services for the domain name that I had registered. I also use it for email and file sharing. We were pioneers in that regard, in April 2008, going fully online for the company, with everybody working from home and interacting through the platform that we set up with Linode.

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.

Our use cases involve their virtual server (VPS) solutions, which we have used since we first started with them. They also have a wonderful DNS service, and we use that as well.

For most of their existence, VPS is more or less what they have been providing.

We have a product named StarBazaar, so we are using it for that. It is a B2B e-commerce platform.

We're a hosting service, as well as a software development and website design company. We use Linode for virtual servers to host the websites that we design and maintain.

The Linode servers we have are all running Ubuntu.

We have several client websites, including several with active eCommerce options, that act as large document management systems for academic journals.

For our own use, we have a major business wiki, which we use for project planning, ISO900 compliance, and contact management, etc.

For all the sites, we also run email services, which are so simple to set up that we don't charge our clients extra to use as many as they like. We offer a webmail system with calendars, address books, etc.

I am using Linode for our cloud platform to host our enterprise solutions.

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.

Its user-friendly interface and convenient administrator panel allow me to quickly and easily manage my services.

I used to work as a software engineer for many years and when I retired, I wanted to carry on writing software. I wanted to work on my own vanity projects, rather than anything commercial. My particular interest and hobby is traditional music, so I wanted to develop tools, such as browser applications, websites, and so forth to help people learn and to promulgate traditional music. I needed a server for that, so I decided to use Linode.

I am using a cloud platform that is running Linux.

I have two use cases. I work mostly by developing e-commerce sites for companies and the first use case is to develop the infrastructure, the hosting solution for those e-commerce platforms. This is done mostly in Magento, WordPress, Drupal, and other open-source platforms.

We also have our own solution, which we host in Linode. It is a software as a service platform that connects Mercado Libre with Zendesk, which are two separate companies, and we join them through middleware.

We use this solution in our company and we deploy it for our customers. I'm a manager for the developer team and we are a user of Linode.

We use Linode as a server.