This article is a stub. You can help The Open Homelab project by expanding it.
There are many reasons as to why you would want to run a local "on premises" homelab, but equally there are plenty of reasons why you might also want to consider simply running your lab in a cloud service provider's platform. Here we discuss some of the options available to move to the cloud and get that noisy spinning rust out of your living room / office!
Pros and Cons
The key benefits to moving to using a cloud homelab are:
- Massive WAF as the cloud homelab makes no noise, takes up no space and is completely invisible to your partner!
- No big capex investments required for you at home to buy physical kit (such as compute hosts, network switches, NAS arrays, etc. Instead the cost of your homelab is spread across its lifetime
- If you do not need to run some or all of your homelab running 24/7, then the cloud homelab is ideal, as you only pay for it when it's running! If you are a very infrequent labber who doesn't need to do much at the actual hypervisor level, it could indeed be an ideal solution, or at least good enough!
- Taking that a step further, if you don't use your cloud homelab for a few weeks or months, it doesn't cost you a penny!
- Flexibility and scalability of the cloud means you can spin up very large environments for testing, then blow them away. In your homelab your homelab is limited to your maximum resource capacity.
- The number of features and technologies available in the cloud
- Licensing is both a pro and a con in the cloud. Certain software you may wish to use may not be compatible with running n multi-tenant compute, but using the licensing built into the cloud platforms mean your licensing is covered automatically (taking Amazon RDS or Azure SQL as perfect examples - SQL licensing is included!). You can even rent some software solutions on an hourly basis, meaning you can fully test some software for as long as you need and only pay a matter of a few pennies to pounds!
Key negatives to using a cloud homelab:
- You have to be very careful to configure the appropriate security and alerting safeguards, to ensure you don't either have your account compromised, or indeed accidentally leave machines running and end up with a huge bill. Setting things like billing alerts can help to mitigate this. Also keeping tight control of your account passwords and keys!
- You don't have that warm fuzzy feeling of doing a local manual install on real tin, and all the potential fiddling and tweaking it sometimes requires (YMMV)
- With the typical internet connection for most folk being asynchronous DSL 2+ (FTTC if you're lucky), upload speeds can make things a bit painful when transferring data and machine images from your home machines.
- Not ideal if you want something which runs multiple machines 24/7 as the costs can spiral.
- Security in general is something you will need to spend a bit more time thinking about if you want to run your homelab in the cloud.
The main use cases for cloud homelabs are:
- You have no space for a homelab
- You have no budget to buy the kit for a homelab up front
- You don't need to run your homelab 24/7, and may even only require it irregularly
- You aren't that interested in doing bare metal installation, and are more keen about testing the hypervisors themselves, or software and services on top
The following is a list of potential cloud computing providers for your Cloud Homelab:
|Vendor||Free / Trial Link||Pricing Link||Pricing Calculator||Notes|
|Amazon AWS||12 Months Free Tier||Pricing||Calculator||The AWS free tier extends beyond 12 months for some services. You can gain $credit by being signing up to all trials and betas.|
|Bare Metal Cloud||None?||Pricing||None||If you want a true bare metal install experience, why not just pay by the hour?|
|Google Cloud Platform||$300 / 60 days||Pricing||Calculator|
|Microsoft Azure||$200 / 30 days||Pricing||Calculator|
|Ravello||6 VMs / 14 days||Pricing||Calculator||Very simple pricing. Currently free to vExperts!|
|VMware vCloud Air||$300 / 30 days||Pricing||Calculator||Very expensive for public IPs.|
Costs will vary depending on which cloud provider you use, and whether you are a member of any particular vendor advocacy programmes.
The good thing is that all of the major cloud vendors are completely transparent in their pricing. The bad thing is that although all of the major cloud vendors are completely transparent in their pricing, it's usually ridiculously complex!
The key thing here is that the more you use your lab, and the more VMs you want to run 24/7, the more it will cost you. If you simply need to spin up a few VMs for a few hours per month, then a cloud homelab will be by far the cheapest option!
Amazon provide one of the most generous "free tier" options of all vendors. 12 months of free (limited) access to a load of their services, including the ability to run one Linux VM, one Windows VM and one RDS (database) instance 24/7/365! Actually this breaks down for the EC2 instances as 750 hours per month, which you can use however you like. For example you could run 10 instances for 3 days!
A couple of key links for setting up your AWS account are below:
For more information and advice on using Amazon AWS as your homelab, see our dedicated page on Amazon AWS homelabs.
Bare Metal Cloud
Bare Metal Cloud are a really interesting "physical cloud" solution! As per their own website:
We provide bare-metal dedicated servers which are unrestricted and not shared. You have full access down to the to the bare-metal of the hardware. All servers come with an OS of your choice but you have full permissions to reinstall or change anything you wish.
So here's the cool bit! You can spin up your own hypervisors or whatever you want on their tin, and simply pay by the hour! When you combine Bare Metal Cloud with AutoLab, you can have your lab up and running in a very short time, and be labbing on physical tin in somebody else's data centre!
If you want to see an example of this working, Mike Laverick did a great article on his blog here:
For more information and advice on using Bare Metal Cloud as your homelab, see our dedicated page on Bare Metal Cloud homelabs.
Google Cloud Platform
In comparison to most vendors (except AWS), GCP provide a pretty decent length 60 day free trial, with a set amount of credit.
For more information and advice on using Google Cloud Platform as your homelab, see our dedicated page on Google Cloud Platform homelabs.
Ravello is a really interesting product which impressed so much, Oracle acquired them recently for ~$500m!
Their key concept is that they are effectively a cloud hypervisor which can run on top of any public cloud, allowing you then to nest your chosen hypervisor and VMs inside of it! Yes, indeed this is taking vInception to a whole new level; Cloud vInception!!! You use a very easy to use visio-style SaaS interface to design your lab, and once you are ready to deploy it, they then choose whatever is the most cost effective cloud to run it on at that time. You are then simply charged by the hour for resources consumed. Simples!
In a very gracious move, Ravello is free for vExperts! Despite their recent acquisition, they have stated that the free access will continue for now. If you are a vExpert, go here to apply:
Jason Langer did an excellent writeup comparing the cost of running a homelab vs using Ravello, and the results were pretty impressive based on the use case of 12 hours per week (pretty heavy use!):
VMware vCloud Air
For more information and advice on using VMware vCloud Air as your homelab, see our dedicated page on VMware vCloud Air homelabs.
Thoughts on Free Trials
That said, with something like Amazon AWS, many of the services are free well beyond the 12 month trial period, and you can gain access to free credit by simply taking part in trials of new services, many of which pay out up to $25 each, which should be more than enough to keep your account going for some time!
Free Cloud Homelabs
A question you may want to ask yourself, is what is the reason you want to run the lab itself? If the main reason is just to play with specific vendor software, then why not just use their free labs? Many of them are effectively just run on a sandbox basis, where you can choose to follow their pre-scripted instructions, or you could just go off piste and mess about with whatever you like (as long as permissions allow!).
This obviously wont apply to every vendor, but many of the most common, such as VMware and Microsoft, do.