CoreStack Gaming/SPHINX
SPHINX
Start Further Ahead.
SPHINX is a Remote Gaming Server platform for studios, operators and platform providers who want to start from a production foundation rather than build the RGS beneath their games from zero.
- Infrastructure you deploy and operate.
- Operator integration handled at the platform level.
- A foundation designed to evolve with the business.
Product Document · SPHINX RGS
Architectural Overview
The blueprint below presents the principal architectural decisions behind SPHINX.
It provides the context for the engineering sections that follow.
Scroll horizontally to view full blueprint
01
Own the Platform
Skip the years of RGS groundwork. Take it from here.
Deploy SPHINX in your own environment, with source-code handover available as part of the commercial model. Start from a working RGS foundation while retaining control over how the platform is deployed, modified and extended.
02
Integration First
Purpose-built for operator and aggregator connectivity across the iGaming ecosystem.
Operator APIs, aggregator adapters and back-office interfaces are handled at the platform level, so each deployment starts from working integration patterns rather than a blank slate.
03
Extend Without Rebuilding
Games, adapters and workflows evolve independently without requiring platform rebuilds.
The foundation stays stable as the product grows, removing the coupling that slows most platforms.
A Simulated Operator, Included
SPHINX includes a Mock Operator environment for developing and testing games and platform integrations without depending on a live operator connection.
It can simulate multiple operator environments with different API behaviours, including failure and edge-case responses, so integrations beyond the happy path can be tested. The Mock Operator includes the player-facing game launch flow, wallet simulation and an admin portal for testing and configuration.
Its source code is included with the SPHINX source-code handover.
One Core, Three Paths.
SPHINX is the same platform in every case, including the Mock Operator environment covered above. What changes between the three paths below is who deploys and operates it, and how much control and responsibility stays with your team.
Source-code handover, in particular, is more than a repository. It includes the build and deployment material needed to actually run SPHINX, together with its architecture and API documentation.
You receive the SPHINX source code and can deploy, operate, modify and extend it independently in your own environment.
SPHINX is licensed for use under commercial terms agreed with CoreStack, with flexibility around how it is deployed and evolved within those terms.
CoreStack deploys and operates SPHINX on your behalf, reducing the operational responsibility your team carries.
Start a Technical Conversation
SPHINX. Custom engineering. Or something in between. Let's start the conversation.