Short answer. This page is for the people who will actually run and extend the code: CTOs, lead developers and the engineers doing technical due diligence. Gambling Soft is a casino platform with a public price list, a transfer of exclusive rights option and 20 brands of our own in production, delivered as a Git repository with 17,000+ commits, 469 versioned migrations, Codeception test suites with CI, Docker Compose for the whole stack and a README per module. Below is what you open on day one, how the platform is extended module by module, the development rules we use ourselves, the quality gates every release passes and how your team stays current after the purchase. Everything here is checked against the repository during the code review under NDA; the architecture and the module table are on the architecture page.
Why engineering teams pick a running platform over a framework
- The hard part is already written and tested with real money. Idempotent bet, win and refund, replay protection for provider callbacks, round rollback, row locking with retry, reconciliation, payout guard, double-credit protection for crypto deposits, wins without a bet, multi-account and bonus abuse, one balance log. These are the bugs that cost operators money in year two; here they are closed and covered by tests and release notes.
- You get the engineering package, not only the files. Migrations with a runner, unit and acceptance tests, CI workflows, Docker Compose, Dockerfiles, deploy script, module READMEs, release notes since 2024. A new team reproduces the installation from the repository without us.
- You choose the stack. PHP 8.2 with Symfony 6.4 services, or the JavaScript/TypeScript edition on Node.js on the same terms.
- Two rights options. Perpetual licence never revoked, code on your servers, root access; or the transfer of exclusive rights (assignment, Offer clause 8.12) with 100% of the source and the exclusive property rights to your copy.
- It is already running. 20 brands on our own installation take every release before clients do, so your upgrade path is tested in production, not in a staging demo.
Day one: what you open
| Part | What it is | What is inside |
|---|---|---|
| Casino engine and player API | PHP 8.2, modular monolith | 40 modules under one API, each a directory with its own code and, where applicable, README, migrations and tests: players, wallet and cashier flows, payments with 11 gateway integrations, crypto cashier, slots catalogue and five provider bridges, bonus, cashback, VIP, tournaments, jackpot, fortune wheel, retention, CRM, partners, revenue share, referral, affiliate postbacks, anti-fraud, safety system, security, KYC, notifications, support, Telegram, email and SMS, queue, cron, migrations, tests, SSE, showcase, geo, key storage |
| Admin panel 2.0 | Separate Symfony 6.4 service | 59 sections, Doctrine ORM, Twig templates, voters for access control, translations, its own compose file and PHPUnit configuration |
| Poker room 2.0 | Separate Symfony 6.4 service | Cash tables and tournaments, rake, time bank, SSE, React front end, 108 migrations, PHPStan, pre-commit hooks, its own CI |
| Themes | Smarty 5 templates | 19 casino themes assigned per brand, with per-brand SEO and custom code slots |
| Database | MySQL-compatible (MariaDB 10.11 in Docker) | 469 versioned migrations (361 engine, 108 poker) with a runner, so any installation is upgraded reproducibly |
| Tests | Codeception | Unit suite with bootstrap and stubs, acceptance suite against a running brand through the REST and browser modules, slot test launches; 121 test files |
| CI | Workflows | Syntax checks and unit tests on every push; PHPStan and pre-commit in the poker room |
| Runtime | Docker Compose | Web server with PHP (LiteSpeed in our installation, Nginx with PHP-FPM supported), MariaDB, Redis, queue workers and cron, admin panel and poker room as separate services; environment templates; APCu cache by default with Memcached or Redis as alternative backends |
| Scheduler and queue | 28 cron jobs, queue workers | Catalogue parsers, exchange rates, cashback, tournaments, retention, mailings, crypto deposit watch, nightly self-test, acceptance tests; a job interface and reference implementations for every type |
| Documentation | READMEs and release notes | Platform, admin panel, poker room, migrations, queue, tests, security, Telegram and crypto cashier READMEs; monthly release notes since 2024 with every change grouped by module |
Day two: how the platform is extended
Every extension point is an interface or a module pattern with working examples in the repository. The table lists the common tasks a buyer's team does in the first year.
| Task | Where | How it is done in the code |
|---|---|---|
| Add a payment gateway | Payments module | Implement the payment system interface (name, deposit, withdraw, sufficient-balance check, auto-payout flag), register the system, add the callback handler with signature verification. 11 implementations (cards, local methods, crypto processors) serve as reference; cascading and withdrawal rules pick the new system up without changes |
| Add a game provider or aggregator | Game bridges | A bridge module implements the seamless wallet callbacks (balance, bet, win, refund, rollback) with idempotency keys and replay protection, plus a catalogue parser that runs through the queue. Five bridges serve as reference; brand, region and currency restrictions apply automatically |
| Add a casino theme | Themes | A Smarty template set in the themes directory; assign it per brand in the admin panel; per-brand SEO, banners per device and custom code are configuration, not code changes |
| Add a scheduled job | Cron module | Implement the cron job interface and register the schedule; 28 jobs show the patterns for parsers, notifications, settlements and self-tests |
| Add a background task | Queue module | Queue jobs for mailings, parsers and reports run on workers in Docker; add a job class and dispatch it |
| Add a bonus type | Bonus and Retention modules | Bonus entities with writers and validators, the wagering engine with per-category contribution and the notification hooks; existing types (deposit bonus, free spins, cashback, login streak, welcome chain, rescue bonus, deposit boost, buff cards) are the templates |
| Add an admin section | Admin panel 2.0 | Symfony controller, Twig template, voter for the role, translation keys; 59 sections show the conventions, including help buttons and instructions in templates |
| Add a player API action | Player API module | Request object, validator and handler; backend translations for DTO messages and asserts; unit test alongside |
| Add a language | Translations | Site languages (10 today) and CRM letters (11) are translation files and templates; backend messages are translated in the API layer |
| Replace the KYC provider | KYC module | The platform consumes a verification verdict and gates payouts by status; the current provider integration is the reference for a new one |
| Add a brand | Admin panel | No code: the self-service casino creation form creates a brand with its domain, theme, payment set, email sender and staff roles on the same installation |
Development rules you inherit
- Protected branches: nothing is pushed directly to the main or development branch; changes go through merge requests with review.
- Code style is enforced with php-cs-fixer and the sniffer on changed files; the poker room adds PHPStan and pre-commit hooks.
- CI must pass (syntax checks and tests) before a merge.
- Schema changes are migrations only; no manual database edits on any installation.
- Every change is listed in the monthly release notes, grouped by module, so a buyer's team reads the history instead of guessing it.
Quality gates every release passes
- Nightly self-test on the installation: database, registration and login, password recovery, stuck payouts, mail queue, exchange rates, crypto deposits and the test suite; results on the platform health screen.
- Acceptance tests against a live brand through the REST and browser modules, and test game launches from the back office after catalogue updates.
- 20 brands as the canary. Releases run on our own brands before they reach clients; October 2026 alone carried 439 changes.
- Security. Full code audit in September 2026 across 12 attack areas; every critical vulnerability reachable without a login was closed within 16 days and re-tested; the status report is available under NDA; audit items are listed in the July and October 2026 release notes.
- Backups. Full database backup every night kept for 14 days; RPO 24 hours, RTO 4 hours; test restore on 6 October 2026 took 11 minutes.
After the purchase: staying current or going your own way
- Hosted by us: we update your installation; fixes and security patches are included during the 12-month warranty and under a support agreement afterwards.
- Source-code licence on your servers: you receive releases from the repository under your support terms and merge them into your fork with Git; migrations and release notes make each upgrade a reviewable change set.
- After the transfer of exclusive rights: the transferred copy is your property; take our releases, fork for good, or both. Nothing in the code calls us.
- Found a defect? Send the reproduction to support; fixes are shipped to all installations and appear in the next release notes with the module named.
- Need a module we do not have? Build it on the interfaces above, or order it: poker $7,500, sportsbook $9,500, official slots package $5,500 and custom work at $1,980 per 40 hours are on the pricing page.
What engineers ask before buying
Monolith or microservices? A modular monolith for the casino core with two separate Symfony services (admin panel 2.0, poker room 2.0) and bridges to providers and payment systems. One deploy, one server set, with the heavy or isolated parts split out; each module has its own directory, README, migrations and tests, so replacing one is a bounded task.
Can we replace a module? Yes. Payments, game bridges and KYC are interfaces with reference implementations; bonuses, CRM and reporting are modules behind the player API; the admin panel and poker are separate services with their own repositories.
Which PHP versions? PHP 8.2 or newer across the engine; Symfony 6.4 LTS for the two services; MariaDB 10.11 in the reference Docker stack.
What is closed? Three files of the licence check module, delivered through ionCube, which verify the key locally and cannot disable the platform. The transfer of exclusive rights delivers them as plain PHP.
How do we verify all of this? Under NDA your developer or an independent auditor gets read access to the repository for 5-7 days, or a live session where we open the code and the Git history on screen; on the same terms you get the contacts of two operators running the platform. The rest of the checklist is on the due diligence page.
Is there a TypeScript edition? Yes, on Node.js, with the same product scope, licence terms and prices; its stack sheet is sent on request.