Self-hosted AI with friends: what the setup really involves
The hardware is the easy part. Sharing it well is a people problem with a software answer.
People have been proposing this in local-model communities for three years, unprompted:
Imagine how much money you would save if, rather than renting a pod 24/7 for just yourself, you pooled your cash with some other people who also wanted to use those models. r/LocalLLaMA · December 2023
Would it be worth it for say 4 or 5 people to split the cost if I could provide free data center hosting?r/LocalLLaMA · March 2025
I wish I had friends that were actually into LLMs… I'd buy one and split the cost with 2-3 other friends.r/LocalLLaMA · May 2025
The idea keeps coming back because it is obviously right and slightly too much work to organise. Here is what the organising actually consists of.
First: you do not need friends for this
Read that third quote again. It is the most common version of this story — someone who wants a machine, can afford a share of one, and has nobody to split it with. That is a matching problem, not a hardware problem, and it is solvable: people who want the same tier get introduced, agree the terms in writing before any money moves, and end up with the same machine a group of friends would have built. What holds a group together is the agreement, not the friendship.
The hardware is the easy part
Buying the machine is a decision and a purchase order. Living with it is the interesting bit: several people who trust each other need accounts on one box, fair access to it, and enough privacy from each other to be comfortable. That is three separate problems.
Accounts, keys and the private endpoint
Each member should get their own account and their own API key against a private endpoint — not a shared password on a web interface. Once everyone has a key, the machine behaves like a private API that happens to belong to you: it plugs into the same editors, chat clients and scripts people already use, and nothing crosses the internet to a vendor.
Fair-share scheduling, before it is needed
Two people running long jobs at once on a single machine is where the friendliness gets tested. The answer is not a rota on a whiteboard, it is fair-share scheduling in the serving layer: queue requests, give each member a share of capacity, let short interactive requests jump long batch ones. Set it up while nobody is annoyed.
Privacy between members
Self-hosting solves privacy from the vendor. It does not automatically give you privacy from your friends — someone with root can read anything. Decide deliberately: who administers the box, whether prompts and logs are retained at all, and who can see usage. Most groups land on "usage totals are visible to everyone, content is visible to nobody", which is easy to configure and avoids an awkward conversation later.
Collectives work when somebody organises them. AI Horde has run a volunteer GPU cluster since 2022, EleutherAI built models as a community, Prime Intellect community-trained a 32B model in 2025, and exo's "cluster your own devices" project has 43,000 stars. The pattern is proven. What stops most friend groups is not capability — it is that nobody wants to be the one handling contracts, colocation and everyone's money.
Where it lives, and what that costs
A Starter box can sit in a member's home on ordinary power, $22–140 a month in electricity, and that is genuinely the right answer for three to five people running compressed large models.
Once you are into multi-GPU territory the machine goes to a real facility, because ten kilowatts of continuous draw is not a domestic proposition. It also puts the box on a proper network with proper uptime, which starts to matter the moment several people depend on it daily. In Bali we host it ourselves from $900 a month per machine, all-inclusive — electricity, internet, monitoring and control, and service. Anywhere else, the group finds a local facility and we hand over a machine that runs.
Where the arrangement actually breaks
Not the technology. The three failure modes we plan around are:
- Someone wants out. Without buyout rules agreed in advance, one person leaving can freeze the whole group.
- Uneven use breeds resentment. The heaviest user pays the same as the lightest one. Visible usage totals fix this socially, long before anyone has to raise it.
- The admin burns out. One friend quietly becoming the unpaid sysadmin is the most common quiet ending. Either rotate it deliberately or pay someone to do it.
What we do about it
We are the middleman and the builder, never the owner. We sell five things, each priced on its own: matching people into a group, supplying the parts from China, designing the machine, assembling it with the serving stack — member accounts, keys, fair-share scheduling — and hosting it in Bali. Each member is invoiced for their own share by Heroic24 LLC; there is no group fund and we never hold anybody's money. The machine belongs to the members from the day it is paid for, and our fees stop being our business the moment the work is done.
If that is the arrangement you have been half-planning in a group chat, put your group on the waitlist — group size and budget is all we need to tell you what your machine looks like. Or start with the cost calculator and bring real numbers to the conversation.