Homegames: A Free, Self-Hosted Platform for Making and Playing Browser Games

Homegames: A Free, Self-Hosted Platform for Making and Playing Browser Games
Homegames is a free, open-source platform that lets people play and create browser-based games without signing up for an account. That no-account requirement is significant because account friction — the hassle of signing up, logging in, remembering passwords — stops a lot of casual players from trying new games. By removing it, Homegames lowers the barrier to entry.
The platform bundles three tools together. The first is a browser-based code editor where creators can write game code and see it run live, even with multiple players testing at the same time. The second is a studio for managing game assets — you can upload files, draw freehand, and record audio. The third handles publishing, letting creators share games publicly or keep them private.
Games are built as JavaScript classes, which means writers use a familiar programming structure rather than learning a special game-design language. Importantly, the source code of every published game is open to read — any visitor can see how the game works. That architectural transparency is uncommon among game distribution platforms.
All the code — the platform itself, the games, and the website — is licensed under GPLv3, a license that ensures the code stays open and shareable. The entire codebase lives publicly on GitHub under the homegamesio organization. The platform is also designed to be self-hostable, meaning someone can run the entire system on their own hardware and API, without relying on the original hosted version staying online.
The project started in 2018 as a solo side project. It originally aimed to be a local multiplayer system — something like Jackbox or Spaceteam, where players in the same room use their phones as controllers. That idea has grown into a broader platform for creation and distribution, though the multiplayer sensibility remains in how the editor lets multiple people preview and test together.
The technical architecture is worth understanding if you are thinking of building on this platform or running your own instance. Because games are JavaScript classes, the runtime is lightweight and portable — creators get a familiar programming interface without a steep learning curve. The in-browser editor with live multiplayer testing suggests the server-side infrastructure that manages sessions is closely tied to the editing workflow. That is a more opinionated design than, say, a tool that exports games to run elsewhere. If you are planning to self-host, you will want to study how the API and session coordination work before you commit to server infrastructure.
Browser-based game creation tools have had ups and downs over the years. Platforms in this space often hit a difficult trade-off: a hosted service that gains an audience eventually faces costs for servers and infrastructure that a solo developer or small team cannot pay without charging users or getting outside funding. Homegames approaches that tension by design. Because it is fully open-source and self-hostable, the platform can survive even if the original hosted version shuts down. The community owns the tools and can run them independently.
The no-account design choice also has technical implications worth flagging. It rules out certain ways of storing game data linked to who a player is, which limits some game design patterns but makes link-based sharing much simpler — a mechanic that has powered viral distribution for browser games since the Flash era. For a platform that appears to rely on organic sharing rather than algorithmic recommendations, that trade-off makes sense.
Eight years of solo development without public funding or a commercial shift is a long trajectory for an open-source project. The real test ahead is whether the platform attracts enough contributors to move from a solo project to a community-maintained ecosystem. The GPLv3 license and public GitHub presence are the right structural conditions for that transition. The gap between having the right license and actually recruiting contributors who take advantage of it is where most projects like this tend to stall.


