Ship sources, deploy to RGS, get a demo stand
A best-in-class pipeline: push the game sources, deploy them remotely to a staging RGS, and get a live demo stand to test and debug the real game — no local infrastructure.
From your sources to a live demo stand
One flow takes the game out of your workspace, onto a staging RGS, and back as something you can play and debug.
Remote deploy to a staging RGS
Push the game's sources and the pipeline deploys them to a staging RGS for you — no local servers, no manual setup, no environment drift.
Submit sources
Push the game's source straight from your workspace.
Deploy to staging RGS
Remote deploy to a staging RGS — no local setup.
A live demo stand to test and debug
Once deployed, you get a demo stand running the real game on the staging RGS — play it, find issues and debug before review.
What the pipeline handles
Source submission
Send the game's source from your workspace.
Remote deploy
Deploy to a staging RGS with no local infra.
Demo stand
Play the real game on the staging RGS.
Remote debug
Inspect and fix issues on the deployed build.
Validation flow
Collect release details and the selected build.
Fast iteration
Redeploy and retest without leaving the flow.
Publishing questions
How sources reach RGS and what the demo stand gives you.
No — the pipeline deploys your sources to a staging RGS for you, with no local infrastructure.
A live instance of the real game on the staging RGS that you can play, test and debug before review.
Yes — you can run and debug the real game remotely on the demo stand, then redeploy as you fix things.
You build with PlaySDK, then the publishing pipeline takes those sources to a staging RGS and back as a demo stand.
Ship your game to RGS
Deploy remotely, test on a real demo stand, and move toward a live game.
