Homegames: An Open-Source, Self-Hostable Browser Game Platform Built for Makers

Homegames is a free, open-source game platform that lets users play, create, and share browser-based games with no account required to play — a design choice that removes the most common friction point in casual game distribution.

The platform bundles three distinct tools: a browser-based code editor with live multiplayer session previews for in-editor testing, a studio for managing game assets (supporting file uploads, freehand drawing, and audio recording), and a publishing layer that lets creators release games publicly or keep them private. Every game is implemented as a JavaScript class, and the source code of every published game is readable by any visitor — an architectural transparency that is relatively rare among game distribution platforms.

All platform code, games, and the website itself are licensed under GPLv3, which means the copyleft provisions apply throughout the stack. The entire codebase is hosted publicly on GitHub under the homegamesio organisation. Critically, the platform is designed to be self-hostable on a user's own hardware, API included — so operators are not dependent on the canonical hosted instance.

The project has been in development since 2018, largely as a solo side project. Its original goal was narrower than what it has become: a local multiplayer system in the vein of Jackbox or Spaceteam, where players in the same physical space use their phones as controllers. That couch-co-op premise has since broadened into a more general-purpose creation and distribution environment, though the multiplayer-first sensibility is visible in the live session preview tooling.

The technical surface area here is worth unpacking for anyone considering building on or self-hosting the platform. Games as JavaScript classes means the runtime model is relatively lightweight and portable — authors get a familiar object-oriented interface without needing to learn a proprietary DSL or engine API. The in-browser editor with live multiplayer previews suggests the server-side session infrastructure is tightly coupled to the editing workflow, which is a more opinionated architecture than, say, a tool that exports to a separate runtime. Anyone planning a self-hosted deployment will want to examine how the API and session coordination layer interact before committing to infrastructure choices.

The broader context here is that browser-based game creation tools have had a mixed history. Platforms in this space have repeatedly collided with the tension between openness and sustainability — a hosted service that grows an audience eventually faces scaling costs that a solo maintainer or small team cannot absorb without monetisation or institutional backing. Homegames' answer to that tension is structural: GPLv3 licensing and full self-hostability mean the platform can survive a loss of the original hosted instance. The community retains the means of production, to use an old framing.

Worth noting is what the no-account-to-play requirement actually signals architecturally. It rules out server-side session persistence tied to identity, which constrains certain game design patterns but dramatically lowers the barrier for link-based sharing — a mechanic that has driven viral distribution for browser games going back to the Flash era. For a platform whose audience discovery model appears to be organic sharing rather than algorithmic recommendation, that is a coherent trade-off.

Eight years of solo development on an open-source side project is a long runway without a public funding announcement or commercial pivot. Whether the platform reaches the kind of contributor critical mass that turns a solo project into a community-maintained ecosystem is, at this point, an open question. The GPLv3 licence and public GitHub presence are the right structural preconditions. The gap between having the right licence and attracting the contributors who act on it is where most projects in this category stall.