A weekend. A backend. No netcode.
Liam is not a programmer. He uses an AI coding assistant and Canvas. By Sunday he has a multiplayer game with 30 concurrent players. Here's the two-day build.
Non-programmer using AI coding assistant and Canvas to build a multiplayer game backend in a weekend.
Draw the backend
Liam opens Canvas and describes the game to his AI assistant: “co-op puzzle, four players, shared inventory, a leaderboard.” The assistant drops three nodes on the canvas — Sync session, Market inventory, Lens scoreboard — and wires them together.
He edits labels, tweaks a capacity number, and hits Deploy. The backend is running before lunch.
Connect a client
He opens a Unity starter project, asks the AI to wire the Sync SDK to his Player prefab. The assistant adds [Sync] attributes to the right fields. Two editor instances connect. The inventory syncs. The scoreboard ticks.
Friends playtest
Sunday morning, 12 friends join a Discord. Liam shares a WebGL build — no server to provision, no Hathora account to create, no port forwarding. Peak concurrency hits 14. The session survives a dropped connection without him having to build reconnection logic.
Ship it
He posts the build link in a gamedev subreddit. Thirty strangers show up over the evening. Free tier covers 50 CCU; he's nowhere near the ceiling. Zero cloud accounts created. Zero vendor onboarding.
“I don't write code. I describe what I want. Canvas handles the backend; the AI handles the client glue.”
A weekend project, online.
Bring an idea and an AI assistant. We'll show you Canvas in a demo.