Your game's server, in a single evening.
Canvas, code, or voice — the platform wires up the rest. Local dev loop, generated SDK, and push-to-deploy built in.
Six things the Code pillar delivers.
Visual scenario composer
Drag, connect, trigger. Canvas authors server behaviour without opening a file.
Push-to-deploy from GitHub
Server code lives next to client code and auto-separates on deploy. No CI template to assemble.
Local dev loop and CLI
Run the full platform locally, typed SDK generated per installed plugin, iterate in your own IDE.
AI-authoring surface
Describe a scenario in plain language; the platform drafts the graph, you review before it ships.
Environments with branches
Workspace-level branches, history, and rollback — platform state tracked like code.
Live-cursor collaboration
Two authors editing the same Canvas at the same time, with presence indicators in forms.
Code fits three kinds of builders.
The only backend person on a small project
You carry client, server, and infra at once. Every hour spent re-assembling primitives is an hour not spent on the game.
Client assembled with AI, server foundation missing
You've composed the client in a few days; the server should take an evening, not a quarter.
Production multiplayer at a larger studio
Shipping a competitive multiplayer game? Start at Sync — Code is the authoring surface on top.
Anchor story forthcoming.
An AI-first day-in-the-life. How an indie tech lead assembles a playable multiplayer backend in an evening, with 80% of the work routed through AI. Sample journeys land here when the game does.
Walk through early access →Code composes five modules into one authoring plane.
- Open spec →CanvasVisual scenario composer. Drag-connect-trigger authoring for game server behaviour.
- Open spec →Cloud FunctionsServer code that sits next to client code and auto-separates on deploy. GitHub push as the deploy pipeline.
- In the platform →Place of CodeLocal platform emulation, CLI, and typed SDK generator per installed plugin. MCP endpoint for AI tools.
- In the platform →EnvironmentsWorkspace-level branches, history, and rollback. Platform state managed like code.
- In the platform →CollaborationLive cursors and presence inside Canvas and forms. Two authors on one scenario without conflict.
Code is included in the Platform tier.
Canvas-first and code-first are the same bill, two entry surfaces — billed on Platform MAU with no separate authoring charge. Hosting and Realtime are billed separately when your game runs on managed capacity.
Ready to wire up the backend?
Your client is ready. Your server's an evening away.