SpacetimeDB 2.0 just dropped, and it looks like a really interesting fit for real‑time and multiplayer Three.js projects.

In 2.0, your game logic runs directly “inside” the database, and it streams state changes out to connected clients, which can include a Three.js front end. You define tables for your world state (players, entities, transforms, systems), reducers for mutations (movement, damage, spawning, etc.), and views for derived, read‑only data. The Three.js client can then subscribe to those tables/views over WebSockets and receive fine‑grained diffs, instead of constantly polling an API.

For us as Three.js devs, this means the server can act as the authoritative world simulator, while our client code focuses on rendering and interpolation. Typical workflows like “entity moved,” “projectile spawned,” or “player joined” map very naturally to adding/removing/updating meshes or instances in a Three.js scene. It feels like a strong building block for anything that needs low‑latency, synchronized 3D state: multiplayer games, collaborative editors, shared data visualizations, or virtual worlds.

Curious if anyone here has already experimented with SpacetimeDB 2.0 + Three.js, and what patterns you’re using for syncing transforms, culling, and interpolation on the client side.

SpacetimeDB Free Tier

generous free tier, and paid tier with much higher limits is only $25 a month

What are you going to build with Spacetime?

I see this database pop up on Hacker News from time to time. I think it’s an interesting piece of tech, but I find their insistence on marketing it as a game engine type thing bizarre. There’s no advantage to using it to make games over making any other type of software service.

One comment I think sums it up well: SpacetimeDB v1.0: Multiplayer at the speed of light | Hacker News

”I kept on reading expecting to see motion prediction, multiversion, or similar given the name and focus on games, but no. This is a totally normal database, designed for low latency and with support for WASM stored procedures. You can host your own server or they will rent you one.

Don’t get me wrong, this looks very nice. It looks like a solid building block for persistent worlds in multiplayer games. You’ll just have to do your lag masking netcode yourself.”

That’s a fair take — the marketing definitely blurs the line. But I think their “game engine” angle is less about competing with Unity or Unreal and more about emphasizing real-time multiplayer sync. Traditional app databases don’t usually focus on low-latency state replication between clients.