Userhoster
Real accounts and member data, self-hosted.
users.example.com/
members/ → sign up · log in · private data
public/ → public profiles & listingsHow it works
The heavyweight of the family. Where gamehoster is casual and ephemeral, userhoster is where real identity and long-term data live — the piece you add when a site needs people to sign in.
Real sign-up & login
Proper accounts with real authentication, hosted on your own server. A folder named for a domain becomes that members service.
Private member data
Each member gets their own long-term storage — the data they see when they log in, and only they can reach.
Public listings
Choose a slice to expose — profiles, directories, leaderboards — for the front of the site to show the world.
Members, done simply
Full accounts and ownership, without the sprawl. It does one job — people and their data — so the casual and realtime cases stay in their own services.
Long-term by design
Unlike a game session, a member and their data persist across visits. Log out, come back next week, and it's all still there.
Private and public sides
A clear split between what a member keeps to themselves and what the site is allowed to publish about them.
The identity layer for the family
Userhoster gives the other services something they lack on their own: a real person to attach data and progress to.
+ Gamehoster →
Turn ephemeral players into real ones — characters, progress and stats that survive past the end of a session.
+ Datahoster →
Own records as a member: data that belongs to a signed-in person rather than an anonymous writer.
+ Localhoster →
Surface public profiles and directories as fast static pages, pulled from the API at build time.
One box each
Each service runs on its own server and hosts every domain of its kind. Start with one of each; add more when the traffic asks for it.