4 Hosting Types Compared: Free and Paid Hosting and VPS | VPS and VPN
Web Hosting

4 Hosting Types Compared: Free and Paid Hosting and VPS



OFFICIAL WEBSITE: https://lukesmith.xyz рџЊђвќ“рџ”Ћ
DONATE NOW: https://lukesmith.xyz/support 💰😎👌💯

Some hosts:
– https://nearlyfreespeech.net (traditional hosting only)
– https://ramnode.com/
– https://www.netcup.eu/
– https://digitalocean.com (offers “Droplets” which are VPSes)
– https://namecheap.com
– https://bluehost.com
– https://hostgator.com

Free hosting sites that you can point a domain to:
Neocities, Gitlab Pages, Github Pages, WordPress.com, many other sites you probably know of.
Look up in each case how to point your domain to it.

30 thoughts on “4 Hosting Types Compared: Free and Paid Hosting and VPS

  1. Free, Free, Free; I have three sites hosting on three free hosting sites. Two have sub-domain names, still all for free. Why pay if you can do it all for free. Now all my sites are also on my PC. Where I edit on my PC then FTP to the hosting site. Where if the free hosting site ever bellies up. I can move quickly to another free hosting site with zero problems. As long the tools and it covers all the necessary needs. Then there really isn't no cons. I'm free what ever I want to do with my site. As I don't used their templates or webshell. All my work is done on my PC with all the HTML and CSS raw coding. Then simply upload though a FTP client. Some free sites do have tools you think they wouldn't have, at least at no extra cost. I haven't pay for a website since Geocities days. An Geocities isn't with us anymore.

  2. One thing I feel you skipped out on when talking about the self-hosting option is the complexity of security. When hosting locally you are required to manage not only your own web application such as doing updates to the framework (WordPress, Drupal, Node, Django, etc…) and code auditing. Assuring software is up to date and making certain that non of the updates might break your application. you also need to assure your network is secure by creating a DMZ. This way if an attacker gets into your Network they'll need to bypass a firewall, else your entire LAN is exposed to some shitty script kiddie from India.

    Web based attacks are one of the hottest areas in infosec right now because most Devs suck at Sysops. Remote exploits drop in major Web frameworks everyday and most developers use so many libraries from various sources – maintaining and managing them all is rare (to be fair package managers gem, pip, node all all working to combat this). Worst of all with all of the external inclusion of code most of developers do not understand their code to the full extent this can make effective code auditing a nightmare.

    if you are still so inclined. best way to run locally hosted sites is a container on a VM separated on a DMZ subnet with a decent firewall separating your LAN (I recommend pfsense since it's free and high quality). Process/Network isolation is absolutely critical here if you don't want to get screwed by some 14 year old kind from hyderabad testing Kali Linux on your home network….

  3. Surprised you didn't mention Netlify, I use it for 3 of my sites and it is great, as you can easily host small websites, or informational websites, also, you could easily depend on Firebase as the backend, and pay almost close to nothing for a small site.

  4. Why not using AWS Lambda? They have 1 million request per month free and another 1 million is 0.20$. For most people's personal website you would probably never pay anything.

  5. Some OpenNIC coverage would be cool. I'm just starting to look into it, but it's free and requires a custom DNS, making it somewhat separate from the normal web. If people are mostly hosting text it could also be cool to look into the Gopher protocol. OpenNIC will even give you a .gopher TLD for gopher sites.

Leave a Reply

Your email address will not be published. Required fields are marked *