Weekend Project or Second Job: SteamDB's Sale as the Test
Use a four-question borrowed-hours diagnostic to decide whether to keep, quit, or sell a project that has outgrown your available time.
Your side project is asking for your evenings again, and the SteamDB sale is a useful warning light. SteamDB's builder ran it mostly alone for 13 years, called the workload unsustainable, and started seeking a purchaser in January 2026 before Nexus Mods publicly said it bought SteamDB from Pavel 'xPaw' Djundik on September 2, 2026.
The sale shows the boundary
Chosen acquired Nexus Mods in June 2025. The financial terms of the SteamDB acquisition were not disclosed. Following the sale, the SteamDB site was expected to retain its existing name, web address, branding, and free features. Chosen's CEO said SteamDB's historical manifests, depots, and update records are valuable for modding.
This is not a template for every hobby. It shows the shape of the decision: a project can outgrow the person who built it, and the next step is to test the fit.
The diagnostic is about fit, not ambition
Most side projects stay side projects, and that is fine. The problem appears when maintenance, demand, and succession stop fitting your available time. You do not need a revenue threshold to know the project has changed. You need a test that can be run in a quiet evening.
The test is simple because the decision is simple. You are not choosing between passion and greed. You are choosing between a project that fits your life and one that does not.
Run the borrowed-hours diagnostic. Each question is meant to be answered in a minute, not a week.
- Maintenance hours: Can you claw back the maintenance hours by pausing updates, cutting one feature, or automating one task?
- Hidden costs: Are scrapers, bandwidth, or patience costs eating the project? Can you name the cost that is growing fastest?
- Succession: Is there a successor you trust? Can you point to someone who would keep it running without you?
- Need: Who actually needs what you built? Can you name the user group that would be hurt if it disappeared?
The first question protects your weekends. If the answer is no, the project is occupying your time instead of using it. The second question catches the quiet drain: a small site can still cost real hours when it is being scraped, monitored, or supported. The third question is the one most builders skip. A successor does not have to be a company. It can be a trusted user, a maintainer, or a community that can take over the boring parts.
The last is the hardest. If you cannot name who needs it, write down what the project is for you, then decide whether to keep it, close it, or hand it off.
A sale is a boundary, not a confession
Selling an indie project can feel like admitting the hobby grew too big, but it can also be a way to keep the thing alive while giving your evenings back. A buyer may care about the data, the users, or the maintenance burden, not just the traffic. The question is whether the project still fits the person who built it.
A buyer may also be a maintainer. If the project has outgrown your evenings but not your values, a sale can be the cleanest way to keep it useful.
Side project burnout is a signal that the boundary moved. If the project has become a second job, the next question is whether you want a second job. Keep the project bounded by a weekly time limit, a support window, or a pause date. It is different from deciding to quit your day job for a startup.
A side project exit can be a sale, a pause, or a clean shutdown. The move from side project to company is not the only path. Write the decision down before you add another feature, and follow it.