SpacetimeDB ThreeJS Support

Devs split over SpacetimeDB 2.0: game engine vibes or just a speedy sync tool

TLDR: SpacetimeDB 2.0 adds real‑time Three.js support and a free tier, promising a database that streams game updates to players. The community is split: boosters love the “DB as game server” idea, while skeptics say it’s just a fast database—not a full game engine—so you still have to handle the hard multiplayer parts.

SpacetimeDB 2.0 rolled in with shiny Three.js support and a generous free tier, and the dev forum immediately turned into a reality show. One camp is all in on the pitch: let the database run the game logic and stream changes to players in real time. “Make the DB your game server,” cheers ryker2000, hyped about clients getting tiny updates over WebSockets (the web’s always‑on connection) instead of clunky refreshing.

But the plot twist? Skeptics are side‑eyeing the “game engine” marketing. A linked HN take calls it a fast, normal database with code plugins (WASM means “WebAssembly,” a safe way to run code in or near the DB), not a magic engine that handles lag or physics. Translation: cool backbone, you still have to write the tricky online multiplayer stuff yourself.

Meanwhile, practical builders showed up with real questions. siriusastrebe wonders what happens to massive, short‑lived stuff like destructible terrain—does it really belong in a database, or just in memory with a cache? usernamed7 says their current “scene‑as‑a‑document” setup makes multiplayer hard, and SpacetimeDB might finally be the missing piece. And agentifysh? “Perfect timing,” already installing.

Add in that “FASTEST database in the world” video thumbnail and a $25/month paid tier, and you’ve got weekend‑hack energy colliding with marketer‑hype eyerolls. The memes wrote themselves: “DB.exe is my new Dungeon Master,” “Hold my WebSocket,” and “It’s not Unreal, it’s Un‑real‑time (sync)”—the crowd is laughing and shipping.

Key Points

  • SpacetimeDB 2.0 runs game logic inside the database and streams state changes to clients.
  • Developers model world state with tables, use reducers for mutations, and views for derived read-only data.
  • Three.js clients subscribe via WebSockets to receive fine-grained diffs instead of polling.
  • The server remains authoritative while the client focuses on rendering and interpolation, suitable for low-latency synchronized 3D state.
  • Pricing includes a generous free tier and a paid plan starting at $25/month; an HN take describes SpacetimeDB as a low-latency DB with WASM stored procedures and hosting options.

Hottest takes

“makes the database your game server” — ryker2000
“temporary gamestate that doesn’t need to persist” — siriusastrebe
“this is pretty cool!... multi-player is ‘difficult’” — usernamed7
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.