Localhoster
Self-hosted building blocks for the web. Six independent services, each as simple as one folder, all running on your own server and synchronised automatically from your local machine.
Sitehoster →
drop a folder, get an HTTPS site
Author static sites as local folders named after their domains; a stateless client mirrors them to your server over HTTPS.
Datahoster →
drop a folder, get an API
Host API endpoints for your data. Declare a collection as a folder named for its domain; your server serves it over HTTPS.
Gamehoster →
realtime multiplayer, hosted
Host realtime state for multiplayer games: rooms, presence and live updates over WebSockets, on your own server.
Userhoster →
accounts and member data, self-hosted
Host real accounts and long-term member data: sign-up, login and each member's private data, on your own server.
Cronhoster →
drop a script, get a schedule
Run scheduled scripts on your own server. Name a JavaScript file for when it should run; a dedicated runner executes it on time.
Taskhoster →
drop a folder, get a task queue
Host durable task queues on your own server. Producers post tasks; workers claim them by capability, then post progress and results.
One home for the self-hosted family
Localhoster is a small family of self-hosted services built on a single idea: describe what you want as a plain local folder, and a tiny stateless client mirrors it to your own server, which serves it over HTTPS automatically. No platform to sign up for, no lock-in, and no per-project setup, just a folder named for its domain.
Whether you're publishing a website, exposing an API, running a multiplayer game, storing member accounts, scheduling background scripts, or opening a public port, it's the same simple workflow, and each service runs independently on hardware you control. Start with the one you need and add the others as you grow.