Core stack
A modern React foundation for long-term product work.
Next.js 16React 19TypeScript
What InGaming is today
InGaming is not a turnkey platform or a bundled backend. It is a frontend product split into two repositories: the operator admin and the casino frontend foundation, both already shaped by real product and UX decisions.
Two product surfaces, one foundation
One repository covers operator work. The other covers player-facing sites. They stay separate because the product problems are different, but together they define the current InGaming scope.
The commercial split follows the same logic: admin-only if you only need the operator product, or the full package if you also want the casino frontend repository.
Admin only
ingaming-admin
Backoffice repoOperator-facing admin product for players, payments, content, permissions, and day-to-day workflows.
Admin + casino frontend
Everything in Admin onlyingaming-sites
Player-facing repoCasino frontend repository with reusable structure and two brand directions already explored.
Why it exists
Across iGaming projects, the backend is usually where the serious investment goes, and the frontend surfaces are treated like an afterthought. That shows up in admin tools that are slow and inconsistent, and in casino sites that get rebuilt brand by brand without a reusable system behind them.
InGaming was built to fix both sides of that problem: a serious operator admin first, then a reusable casino frontend foundation instead of another one-off build.
No bundled backend and that's the point
InGaming ships with demo data, not a production backend. That is intentional. Operators already have their own auth, payment providers, compliance logic, and business rules. Bundling a fixed backend here would create more rewrite work, not less.
Integration model: you bring your backend. InGaming provides the frontend surfaces and the boundaries to connect them cleanly.
Tech stack
The stack is modern and production-grade, but it is still a supporting point rather than the main reason to buy. The codebase is structured to make extension and long-term maintenance predictable.
Next.js 16
React 19
TypeScriptUI system
Fast iteration with reusable, consistent interface patterns.
Tailwind CSSshadcn/uiTheme support
Tailwind CSS
shadcn/uiCode structure
Organized to keep domain logic and UI boundaries clear.
FSDReusable widgetsShared UI
FSDIntegration model
Prepared for backend boundaries, demo data, and multi-project product work.
API boundariesDemo data layerMulti-project setup