Alternatives to Linode logo

Alternatives to Linode

DigitalOcean, Vultr, Heroku, WebFaction, and RamNode are the most popular alternatives and competitors to Linode.
746
623
+ 1
422

What is Linode and what are its top alternatives?

Get a server running in minutes with your choice of Linux distro, resources, and node location.
Linode is a tool in the Cloud Hosting category of a tech stack.

Top Alternatives to Linode

  • DigitalOcean
    DigitalOcean

    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel. ...

  • Vultr
    Vultr

    Strategically located in 16 datacenters around the globe and provides frictionless provisioning of public cloud, storage and single-tenant bare metal. ...

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • WebFaction
    WebFaction

    No need to spend hours installing and configuring the software, database and other tools. We have over 50 one-click installers in our control panel. ...

  • RamNode
    RamNode

    High performance hosting on a simplified OpenStack platform.

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Apache HTTP Server
    Apache HTTP Server

    The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet. ...

  • Amazon EC2
    Amazon EC2

    It is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers. ...

Linode alternatives & related posts

DigitalOcean logo

DigitalOcean

18.1K
2.6K
Deploy an SSD cloud server in less than 55 seconds with a dedicated IP and root access.
18.1K
2.6K
PROS OF DIGITALOCEAN
  • 560
    Great value for money
  • 364
    Simple dashboard
  • 362
    Good pricing
  • 300
    Ssds
  • 250
    Nice ui
  • 191
    Easy configuration
  • 156
    Great documentation
  • 138
    Ssh access
  • 135
    Great community
  • 24
    Ubuntu
  • 13
    Docker
  • 12
    IPv6 support
  • 10
    Private networking
  • 8
    99.99% uptime SLA
  • 7
    Simple API
  • 7
    Great tutorials
  • 6
    55 Second Provisioning
  • 5
    One Click Applications
  • 4
    Dokku
  • 4
    LAMP
  • 4
    Debian
  • 4
    CoreOS
  • 4
    Node.js
  • 3
    1Gb/sec Servers
  • 3
    Word Press
  • 3
    Mean
  • 3
    LEMP
  • 3
    Simple Control Panel
  • 3
    Ghost
  • 2
    Runs CoreOS
  • 2
    Quick and no nonsense service
  • 2
    Django
  • 2
    Good Tutorials
  • 2
    Speed
  • 2
    Ruby on Rails
  • 2
    GitLab
  • 2
    Hex Core machines with dedicated ECC Ram and RAID SSD s
  • 1
    CentOS
  • 1
    Spaces
  • 1
    KVM Virtualization
  • 1
    Amazing Hardware
  • 1
    Transfer Globally
  • 1
    Fedora
  • 1
    FreeBSD
  • 1
    Drupal
  • 1
    FreeBSD Amp
  • 1
    Magento
  • 1
    ownCloud
  • 1
    RedMine
  • 1
    My go to server provider
  • 1
    Ease and simplicity
  • 1
    Nice
  • 1
    Find it superfitting with my requirements (SSD, ssh.
  • 1
    Easy Setup
  • 1
    Cheap
  • 1
    Static IP
  • 1
    It's the easiest to get started for small projects
  • 1
    Automatic Backup
  • 1
    Great support
  • 1
    Quick and easy to set up
  • 1
    Servers on demand - literally
  • 1
    Reliability
  • 0
    Variety of services
  • 0
    Managed Kubernetes
CONS OF DIGITALOCEAN
  • 3
    No live support chat
  • 3
    Pricing

related DigitalOcean posts

Christopher Wray
Web Developer at Soltech LLC · | 15 upvotes · 185.7K views

This week, we finally released NurseryPeople.com. In the end, I chose to provision our server on DigitalOcean. So far, I am SO happy with that decision. Although setting everything up was a challenge, and I learned a lot, DigitalOceans blogs helped in so many ways. I was able to set up nginx and the Laravel web app pretty smoothly. I am also using Buddy for deploying changes made in git, which is super awesome. All I have to do in order to deploy is push my code to my private repo, and buddy transfers everything over to DigitalOcean. So far, we haven't had any downtime and DigitalOceans prices are quite fair for the power under the hood.

See more

Hello, I'm currently writing an e-commerce website with Laravel and Laravel Nova (as an admin panel). I want to start deploying the app and created a DigitalOcean account. After some searches about the deployment process, I saw that the setup via DigitalOcean (using Droplets) isn't very easy for beginners. Now I'm not sure how to deploy my app. I am in between Laravel Forge and DigitalOcean (?Apps Platform or Droplets?). I've read that Heroku and Laravel Vapor are a bit expensive. That's why I didn't consider them yet. I'd be happy to read your opinions on that topic!

See more
Vultr logo

Vultr

180
10
Deploy Cloud Servers, Bare Metal, and Storage worldwide
180
10
PROS OF VULTR
  • 3
    Affordable
  • 3
    Cloud Based
  • 3
    <a href="https://hostandprotect.com/">secure</a>
  • 1
    Easy to use
CONS OF VULTR
  • 1
    Why can't i delete a cons?
  • 0
    Ưefwef

related Vultr posts

Paul Whittemore
Developer and Owner at Appurist Software · | 4 upvotes · 280.5K views

For those needing hosting on Windows or Windows Server too (and avoiding licensing hurdles), both Vultr and Amazon LightSail offer compelling choices, depending on how much compute power you need. Don't underestimate Amazon LightSail, especially for smaller or starting projects, but Vultr also offers an incremental $16 Windows option on top of their standard compute offerings.

See more
Heroku logo

Heroku

25.6K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
25.6K
3.2K
PROS OF HEROKU
  • 703
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 153
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    Painless & well documented
  • 6
    No-ops
  • 4
    I love that they make it free to launch a side project
  • 4
    Free
  • 3
    Great UI
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
  • 1
    Security
  • 1
    Able to host stuff good like Discord Bot
  • 0
    Sec
CONS OF HEROKU
  • 27
    Super expensive
  • 9
    Not a whole lot of flexibility
  • 7
    No usable MySQL option
  • 7
    Storage
  • 5
    Low performance on free tier
  • 2
    24/7 support is $1,000 per month

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 2.9M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
WebFaction logo

WebFaction

31
18
Hosting for developers: full shell access to fast servers with all your favorite tools pre-installed and maintained for...
31
18
PROS OF WEBFACTION
  • 3
    Cost effective
  • 3
    Great customer support
  • 3
    Servers administered for you
  • 2
    Comes with Rails installed automatically
  • 1
    Great documentation
  • 1
    SSH access
  • 1
    Best price
  • 1
    SSD
  • 1
    Many pre-installed apps
  • 1
    Having the least amount of new "fancy" terminologies
  • 1
    No needs configuration
CONS OF WEBFACTION
    Be the first to leave a con

    related WebFaction posts

    RamNode logo

    RamNode

    20
    2
    High Performance Cloud VPS
    20
    2
    PROS OF RAMNODE
    • 1
      SSH root access
    • 1
      Affordable
    CONS OF RAMNODE
      Be the first to leave a con

      related RamNode posts

      NGINX logo

      NGINX

      113.8K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      113.8K
      5.5K
      PROS OF NGINX
      • 1.4K
        High-performance http server
      • 894
        Performance
      • 730
        Easy to configure
      • 607
        Open source
      • 530
        Load balancer
      • 289
        Free
      • 288
        Scalability
      • 226
        Web server
      • 175
        Simplicity
      • 136
        Easy setup
      • 30
        Content caching
      • 21
        Web Accelerator
      • 15
        Capability
      • 14
        Fast
      • 12
        High-latency
      • 12
        Predictability
      • 8
        Reverse Proxy
      • 7
        Supports http/2
      • 7
        The best of them
      • 5
        Great Community
      • 5
        Lots of Modules
      • 5
        Enterprise version
      • 4
        High perfomance proxy server
      • 3
        Embedded Lua scripting
      • 3
        Streaming media delivery
      • 3
        Streaming media
      • 3
        Reversy Proxy
      • 2
        Blash
      • 2
        GRPC-Web
      • 2
        Lightweight
      • 2
        Fast and easy to set up
      • 2
        Slim
      • 2
        saltstack
      • 1
        Virtual hosting
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 1
        Ingress controller
      CONS OF NGINX
      • 10
        Advanced features require subscription

      related NGINX posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      John-Daniel Trask
      Co-founder & CEO at Raygun · | 19 upvotes · 496.7K views

      We chose AWS because, at the time, it was really the only cloud provider to choose from.

      We tend to use their basic building blocks (EC2, ELB, Amazon S3, Amazon RDS) rather than vendor specific components like databases and queuing. We deliberately decided to do this to ensure we could provide multi-cloud support or potentially move to another cloud provider if the offering was better for our customers.

      We’ve utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an nginx instance and are managed using scaling groups in Amazon EC2 sitting behind a standard AWS Elastic Load Balancing (ELB).

      While we’re satisfied with AWS, we do review our decision each year and have looked at Azure and Google Cloud offerings.

      #CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy

      See more
      Apache HTTP Server logo

      Apache HTTP Server

      64.6K
      1.4K
      Open-source HTTP server for modern operating systems including UNIX and Windows
      64.6K
      1.4K
      PROS OF APACHE HTTP SERVER
      • 479
        Web server
      • 305
        Most widely-used web server
      • 217
        Virtual hosting
      • 148
        Fast
      • 138
        Ssl support
      • 44
        Since 1996
      • 28
        Asynchronous
      • 5
        Robust
      • 4
        Proven over many years
      • 2
        Mature
      • 2
        Perfomance
      • 1
        Perfect Support
      • 0
        Many available modules
      • 0
        Many available modules
      CONS OF APACHE HTTP SERVER
      • 4
        Hard to set up

      related Apache HTTP Server posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 4.3M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Tim Abbott
      Shared insights
      on
      NGINXNGINXApache HTTP ServerApache HTTP Server
      at

      We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

      Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

      See more
      Amazon EC2 logo

      Amazon EC2

      48.5K
      2.5K
      Scalable, pay-as-you-go compute capacity in the cloud
      48.5K
      2.5K
      PROS OF AMAZON EC2
      • 647
        Quick and reliable cloud servers
      • 515
        Scalability
      • 393
        Easy management
      • 277
        Low cost
      • 271
        Auto-scaling
      • 89
        Market leader
      • 80
        Backed by amazon
      • 79
        Reliable
      • 67
        Free tier
      • 58
        Easy management, scalability
      • 13
        Flexible
      • 10
        Easy to Start
      • 9
        Widely used
      • 9
        Web-scale
      • 9
        Elastic
      • 7
        Node.js API
      • 5
        Industry Standard
      • 4
        Lots of configuration options
      • 2
        GPU instances
      • 1
        Simpler to understand and learn
      • 1
        Extremely simple to use
      • 1
        Amazing for individuals
      • 1
        All the Open Source CLI tools you could want.
      CONS OF AMAZON EC2
      • 14
        Ui could use a lot of work
      • 6
        High learning curve when compared to PaaS
      • 3
        Extremely poor CPU performance

      related Amazon EC2 posts

      Ashish Singh
      Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3.4M views

      To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

      Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

      We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

      Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

      Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

      #BigData #AWS #DataScience #DataEngineering

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more