# GameVault: a self-hosted Steam-style client for DRM-free game libraries > GameVault is the client application for a self-hosted gaming platform that organises DRM-free games sitting on your own file server. It is C#, source-available under CC BY-NC-SA 4.0, and the README points to gamevau.lt for guides rather than documenting an install path in the repository itself. **Phalcode/gamevault-app** — Frontend for the self-hosted gaming platform for drm-free games - Repository: https://github.com/Phalcode/gamevault-app - Website: https://gamevau.lt - Stars: 802 · Forks: 51 - Language: C# - License: NOASSERTION - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/phalcode-gamevault-app ## The problem GameVault picks, and who actually has it A folder of DRM-free games is easy to create and hard to live with. Installers, patches and loose executables accumulate, nothing tracks what you own, and sharing the collection with friends means handing out paths and hoping they can find the right binary. GameVault's README frames the project as a self-hosted, source-available alternative to popular gaming platforms, and describes the goal plainly: let you and your friends enjoy DRM-free games stored on your file server "in an organized way." The phrase it uses for the result is a self-hosted Steam. The audience is narrow and specific. You need a file server already holding games you obtained legally, at least one other person you want to give access to, and a willingness to run the backend that the client talks to. The README is explicit that this repository is the client application, not the server, so anyone arriving here expecting a complete stack has half the picture. The legal disclaimer reinforces the boundary: GameVault manages DRM-free games, it is not responsible for what users store or share, and the project states that it does not endorse piracy even though it acknowledges the tool could theoretically be pointed at illegally obtained files. That is a positioning choice as much as a legal one, and it shapes who the project is written for. ## Client, server and the split the README does not explain The repository layout is the clearest signal of the architecture. The top level holds gamevault.sln, a gamevault/ directory, and the usual community files: CHANGELOG.md, CONTRIBUTING.md, LICENSE, README.md and SECURITY.md. The C# solution file means the client is a .NET application, and the README repeats that "the project you are looking at right now is the client application." What that implies is a two-part system where the client is the presentation layer and something else, hosted by you, serves the library. The README never describes the data flow between them, the protocol, or the API surface. It does not say how the client discovers a server, how authentication works, or where game metadata comes from. It points to gamevau.lt for "useful guides and information" and stops there. For an engineer deciding whether to adopt this, that gap matters more than the feature list: you are being asked to run a client whose counterpart is documented elsewhere, and the repository you are reading will not tell you what the counterpart expects. The topics list confirms the framing: frontend, gamevault, gaming, platform, self-hosted, source-available. Frontend is the operative word. ## Getting the GameVault client and reaching a first library The README does not contain install steps. It does not list a package manager, a download URL for a binary, a Docker image, or a build command. What it does say is that you can "learn more about the project and find useful guides and information on the official Website" at gamevau.lt. That is where the project says to get it, so treat the website as the entry point rather than the repository. For anyone who wants to build the client from source, the solution file at the repository root is the starting point: gamevault.sln, alongside the gamevault/ directory. The README does not document the target framework, the required .NET SDK version, or any platform-specific dependencies, so the repository gives you the entry file and nothing else about how to build it. The CHANGELOG.md at the top level is the place to look for what changed between releases. The most recent releases listed are 1.17.5.0 on 2025-12-13, 1.17.4.0 on 2025-11-13 and 1.17.3.0 on 2025-11-08, so the release cadence through late 2025 was roughly monthly, with two releases eight days apart in November. The repository's last push was on 2026-08-25, which is recent enough that the project is not dormant, though the README does not describe what that push contained. Before building, read CONTRIBUTING.md and SECURITY.md. The former is where build prerequisites would normally live if they exist anywhere in the repository, and the latter tells you how the maintainers want vulnerabilities reported. Neither is summarised in the README. ## Where GameVault stops being the right tool The licence is the first hard limit. The README states the work is licensed under CC BY-NC-SA 4.0 and adds, without hedging, that "this project is not and never was open-source," linking to a blog post explaining why. The repository metadata marks it source-available, and the GitHub licence field reads NOASSERTION, which is consistent with a Creative Commons licence rather than an OSI-approved one. The NonCommercial clause rules out commercial use, and ShareAlike means derivative works carry the same terms. If your plan involves shipping the client inside a paid product, or building a proprietary fork, this licence is the wrong fit and no amount of technical merit changes that. The second limit is the missing backend. The README says this repository is the client. If you do not already run the server side, the client has nothing to talk to, and the repository does not tell you how to stand that up. Anyone evaluating GameVault from this repository alone is evaluating half a system. The third is documentation depth inside the repository. There is no architecture document, no API reference, no configuration schema, and no troubleshooting section. The README is short and points outward. That is a legitimate choice for a project that wants its guides in one place, but it means the repository is a poor source of truth for operational questions. If you need to know how the client behaves when the server is unreachable, or how it handles a library with duplicate entries, you will not find the answer here. ## How GameVault differs from a plain file share The obvious alternative is not another game platform. It is a network share, a Syncthing folder, or an SFTP account. Those solve distribution and nothing else. You get bytes on a disk and a directory tree as the interface. There is no library view, no metadata layer, no notion of who has access to which title beyond filesystem permissions, and no client that a non-technical friend can open without being taught the folder structure. GameVault's difference is the organised-library layer. The README's promise is that games stay on your file server but are presented through a client, which is the same split Steam uses: content lives somewhere, and the client mediates access. The trade-off is real. A file share works with zero components to maintain and any operating system that mounts a network drive. GameVault adds a server you must run, a client you must install on each machine, and a licence that constrains what you can do with the code. You are trading operational simplicity for presentation and access control. There is also the GameVault+ tier mentioned in the README's support section, which the project offers alongside donations on Ko-Fi, Liberapay, GitHub Sponsors and PayPal. The README does not describe what GameVault+ includes, so anyone weighing the free client against the paid tier should check gamevau.lt rather than assume feature gating from this repository. ## Maintenance, upgrades and what the licence costs you The release history is the most concrete maintenance signal available. Versions 1.17.3.0, 1.17.4.0 and 1.17.5.0 landed between 2025-11-08 and 2025-12-13, and the repository saw a push on 2026-08-25. The project is not archived. Beyond that, the README does not document a support window, a deprecation policy, or a migration path between versions. CHANGELOG.md is the file to read before upgrading, and it is the only upgrade documentation visible in the repository. The upgrade cost for a self-hosted client is mostly your own: you rebuild or reinstall on each machine that runs it, and you keep the client version compatible with whatever server version you run. The README does not state a compatibility matrix between client and server releases, so pinning both and reading the changelog before each jump is the cautious approach. There is no documented rollback procedure. On licensing, the CC BY-NC-SA 4.0 terms are unusual for a codebase and worth reading in full rather than skimming. Attribution, non-commercial use and share-alike are the three obligations. The project is candid that it is not open source, which means it will not satisfy procurement rules that require an OSI-approved licence. This is not legal advice; if you intend to redistribute the client or bundle it with anything, get your own reading of the licence text and the linked blog post before you commit. ## Conclusion Adopt GameVault if you already keep legally obtained DRM-free games on a file server and want a library front end that you control. Do not adopt it if you need permissive licensing, a commercially redistributable component, or a client whose build and install steps are documented inside the repository. Verify first whether the client package for your platform exists on gamevau.lt, and read the CC BY-NC-SA 4.0 terms against your intended use before you build anything on top of the C# solution. ## FAQ ### Is the GameVault app safe to use? The repository does not make security claims, but it does ship a SECURITY.md file, which is where the maintainers document how to report vulnerabilities. The README's legal disclaimer states that GameVault is solely a tool for managing DRM-free games and that users are responsible for complying with copyright law in their jurisdiction. Whether it is safe for your setup depends on the server you run behind it, which this repository does not document. ### What kind of games does GameVault manage? The README describes GameVault as a tool for DRM-free games stored on your file server, organised through a self-hosted client. It states that when the project says DRM-free games, it means games obtained legally, and that it does not endorse or support piracy. ### Is GameVault open source? No. The README states plainly that the project is not and never was open-source, and that it is licensed under CC BY-NC-SA 4.0. The repository topics describe it as source-available instead. ### Does the gamevault-app repository include the server? No. The README says the project you are looking at is the client application, and the top-level entries are a C# solution file plus a gamevault/ directory. The server side is not part of this repository, and the README points to gamevau.lt for guides on the wider setup. ### How do I install the GameVault app? The README does not contain install steps. It directs readers to the official website at gamevau.lt for guides and information. Building from source starts with the gamevault.sln solution file, but the repository does not document the required .NET SDK version or platform dependencies. ## Sources - [Issues](https://github.com/Phalcode/gamevault-app/issues) - [Phalcode/gamevault-app on GitHub](https://github.com/Phalcode/gamevault-app) - [Project website](https://gamevau.lt) - [README](https://github.com/Phalcode/gamevault-app/blob/master/README.md) - [Releases](https://github.com/Phalcode/gamevault-app/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/phalcode-gamevault-app