PlayCanvas.

Self-hosted deployment, built from the private GitHub repository stevenlimo20123/playcanvas.

What is deployed here

  • Engine — release builds of the open-source PlayCanvas WebGL/WebGPU engine, served under /engine/.
  • Editor frontend — the production build of the open-source PlayCanvas Editor frontend (Vite bundles, styles, monaco, wasm), served from /js, /css, /json, /wasm and /static.
  • Source — the combined repository holds both projects as subdirectories: engine/ and editor/.

Editor frontend — live demo

Open the PlayCanvas Editor frontend (projects dashboard UI) built by this deployment. It boots from the bundles served here; because no PlayCanvas backend runs on this server, project lists stay empty and API actions show errors — the working editor lives at playcanvas.com.

Open the frontend demo →

Engine builds

UMD bundle /engine/playcanvas.js
ESM bundle /engine/playcanvas.mjs
ESM modules /engine/playcanvas/src/index.js
Usage <script src="/engine/playcanvas.js"></script>

About the Editor frontend

The PlayCanvas Editor frontend hosted here is the open-source UI of the editor. The complete editing experience — projects, scenes, asset pipeline, real-time collaboration — is provided by the PlayCanvas backend service at playcanvas.com, which is not part of the open-source repository. That is why the frontend has no standalone URL of its own: on playcanvas.com the HTML pages come from their backend, which also injects the session configuration the UI needs. This deployment serves the full frontend build (usable via the demo page above, which stubs that configuration) and the engine builds. To work in the real editor, sign in at playcanvas.com (a locally running frontend build can be loaded there with the ?use_local_frontend query parameter).