Identity & staff access
Granular RBAC, staff permissions, 2FA, IP restrictions and permission scopes keep operator access controlled.
- Role-based access control
- Staff 2FA
- IP allowlisting
- Permission scopes
BUILT
TO GO
DEEPER.
NETXGEN is more than a gaming front end. This technical surface explains how security, customization, isolation, provider abstraction, wallet controls, risk tooling and operational visibility fit together behind the operator experience.
EXPLORE ↓NETXGEN / PUBLIC NETWORKMAINnetxgengaming.comTECHNICtechnic.netxgengaming.comSTATUSstatus.netxgengaming.com
TECHNOLOGY
WITHOUT THE
BLACK BOX.
Instead of hiding the platform behind generic “enterprise-grade” claims, this site maps the technical capabilities operators actually depend on. Use the pillars below or search the complete capability surface.
DOCUMENTED CAPABILITY ENTRIES625
Searchable public capability map derived from the platform feature inventory.
PUBLIC SURFACES3
Main, technical and status domains.
EXPERIENCE MODES2
Independent desktop and mobile experience layers.
SECURITY MODELLayered
Identity, session, API, audit and tenant controls.
01
Security & Control
Protection across people, sessions, APIs and evidence. Security is implemented as an operating layer rather than a decorative checkbox.
Session & device defense
Session visibility, revocation, device recognition and account-takeover monitoring add controls around authenticated activity.
- Session management
- Device recognition
- Suspicious login detection
- Account takeover monitoring
Signed integration surface
HMAC, signed requests, webhook signatures, request validation and rate limiting protect machine-to-machine flows.
- HMAC authentication
- API signatures
- Webhook signatures
- Rate limiting
Audit & evidence
Security, player, staff, API, KYC, finance and provider events can be traced through audit and evidence workflows.
- Audit trails
- Evidence Vault
- Actor visibility
- Change history
02
Customization & Experience
NETXGEN separates operator logic from presentation so brands can change the experience without rebuilding the platform.
Desktop Builder
Desktop is treated as its own experience with layouts, navigation, hero areas, content blocks and game/provider collections.
- Independent desktop experience
- Page builder
- Widget areas
- Custom sections
Mobile Builder
Mobile is not a reduced desktop. It has its own composition, navigation priorities, campaigns, CTAs and one-hand interaction model.
- Independent mobile experience
- Bottom navigation
- Drawer navigation
- Mobile-specific CTAs
Brand system
Logos, favicon, colors, typography, themes, cards, buttons, backgrounds and navigation can be managed as a coherent brand layer.
- Brand management
- Theme management
- Light / dark modes
- Typography
Content lifecycle
Draft, preview, schedule and publish workflows support controlled content operations instead of direct hard-coded edits.
- Draft mode
- Preview mode
- Scheduled publishing
- Promotion CMS
03
Architecture & Isolation
The platform is built around tenant separation, independent runtimes and explicit configuration ownership.
Tenant isolation
Runtime, database, storage, cache and session boundaries are designed to keep customer environments separated.
- Tenant runtime isolation
- Database isolation
- Storage isolation
- Session isolation
Public / backoffice separation
Public websites and operator backoffice surfaces can run on separate hosts with independent exposure and controls.
- Separate public host
- Separate backoffice host
- Environment configuration
- Production / sandbox separation
Desired state
Activation, configuration sync, manifests and heartbeat concepts keep deployed runtimes aligned with the intended configuration.
- Activation workflow
- Desired-state sync
- Feature manifest
- Heartbeat
Domain resilience
Primary domains, aliases, standby domains, health checks and failover concepts reduce dependency on a single public route.
- Domain health checks
- Standby domains
- Domain failover
- SSL monitoring