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
ARCHITECTURE & ISOLATION
The platform is built around tenant separation, independent runtimes and explicit configuration ownership.
DETAIL ↓NETXGEN / PUBLIC NETWORKMAINnetxgengaming.comTECHNICtechnic.netxgengaming.comSTATUSstatus.netxgengaming.com
03
Architecture & Isolation
The platform is built around tenant separation, independent runtimes and explicit configuration ownership. The sections below describe the capability surface in customer-facing technical language while intentionally avoiding internal credentials, topology and commercially sensitive controls.
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