Short answer. Gambling Soft is a modular casino platform available in two editions: PHP 8.2 with two separate services on Symfony 6.4 (described on this page) and a JavaScript/TypeScript edition on Node.js for teams that standardise on a JS stack. The PHP edition runs (the admin panel 2.0 and the poker room 2.0), a MySQL-compatible database, Smarty templates for 19 casino themes, queue workers, a cron scheduler with 28 jobs and the whole stack running in Docker Compose (web server with PHP, MariaDB, Redis, workers, admin panel, poker room). A buyer receives the complete source code of the engine, the admin panel, the poker room and all themes, 469 database migrations, the unit test suite with CI workflows, deployment scripts and module documentation under a perpetual licence. Only the licence check module is delivered in protected form (3 ionCube files); all business logic, payments, front end and admin panel are plain PHP. This page describes what is inside the PHP edition and what exactly is handed over; the TypeScript edition is delivered on the same terms and its stack sheet is sent on request. Prices are on the pricing page; the checks a buyer should make are on the due diligence page.
Technology stack
| Layer | Technology |
|---|---|
| Language | PHP 8.2 or newer across the engine, the admin panel and the poker room. Second edition: JavaScript/TypeScript on Node.js, same product scope, same licence terms |
| Casino engine and player API | Modular PHP application: request objects, validators and handlers (application layer), domain and infrastructure layers separated; Smarty 5 templates for the player front end |
| Admin panel 2.0 | Separate Symfony 6.4 application with Doctrine ORM, forms, validators and a role model; 59 sections |
| Poker room 2.0 | Separate Symfony 6.4 application with Doctrine ORM, 167 game handlers, its own schema and admin section; connected to the casino wallet through a bridge |
| Database | MySQL-compatible (MariaDB 10.11 in our own installation, MySQL 8 supported); 361 engine migrations and 108 poker migrations under version control, run by the migration runner on every deploy |
| Caching | APCu by default for brand configuration, key storage and catalogue data; the cache layer can be switched to Memcached or Redis for multi-server installations; report cache for heavy admin reports; shared per-brand game catalogue cache |
| Background work | Queue workers for mailings, parsers and reports; cron scheduler with 28 jobs (bonuses, cashback, tournaments, jackpots, exchange rates, partner rewards, catalogue imports, site checks, cleanup) |
| Deployment | The whole platform runs in Docker: Docker Compose with the web server and PHP (LiteSpeed in our installation, Nginx with PHP-FPM supported), MariaDB, Redis, queue workers and cron, plus the admin panel and the poker room as their own services; the same stack runs our own casino brands. Deploy script that pulls the code, checks the environment, runs migrations and warms caches; automatic static asset versioning |
| Quality | Unit test suite (121 test files) and PHP syntax gates in CI on every push and pull request; monthly release notes |
| Front end | 19 casino themes on shared components (cashier, bonuses, wagering scale, notifications), WebP images, self-hosted fonts and scripts, right-to-left layout for Arabic |
Architecture
The platform is a modular monolith for the casino core plus separate services where isolation pays off. The core (player API, wallet, cashier, bonuses, catalogue, themes) runs as one application that serves any number of brands and domains from one installation; every operation and report is scoped to the player’s brand. The admin panel 2.0 and the poker room 2.0 run as their own Symfony services next to the core and share its database or talk to it through bridges. Game providers and aggregators are connected through bridges with a seamless wallet, idempotent callbacks and GGR accounting per brand and label. Payment systems implement one interface (deposit, callback, payout, status), so a new gateway is added without touching the cashier. Long tasks go to queue workers and cron jobs, never into web requests.
We chose this shape on purpose: one deployable core is cheaper to host and operate for a start-up or a mid-size operator than dozens of microservices, while the admin panel and poker are separate because they have their own release cycles and load profiles. The same codebase runs our own casino brands every day, so fixes and performance work come from live operation, not from a demo.
Components
| Area | What is included |
|---|---|
| Player account management (PAM) | Registration (email, phone, social networks, Telegram), two-factor authentication with app codes, profile, documents, sessions, self-exclusion and deposit limits, multi-brand player scoping |
| Wallet and cashier | Multi-currency balances with atomic debits, currency change, deposit and withdrawal flows with cascading payment systems, withdrawal approval rules, payout guard, refusal reasons from gateways, payment history |
| Payments | Unified payment framework with 11 gateway integrations (cards, local methods, crypto processors) plus a crypto cashier on own wallets: USDT TRC20, Ethereum, Solana, Bitcoin, BNB Smart Chain, TRON |
| Games | Catalogue with categories, providers, hoster restrictions per brand, favourites, search, neutral game launch; bridges to game aggregators and direct providers with seamless wallet; free spins through bonuses; jackpots (real and showcase); slot simulator for demo brands |
| Bonus engine | Deposit bonuses, free spins, cashback, login streak, welcome chain, rescue bonus, deposit boost, promo codes, buff cards, VIP levels and points, wagering with per-category contribution, bonus notifications |
| CRM and retention | Segments, cohorts, LTV timeline, risk flags, retention campaigns, win-back and “leaving now” lists, email campaigns on the player’s language with bonuses attached, unsubscribe pages |
| Affiliates and agents | Promo partners, promo and agent links, CPA conditions, revenue share, partner statistics scoped to brand, affiliate tracking postbacks, pin codes and scratch cards |
| KYC, AML and anti-fraud | Identity verification through a KYC provider integration with sanctions (OFAC, EU, UN, UK OFSI), PEP and adverse-media screening included by default in the provider’s verification and kept up to date by the provider; the platform applies the verdict, verification status on payouts, multi-account signals at registration, deposit-request limits, blacklists for bets and emails, crypto wallet rental limits, approvals of large money operations by a second administrator, employee action log |
| Responsible gaming | Deposit limits, self-exclusion for a period or forever across all login methods, cooling rules for limit changes, player notifications |
| Sportsbook and poker | Betting module through a sports feed integration; poker room 2.0 with cash tables, tournaments, time bank, chat, statistics |
| Engagement | Tournaments, fortune wheel, jackpots, last wins, buff cards, VIP club, referral programme, player notifications (bell, list, push windows) |
| Support | Tickets and chat with attachments, AI assistant for first-line answers, Telegram notifications to staff, bug reports |
| Reporting | Live dashboard, income by brand with GGR by provider and daily chart, CRM reports, statistics by payout day, gateway balances and transfers, CSV exports, admin timezone |
| Multi-brand operations | Unlimited brands and domains on one installation, white label mode with credits, mirrors and routing, region restrictions, per-brand settings, templates and email senders, brand-scoped staff roles |
| Security | CSRF protection on all state-changing actions, rate limits on login and registration, 2FA for staff and players, signed provider and payment callbacks, console-only maintenance scripts, security audits in July and October 2026 (see release notes) |
Functional scope
The component table above is the architectural view. The functional list is longer: 156 features in 20 groups on the platform features page. Beyond the standard set of a casino platform (PAM, wallet, payments, games, bonuses, affiliates, KYC and AML, responsible gaming, risk, reporting) the delivery includes modules that most source-code offers price separately or do not have:
- Poker room 2.0 and a sportsbook module on the shared casino wallet.
- Crypto cashier on the operator’s own wallet pool: 5 networks, 7 coins, dedicated wallet per payment, early crediting on partial confirmations.
- CRM and retention suite: lifecycle segments, cohorts, first-deposit funnel, fading and lost player lists, win-back campaigns, bonus payback analysis, CRM letters in 11 languages.
- Engagement set: slot tournaments, progressive jackpots, wheel of fortune, buff cards, VIP program with point exchange, latest wins ticker, banners per device.
- Multi-brand operations: unlimited brands on one installation, self-service casino creation form, mirrors with automatic block checks, antiblock page, private VIP domain, per-brand SEO and custom code, white label on credits, API bridges for reselling game content with separate GGR accounting.
- Telegram: the casino as a Mini App with Telegram login, casino bot, staff alerts.
- Support: on-site chat with file upload and AI auto-replies by the brand’s rules, operator tickets, bug reports with screenshots.
- Agent and cashier network: agent balances, cash desks, printable PIN vouchers, cash operations report.
- Operations: nightly platform self-test, platform health screen, test game launches from the back office, action log, 8 staff roles, 10 site languages, sweepstakes and social casino mode for the US market.
What is handed over
- Source code of the casino engine and player API, the admin panel 2.0, the poker room 2.0 and all 19 themes, in plain PHP, JavaScript and Smarty templates. Only the licence check module is delivered protected (3 ionCube files); it is not tied to a domain or a server, checks the key locally without calling our servers, and a fully paid licence is never revoked or disabled remotely. A full ownership option (the code without protected files plus the intellectual property rights) is quoted on request.
- Database schema as 469 versioned migrations with the migration runner, so an installation can be upgraded reproducibly.
- Tests and CI: the unit test suite (121 test files) with its bootstrap and stubs, and the CI workflows for syntax checks and tests.
- Deployment: Docker Compose files for the whole stack (web server with PHP, MariaDB, Redis, workers and cron, admin panel, poker room), Dockerfiles, the deploy script, environment templates and the cron job set.
- Documentation: module READMEs (platform, admin panel, poker room, migrations, queue, tests, security, Telegram, crypto cashier) and the monthly release notes.
- Installation and warranty: we install the platform on your servers and keep a 12-month warranty; you keep root access. Code escrow is available under a separate agreement.
Module inventory
The casino engine is organised as 40 modules under one API, plus the admin panel 2.0 (59 sections) and the poker room 2.0 as separate services. Each module is a directory with its own code and, where applicable, README, migrations and tests.
| Module | Purpose |
|---|---|
| Player API | request objects, validators and handlers for every player action |
| Players | profiles, sessions, confirmations, 2FA, self-exclusion |
| Social login | Google, Facebook, Telegram with signed auth data |
| Domains and brands | multi-brand routing, mirrors, aliases, per-brand settings |
| Payments | unified gateway interface, 11 integrations, callbacks, payouts |
| Cashier flows | deposit boost, withdrawal rules, payout guard, cashier and agent desks |
| Crypto cashier | own wallet pool, 6 networks, rental, confirmations, admin page |
| Exchange rates | daily rates for all played currencies |
| Slots catalogue | categories, providers, images, restrictions, neutral launch |
| Game bridges | five bridges to aggregators and providers with seamless wallet |
| Bonus | deposit bonuses, free spins, promo codes, wagering engine |
| Cashback | scheduled cashback with watchdog |
| VIP | levels, points, exchange, rewards |
| Tournaments | slot tournaments with schedules and prize pools |
| Jackpot | progressive and showcase jackpots |
| Fortune wheel | sectors, probabilities, schedules |
| Buff cards | collectible cards with bonuses |
| Last wins | winners ticker |
| Retention | welcome chain, rescue bonus, login streak, win-back campaigns |
| CRM | segments, cohorts, LTV, campaign letters |
| Partners | promo partners, CPA, promo links and materials |
| Revenue share | monthly partner payouts |
| Referral | player referral programme |
| Affiliate postbacks | registration and deposit postbacks to affiliate networks |
| Anti-fraud | multi-account signals, deposit-request limits, blacklists |
| Safety system | risk flags, payout stop rules |
| Security | signed tokens, callback secrets, rate limits |
| KYC | identity verification provider integration with AML screening |
| Notifications | bell, lists, pop-ups, player event feed |
| Support | tickets, chat, attachments, AI assistant |
| Telegram | bot, Mini App, staff alerts |
| Email and SMS | providers, templates, limits, confirmations |
| Queue | workers for mailings, parsers, reports |
| Cron | 28 scheduled jobs |
| Migrations | versioned schema changes with a runner |
| Tests | unit suite with bootstrap and stubs |
| SSE | live event streams for the back office |
| Showcase | demo brand with a slot simulator |
| Geo | GeoIP country detection and restrictions |
| Key storage | configuration and secrets cache |
Support, updates and security evidence
- Support 24/7 (terms of work, clauses 9.4 and 12): incidents are accepted at any time via Telegram, WhatsApp, email and tickets. First response: a critical incident (site, games or payments unavailable) within 1 hour at any time of day, high priority within 4 hours, other requests within 1 business day.
- Backups and recovery: full database backup every night, kept for 14 days; RPO up to 24 hours, RTO up to 4 hours after a critical failure (test restore on 6 October 2026: 11 minutes).
- Updates: fixes and security patches are rolled out to client installations during the 12-month warranty; afterwards technical support is $1,980 per 40 hours or under a support agreement. Every change is listed in the monthly release notes.
- Security evidence: full code audit in September 2026 across 12 attack areas; every critical vulnerability reachable from the internet without a login was closed within 16 days and re-tested; the current audit status report is available to buyers under NDA. The July and October 2026 audit items are listed in the release notes.
- Demo: a back-office demo account with a guided tour, live brands on our own installation, and a demo of your configured platform before the second payment.
Track record and licence
- Gambling Soft has developed online casino software since 2010; the history of this site since June 2010 is in the Wayback Machine. The platform repositories hold 17,000+ commits. 20 casino brands run on our own installation of the platform, so every release is tested in live operation before it reaches clients.
- Licence (terms of work, clause 8): perpetual; modify the code and use it in any number of your own projects; run casinos for other operators on your infrastructure (white label). Prohibited: resale, transfer to third parties, publication. Payment in three equal parts: advance, after the demo of your configured platform, after acceptance. Public price list on the pricing page. Full ownership option on request: the code without protected files and the transfer of the intellectual property rights, including resale (clause 8.12).
What this means against other offers
- No lock-in by design. Perpetual licence, code on your servers, root access, a stack any PHP or TypeScript team can hire for, 469 migrations and a test suite in the box. Three licence-check files are the only protected part, and we say so in writing instead of hiding it; they cannot switch the platform off, and a full ownership option without them is available.
- Proven in production, not in a demo. The same code runs 20 casino brands of our own every day; fixes reach clients through monthly release notes compiled from the repository, with 439 changes in October 2026 alone.
- Public terms. Prices, support response times, backup targets, warranty and payment schedule are published, so a buyer can compare offers without a sales call.
- Wider scope for the money. Poker room, sportsbook module, crypto cashier on own wallets, CRM and retention suite, multi-brand operations and a Telegram Mini App are included, where other source-code offers stop at PAM, wallet and games.
- Two editions. PHP or TypeScript, chosen by your team, not by the vendor.
If Gambling Soft disappears
Buyers of source code ask this question first, so the answer is in the contract, not only on this page. The platform does not depend on us to keep running:
- The code is on your servers. You hold root access and may export a full copy of the database, files and source code at any time (terms of work, clause 8.11).
- Nothing can be switched off remotely. The licence check in the three protected files verifies the key and the dates locally, does not call our servers and does not stop the software while the licence is valid; a fully paid licence is perpetual and is never revoked or suspended (clauses 8.6, 8.7 and 8.9).
- The project maintains itself. Migrations, unit tests, CI workflows, Docker Compose files, a deploy script, module READMEs and monthly release notes are part of the delivery, so your own team or any PHP or TypeScript team continues development without us.
- Escrow and full ownership. Code escrow with an independent agent is available under a separate agreement, with release on liquidation or after 30 business days without support (clause 8.9). A full ownership option, the complete code without protected files plus the transfer of the intellectual property rights including resale, is quoted by the manager on request (clause 8.12).
Before you buy: code review and references
Under NDA we give your developer or an independent auditor read access to the repository for 5-7 days, or hold a live session where we open the code and the Git history on screen. On the same terms we give the contacts of two operators running the platform, so you hear about delivery, support and stability from them, not from us. The rest of the checklist is on the due diligence page.
What we do not claim
- RNG and game certificates (GLI and similar laboratories) belong to the game studios and come with their content; Gambling Soft does not hold its own laboratory certificates for the platform.
- Certification of the platform for a specific regulated market is a separate project priced per jurisdiction; it is not included in the licence price.
- We do not publish aggregator and provider names in marketing texts; the list is shared under NDA during due diligence.
FAQ
Is the platform microservices or a monolith? A modular monolith for the casino core with two separate Symfony services (admin panel 2.0 and poker room 2.0) and bridges to providers and payment systems. For an operator this means one server set to run and one deploy to make, with the heavy or isolated parts split out.
Which parts of the code are closed? Three files of the licence check module, delivered through ionCube. Everything else, including wallet, payments, bonuses, catalogue, themes and both Symfony applications, is open and editable.
Can my team maintain it without you? Yes. The stack is PHP 8.2, Symfony 6.4, Doctrine, Smarty and MySQL; migrations, tests, CI, Docker Compose and module documentation are part of the delivery; any PHP team can take over.
How do I verify this before paying? Through the demo of your configured platform before the second payment, the due diligence checklist and the release notes, which are compiled from the repository history every month. Under NDA you can also review the code (read access for 5-7 days or a live session with the Git history) and talk to two operators running the platform.
Is there a version not in PHP? Yes, a JavaScript/TypeScript edition of the engine on Node.js. Write to us with your stack requirements and we will send its description.
What does it run on? Any Linux server you choose, either as the delivered Docker Compose stack (web server with PHP, MariaDB, Redis, workers, admin panel, poker room) or installed directly with PHP 8.2+, a MySQL-compatible database, PHP-FPM behind a web server, APCu (or Memcached or Redis as the cache backend) and cron. We recommend a configuration and install it.