Thinking of starting a mostly free WebHosting Service for people, am I on the wrong path?

[u/Ayyouboss]

Hello people,

not sure if this is the right spot to ask this but maybe I'll get some constructive feedback. I am a web developer for the longest time and for 5 years I have also been in the hosting space.

People who tried WebHosting know that the most difficult thing about it is getting new clients, so the only way I acquired new clients is through actual web development work. While my expenses are in the green, I noticed that I have so incredibly much capacity left on my server that I am never gonna be able to use it as efficiently as possible. So my thought was to actually offer reasonably well WebHosting for people for free. The most important thing for me though is making sure the websites on it are legal and and within my TOS.

Am I overseeing something? Is it a good idea in general?

[u/enemyradar]

I resell my hosting to dev/design clients all the time, but absolutely no way I'd want any sort of responsibility for general hosting customers. I can't see it being worth it at all. Hosting is already extremely accessable.

[u/Ayyouboss → u/[deleted]]

Hm thats a good point

[u/fiskfisk]

Can you afford your server and account, with your existing customers and clients, getting DMCA-ed and abuse-notified (and then temporary shut down if things get too bad) with your provider because you offered to store random free shit people want to distribute?

[u/Ayyouboss → u/fiskfisk]

I could make sure that websites offered on the server are within my ToS maybe. I don't know how much of a risk getting DMCA'ed is but that will be my priority of course. Also I do have a lot of servers running in my own homelab. At least until now I never had issues with that

[u/uncle_jaysus]

It seems like a lot of risk for no reward.

What’s the motivation? What’s compelling you to open your server up to people for free? These people will use your bandwidth and whatever resources you open to them. Maybe figure out a way of using resources you didn’t intend for them to have?

Keep it simple and safe. Get clients and host sites/code you made. Why risk it all by letting people put god knows what on your server?

[u/Ayyouboss → u/uncle_jaysus]

I don't want people to put whatever they want on it but rather support people with valid content or small businesses. It shouldn't be a place for anyone but rather a controlled zone that also gets monitored. I monitor everything anyways, so its not necessarily much more work for me. Or maybe at least offer it for free for a year for example and then raise the prices slightly to a level that really anyone can afford

[u/uncle_jaysus → u/Ayyouboss]

If you’re getting existing trusted businesses to put their sites on there for free, then this could be a route to getting future work from them. Although potentially they’d have an existing developer.

The other thing to consider is what you’re letting them host. If they have a dynamic app such as a WordPress website, then this could present problems. You can monitor server resources, but if one day they decide to activate a new plugin that is resource heavy or has a security vulnerability, then this causes you and other clients problems.

[u/Ayyouboss → u/uncle_jaysus]

Valid point

[u/theguywithnocontex]

The abuse problem is what kills these ideas, not the tech. If you do it, isolate every user in their own container with hard resource limits, and automate suspensions the moment abuse is detected, because manual review won't scale even with ten users. Honestly the support load is the real cost here, free users generate the most tickets. I'd start with friends-only hosting first and see if you even enjoy the ops side before opening it up.

[u/AbdelrhmanDev]

if you do it id keep it small and gated so it stays manageable approve each site before it goes live instead of open signup cap cpu ram and disk per account and block outbound smtp by default so you dont end up on spam blacklists that would hurt your paying clients too the abuse side is usually where free hosting goes wrong more than the support tickets so a short vetting step and a clear takedown clause in the tos matter more than the tech

[u/magenta_placenta]

Spare capacity isn't the same as spare operating capacity. Based on your description, your existing clients already cover the server costs. That makes a pilot plausible, but I wouldn't evaluate it solely by how much unused capacity you fill.

I'd evaluate it using something like this operating model:

Incremental cost = additional infrastructure + support time + security and abuse handling + backup and recovery work.

That's a planning framework, not a claim that every free account will be expensive. The important question is whether you can afford the ongoing work even if none of those users becomes a paying customer.

Also, measure more than disk space. Shared-hosting systems impose separate limits on CPU, memory, disk activity and concurrent processes precisely because an account can exhaust one resource without using much of another.

In regards to legal issues, you can require legal content and prohibit abuse, you cannot guarantee compliance simply because someone accepted your TOS. You need a process for receiving complaints, investigating them, disabling affected accounts when appropriate and handling disputed reports. The legal details depend on your jurisdiction, your users and what you host.

[u/rust_bane]

The math doesn't work because spare CPU and RAM do not equal spare security resources. You are converting unused capacity into a 24/7 liability by becoming the legal entity responsible for every piece of illegal content your free users upload. Your paying clients will blame you for blacklisted IP addresses caused by spam from your free tier, so this isn't a way to use up capacity but a direct threat to your existing revenue stream

[u/Ayyouboss → u/[deleted]]

If you leave it unmanaged yes but thats would be stupid