Gamehoster

Realtime multiplayer, hosted. Rooms, presence and live state.

Gamehoster/
  game.example.com/            ← a domain, hosting several games
    pong/        →  wss://game.example.com/pong
    asteroids/   →  wss://game.example.com/asteroids
  arcade.example.com/          ← another domain on the same server
    tanks/       →  wss://arcade.example.com/tanks
How it works The family

How it works

The same drop-a-folder idea as localhoster, but the payload is live state instead of files. A folder named for a domain becomes a realtime host on your own server, and each game inside it is served at its own path (wss://your-domain/your-game); players connect over a WebSocket and everything in a room stays in step. One server hosts many domains, each with many games.

Rooms & broadcast

A room is a shared space. Anything one client sends is relayed to everyone else in it, instantly. This is the core of any multiplayer game or live page.

Presence

The server tracks who is connected and lets go when they leave, so the room always reflects who is actually there right now.

In-memory & fast

Live state lives in memory with a short lifetime, tuned for low latency rather than long-term storage.

Casual by default

No sign-up to play. Arrive, pick a name, and you control your own character, ephemeral by design.

·

Enter a name

A player joins with just a display name and gets an ephemeral session that owns only its own character. Leave and come back, and you're someone new.

·

Reconnect mid-session

Drop the connection and your session resumes where it was, the same character, as long as you're back before it times out.

Part of the Localhoster family

Gamehoster is one of a set of small, self-hosted services that all work the same way: a directory of domain folders, mirrored to your own server.