Infrastructure
How CloudWalker is wired into the platform
Infrastructure. CloudWalker is the hosting layer underneath both shared and dedicated deployments of the platform.
- What the connection carries
- 3 capabilities, listed in full below
- Who owns what
- Scalara owns the integration and the record it writes. CloudWalker owns its own service, under its own terms.
What the integration covers
The capabilities this connection actually carries. Anything CloudWalker sells that is not on this list is not part of what you get here.
Hosting for platform deployments
The infrastructure layer that shared and dedicated deployments of the platform run on.
Separation between deployments
A dedicated deployment is genuinely its own environment rather than a tenant on a shared one.
Included in the platform fee
Hosting is part of what the monthly platform fee covers, and is not billed separately.
CloudWalker is our infrastructure partner. They provide the hosting layer the platform runs on, for our own brands and for the deployments we sell.
Inside Scalara
Infrastructure is what makes the difference between a private platform copy and a skin. A dedicated deployment is a separate environment holding one operator's data, one operator's player accounts and one operator's financial history, and separation at the infrastructure level is what makes that statement true rather than aspirational. The same layer carries the shared deployments used by white label brands. Hosting, platform updates and the service level agreement are part of what the monthly platform fee covers, so infrastructure is not a separate invoice arriving from somewhere else.
The problem it removes
Operators who take a private deployment elsewhere usually inherit an infrastructure problem with it: a copy that drifts from the product, upgrades that turn into migrations, and a hosting bill that grows on its own schedule. Because every deployment runs the same codebase on a managed layer, an improvement reaches all of them from one release, and the operator does not acquire a platform team along with the platform.
What stays with you
Where your deployment sits, and what your data residency requirements are, are decisions we take with you rather than defaults we apply. Those requirements are often driven by your licence and your target markets, so they belong in discovery. On a dedicated deployment you also keep the choices that come with ownership, including how your environment is scaled and when it changes.
Where it sits on the platform
It stands behind private platform copies and security architecture.
Questions about CloudWalker
On a dedicated deployment, completely. A private platform copy is your own environment holding your infrastructure, your data, your player accounts and your branding, and there is nothing shared for another customer to reach.
On shared deployments, brands are separated at the identity and account level, so credentials and player records do not cross between them. If data residency or isolation has a specific meaning for your licence, raise it in discovery, because it shapes where your deployment sits.
In the deployment your brand runs on, hosted through our infrastructure partner CloudWalker. On a dedicated deployment that is your own environment, and where it sits is a decision we take with you rather than a default we apply, because residency is often driven by your licence and your target markets.
On shared deployments, brands remain separated at the identity and account level. If residency is a hard requirement, bring it to discovery early, because it shapes the deployment plan.
See it running against your own operation
Commercial terms and jurisdictional availability are assessed with you during discovery.
