Multi-brand casino core: lobby, wallet, bonus engine, CRM and back-office — on one licence-aware platform.
Run several brands from a single instance, switch jurisdictions per brand, and ship a new skin without a rebuild.
Most platforms were built for one brand in one market.
Adding a second licence usually means a second instance, a second wallet and a second ops team. Reporting splits, bonuses drift, and compliance work doubles with every launch.
Sirius keeps one wallet, one player identity and one back-office, and lets each brand carry its own jurisdiction rules, game catalog and bonus policy. Launching brand number four costs about as much as brand number two.
What ships in the box.
Multi-brand lobby
Skins, menus and promotions per brand from one catalog; A/B-tested layouts without deploys.
Unified wallet
Fiat and crypto balances, bonus money and real money kept separate with full audit trail.
Bonus engine
Welcome packs, cashback, tournaments and free spins with wagering rules per jurisdiction.
CRM & segmentation
Lifecycle journeys, VIP tiers and triggers across email, push and in-lobby messages.
Compliance per brand
Limits, self-exclusion, reality checks and regulator reporting configured per licence.
Reporting & BI
GGR, NGR, retention and provider performance by brand, market and cohort; export to your warehouse.
Built for operators who live in the back-office.
From signed contract to first bet.
- 01 · week 1
Sandbox & keys
Brand instance, API keys and test wallet provisioned.
- 02 · weeks 2–4
Frontend & content
Skin the lobby or connect your own via REST + WebSocket.
- 03 · weeks 4–6
Payments & KYC
Altair and Rigel enabled per market, or your providers mapped.
- 04 · weeks 6–8
Compliance review
Jurisdiction rules, limits and regulator reports verified.
- 05 · weeks 8–12
Go-live
Soft launch, monitoring and 24/7 ops handover.
POST https://api.spacesoft.tech/v1/sessions { "brand": "nova-eu", "player_id": "p_8f2", "game_id": "g_starburst", "currency": "EUR" } 200 { "session_url": "https://play.nova.eu/s/…", "expires_in": 900 }
Pick the scope, not the feature list.
| Capability | Starter | Growth | Enterprise |
|---|---|---|---|
| Brands per instance | 1 | 3 | Unlimited |
| Jurisdictions | 1 | 3 | Any supported |
| Game aggregation | Core catalog | Full catalog | Full + exclusives |
| Bonus engine | — | Included | Included |
| CRM & journeys | — | Standard | Custom |
| SLA | 99.5% | 99.9% | 99.98%, dedicated |
| Pricing | [YOUR PRICE] | [YOUR PRICE] | On request |
Questions operators ask first.
How long does a Sirius launch take?
Typically 8–12 weeks from signed agreement to go-live, including the licence-dependent compliance review.
Can we migrate an existing player base?
Yes. Player accounts, balances, KYC status and bonus history are imported from your current platform, and the cut-over is rehearsed on a sandbox before go-live.
Which jurisdictions does the platform support?
Sirius ships rule sets for [N] regulated markets. Limits, self-exclusion and regulator reporting are configured per brand, so one instance can serve several licences.
Do we have to use Altair and Rigel, or can we keep our providers?
Either. Altair (payments) and Rigel (KYC) plug in natively, but Sirius connects to third-party PSPs and KYC vendors through the same adapters.
Is the platform offered as white-label or turnkey?
Both. Turnkey runs under your licence with your team; white-label runs under our licence and operations. The platform underneath is the same.
See Sirius running your brand.
A 45-minute walkthrough of lobby, wallet and back-office on a sandbox with your markets configured.