Built InGaming as a frontend MVP for the iGaming space, with two main parts:
1. a back-office admin for casino / gambling operations 2. a multi-brand storefront system for casino sites
The starting point was simple: in all the years I’ve worked around iGaming, I haven’t seen a single admin panel I’d call genuinely good. Most of them are either bloated, awkward to use, or patched together from disconnected tools that don’t really fit how teams work day to day. So I decided to build the kind of admin I actually wish existed.
On the admin side, the MVP includes flows for players, payments and transactions, casino and sportsbook operations, content and static pages, reporting, and website configuration.
On the storefront side, I built a separate frontend repo to validate a multi-brand setup on shared foundations. Right now that includes two demo brands: BetStake and ShipBet.
Important caveat: this is frontend work and product validation, not a finished end-to-end platform. I’m treating it as an expanded MVP that is already strong enough to be a serious starting point, rather than just another rough concept.
What I’m really trying to figure out now is whether this is already valuable as a project someone could buy as a head start. My view is that it could save a lot of time for a team that would otherwise need to build the admin, storefront layer, and overall product structure from scratch.
Happy to answer product or frontend architecture questions.
Comments URL: https://news.ycombinator.com/item?id=47813386
Points: 1
# Comments: 0