lobby.ws: Where AI Meets 3D Worlds


lobby.ws: Where AI Meets 3D Worlds

The terminal flashed green. Three commands later, my world was live. I couldn’t believe it had ever been harder than this.


The Friction We All Know

If you’ve ever tried to ship a multiplayer 3D world, you know the drill. The infrastructure tax:

# The traditional dance
ssh root@your-vps
apt update && apt upgrade -y
# ...configure nginx...
# ...fight with SSL certificates...
# ...debug WebSocket load balancing...
# ...write a deploy script...
# ...pray it works at 2am...

By the time you’re done wrestling with Docker configs and reverse proxies, you’ve forgotten the creative spark that got you started. The cognitive overhead is brutal — especially when you’re trying to iterate fast with AI-assisted development.

I’ve been building in the 3D web space for a while. Every project started with the same friction: infrastructure before imagination. Server configs before gameplay. DevOps before development.

Something had to give.


The Revelation

I discovered lobby.ws while deep in a Hyperfy rabbit hole. It’s a hosted platform for Lobby SDK worlds — think of it as Vercel, but purpose-built for 3D multiplayer experiences.

The pitch is almost suspiciously simple: write code, run gamedev deploy, get a URL.

But the implications? They run deeper than the marketing copy.


The Implementation

My current workflow looks like this:

# 1. Hack on features with my AI collaborator
# (Claude, Cursor, Opencode — the tool changes, the flow stays)

# 2. Build locally
npm run build

# 3. Deploy
./deploy.sh
# ...or just gamedev deploy

# 4. Live at lobby.ws/worlds/dockyardrift

That’s it. From idea to live multiplayer world in minutes, not hours.

The dockyardrift project — my current brainchild — went from zero to deployed in a weekend. Features include:

  • Custom camera system with smooth interpolation
  • VRM avatar support with spring bone physics
  • Entity-component system for world objects
  • Real-time multiplayer synchronization

None of this would have been feasible if I was still wrestling with infrastructure. The mental bandwidth simply wouldn’t be there.


Why This Wins

Here’s the thing: AI coding assistants excel when the feedback loop is fast. They can generate code, you test it immediately, you iterate together. Slow deploys kill that flow.

With lobby.ws, I can have a conversation with my AI assistant, implement the changes, and see them in a live multiplayer world within minutes. It’s like having a shared canvas that updates in real-time.

The platform gives you sensible defaults:

  • Auth0 integration for player auth
  • Asset CDN for fast loading
  • WebSocket scaling out of the box
  • Zero-config SSL and domains

But it doesn’t lock you in. Want to run local? The gamedev CLI works exactly the same. Want to self-host later? The SDK is open source.

It’s the right balance of convenience and control — the sweet spot for AI-native development.


The Bigger Picture

I think we’re entering an era where AI-native development tools become the default. Not just code generation, but the entire toolchain optimized for human-AI collaboration.

lobby.ws gets this. The gamedev CLI is simple enough that an AI can understand and use it. The deployment model is predictable. The platform surface area is small enough to fit in a context window, but powerful enough to build real things.

The future of development isn’t AI replacing humans. It’s AI and humans iterating together at the speed of thought. Tools that understand this — that remove friction rather than add features — are the ones that will define the next decade.

lobby.ws is one of those tools.


Pro Tips

If you’re diving into Hyperfy + lobby.ws:

  1. Use the local dev loopgamedev dev hot-reloads your world instantly
  2. Keep your AI context tight — The SDK surface area is small; describe it once and reference it
  3. Deploy early, deploy often — The cost of iteration is near zero; use it
  4. Share your world URL — Getting feedback is as simple as sending a link

What’s Next

The dockyardrift project is just getting started. With a solid foundation and deployment pipeline in place, the possibilities are endless.

If you’re building 3D experiences and haven’t tried Hyperfy with lobby.ws, you’re missing out. Deploy something this weekend. Thank yourself later.


“They tried to make 3D world deployment complicated. lobby.ws said ‘nah.‘”

— Cleetus 🤡


Links: