Unity Gaming Services

Serverless Cloud Code validation scripts

Server-side logic runs as Cloud Code scripts (JavaScript) or modules (C#) in a serverless environment. Scripts validate client requests but don’t maintain persistent game state.

Partial — shared .NET types only, not execution

Cloud Code modules can reference shared .NET types for data contracts, but client and server don’t execute the same logic. No deterministic re-execution or state synchronization.

Suite of independent cloud services

UGS consists of separate services (Cloud Code, Cloud Save, Economy, Remote Config, etc.) each with its own API. Services communicate via REST calls, not a shared runtime.

Mostly closed; Netcode for GameObjects open source

Backend services are closed-source Unity SaaS. The Netcode for GameObjects networking library is open source on GitHub, but it handles client networking, not backend logic.

Key-value Remote Config with JSON schema

Remote Config stores key-value pairs with optional JSON schema validation. Supports targeting rules and A/B testing, but lacks spreadsheet import or typed object compilation.

Fixed SaaS dashboard (Unity Dashboard)

The Unity Dashboard provides web-based management for all UGS services. It is a standard SaaS interface with no source code access or extensibility beyond the provided REST APIs.

Managed only (Unity cloud)

All UGS services run exclusively on Unity’s cloud infrastructure. There is no self-hosting option — the platform is tightly coupled to Unity’s multi-tenant environment.

Serverless auto-scaling per service

Each service scales independently in Unity’s serverless environment. Developers don’t manage capacity, but also have no control over scaling behavior or resource limits.

Cloud-only for backend services

Backend logic must be deployed to Unity’s cloud for testing. The Unity Editor integrates with UGS services, but there is no local backend server for offline development.