Docs Buy Now
Documentation › Getting Started › FAQ for Operators

FAQ for Operators

Getting Started · Updated March 15, 2026 · 9 min read

Answers to the most common questions from operators who have purchased the script.

Licensing and Usage

1. What does my license allow me to do?

Your one-time purchase gives you a single-site license to install and operate the script on one domain. The license includes:

  • Full source code access
  • Lifetime use of version 1.0.0 and all point releases
  • The right to modify the code for your own deployment

The license does not include:

  • The right to resell, sublicense, or redistribute the script (see question 11)
  • The right to operate multiple independent casinos under a single license
  • White-label rights to rebrand and resell the product as your own platform

If you need to run the script on multiple domains or build a SaaS product, contact sales for a multi-site or white-label license.

2. Am I responsible for obtaining a gambling license?

Yes — entirely. Online Casino Script is a software product. We sell you the technology; you are responsible for:

  • Obtaining the appropriate gambling operating license from your target jurisdiction’s regulator
  • Ensuring the software is configured to meet your license conditions
  • All compliance obligations including AML/KYC, responsible gaming, and player protection

The script includes tools that support compliance (KYC workflows, AML alerts, responsible gaming features, jurisdictional rules), but the legal obligation to operate lawfully rests with you as the operator.

3. Can I use the script without a gambling license?

We strongly advise against operating real-money gambling without a valid license in your target market. Gambling laws vary by jurisdiction. It is your responsibility to understand and comply with applicable law. The script may be used for:

  • Demo/staging environments (no real money)
  • Sweepstakes or play-money modes (verify legality in your jurisdiction)
  • Jurisdictions where real-money online gambling is explicitly permitted

Updates and Maintenance

4. How do I update to a new version?

Pull the latest code from your repository and follow the update steps:

cd /var/www/casino
git pull
composer install --no-dev --optimize-autoloader
npm ci && npm run build
php artisan migrate --force
php artisan config:cache && php artisan route:cache && php artisan view:cache
php artisan horizon:terminate
sudo systemctl restart php8.3-fpm

For Docker:

git pull
make down && make up
make migrate

Full details are in Developer: Installation Guide → Subsequent Deploys.

5. Are updates included in the price?

Yes. All point releases for v1.0.x are delivered to your repository at no extra charge. Major version upgrades (e.g., v2.0) may be offered as paid upgrades or discounted to existing customers — this will be communicated in advance.

Customisation and White-labelling

6. Can I customise the look and feel?

Yes. The frontend is a Vue 3 SPA with full source code access. You can:

  • Change colors, fonts, and logos via Admin → Settings → Theme (no code required)
  • Fully customise the frontend by editing resources/js/ and resources/css/
  • Swap out game assets, lobby layouts, and player-facing pages

The design system is documented in docs/guides/BRANDING_GUIDE.md. CSS design tokens are in client/shared/design-system.css.

7. Can I add custom games or payment providers?

Custom games: All games extend app/Services/Games/BaseGame.php and implement GameInterface. You can add a new game by creating a new service class, registering it in config/games.php, and adding a Vue frontend component. The provably fair RNG system is available to any game via ProvablyFairService.

Custom payment providers: Add a new adapter class in app/Services/Payments/. The payment system uses a provider interface — implement it, register the provider, and add the relevant .env credentials.

8. Can I rename or rebrand the software?

Yes, within your license. You can change the casino name, branding, and remove any product references from the UI. You may not present the software as an original product you developed for the purpose of selling or licensing it to others (see question 11).

Hosting

9. What server do you recommend?

For a production deployment serving real players, we recommend:

  • VPS or dedicated server: 8 vCPUs, 16 GB RAM, 100 GB NVMe SSD
  • OS: Ubuntu 22.04 LTS
  • Providers: DigitalOcean, Hetzner, Linode, AWS, OVH, or any provider that allows gambling-related services (some providers restrict this — verify before purchasing)

See Developer: Installation Guide → Server Requirements for the full hardware and software requirements.

Full Docker setup is available for development and smaller production deployments.

10. Does the script work on shared hosting?

No. Shared hosting does not support long-running processes (Horizon queue worker, Reverb WebSocket server) or the server-level configuration required. You need a VPS or dedicated server with root access.

11. Can I resell or relicense the script?

No. The standard single-site license does not permit:

  • Reselling the script to third parties
  • Operating a SaaS platform where multiple clients run on your infrastructure under your license
  • Rebranding and selling it as your own platform product

If you want to build a SaaS casino platform or sell white-labeled deployments, contact sales for a white-label/reseller license.

12. Is player data mine? What about GDPR?

All player data is stored in your own database on your own server. We have no access to your player data.

As the data controller, you are responsible for:

  • Complying with GDPR (if you process EU resident data) or equivalent data protection laws in your jurisdiction
  • Maintaining a privacy policy that accurately describes your data practices
  • Honoring data subject requests (access, deletion, portability)
  • Retaining data for periods required by your gambling license (typically 5 years for financial records)

The script includes a Privacy Policy template page (/privacy-policy) that you must update to reflect your actual practices before going live.

Technical

13. How do I set up SSL?

Use Let’s Encrypt (free) via Certbot. Full instructions including Nginx configuration are in Developer: Installation Guide → SSL Certificate.

If your server is behind a load balancer or CDN that terminates SSL, set FORCE_HTTPS=true in .env and ensure REVERB_SCHEME=https and REVERB_PORT=443 are set correctly.

14. What is provably fair, and how does it work?

Every game outcome is generated server-side using a provably fair RNG system. This means players can independently verify that the casino did not manipulate the outcome of any round.

How it works:

  1. Before a round, the server generates a random server seed and shares a SHA-256 hash of it with the player.
  2. The player provides (or the system generates) a client seed.
  3. The outcome is derived from HMAC-SHA256(server_seed, client_seed + ":" + nonce).
  4. After the round, the player can verify the outcome by revealing the server seed and re-running the derivation.

Players can verify any round using the built-in verification tool at Account → Provably Fair. Operators can access round verification data via the API at GET /api/provably-fair/verify/{roundId}.

The full RNG specification is in docs/certification/RNG-SPECIFICATION.md in the source repository.

15. How do I back up and restore the platform?

Backup scripts are included in scripts/backup/:

  • backup-database.sh — dumps MySQL to a compressed archive
  • backup-redis.sh — backs up the Redis RDB snapshot

Recommended cron schedule:

  • Daily database backup at 02:00 UTC
  • Retain backups for at least 30 days
  • Store backups off-server (S3, Backblaze, or equivalent)

To restore:

# Restore MySQL
mysql -u casino -p online_casino < /path/to/backup.sql

# Restore Redis (stop Redis first, replace the dump.rdb, restart)
sudo systemctl stop redis-server
cp /path/to/dump.rdb /var/lib/redis/dump.rdb
sudo systemctl start redis-server

Test your restore procedure before going live — a backup you’ve never tested is not a backup.

Support

Where do I get support?

Check the documentation in this folder first — most setup and configuration questions are answered here.

For issues not covered here, contact the support team through your purchase account portal. When raising a support ticket, include:

  • Your server OS and PHP version
  • The exact error message or behavior
  • Relevant log output from storage/logs/laravel.log
  • Steps to reproduce the issue

Response times vary by support tier. Business-critical issues (site down, payment processing failure) are prioritized.

Next →
Quickstart Guide