Lochost

Lochost

Every local project at http://<name>.localhost, not at a port number

Lochost is the tool local-apps. It starts the local projects of one Mac in the background and gives each one a name instead of a port, through Caddy: http://<name>.localhost. Every page it serves carries the Admin Banner, the way into that project's admin, docs and tests. After every agent turn it brings each running app to its newest code.

A personal tool. It runs on its author's Mac and serves his own projects. It is not packaged for anyone else, and there is nothing to buy or install here.

See what it doesWrite to the author

Admin Banner /admin/ Docs Tests
A local app's page: the Admin Banner on top leads to the app's own admin, its Docs page and its Tests page.

What it does

A name instead of a port

Every app answers at http://<name>.localhost through Caddy. Browsers resolve *.localhost to 127.0.0.1 themselves, so nothing goes into /etc/hosts. Each server runs as its own launchd job, never as a child of whoever started it, and a crashed server runs again within 15 seconds.

One page of every app

http://local-apps.localhost/ is a grid of cards, one per app, each with a live preview over a saved screenshot, its local address and its public address. Cards of one project share a tile; the order is dragged by hand and kept, and a pattern search box filters the cards.

The Docs hub

Every app has a Docs page at /admin/docs/ on its own host: README.md, AGENTS.md and every document of the repository's docs/ folder, its plan (saved artifacts), its roadmap and its Notion pages, with full-text search and the project's logo. Notes that hold for every project are written once and shown on every Docs page.

One Tests page for every project

/admin/tests/ on every app's host shows that project's recorded test runs, newest first, the chosen run's failures with their output, and a retro of the most failing, flaky and slowest tests. Above them it shows the Mac's push queue: which pushes wait for their tests, and in what order. No repository keeps a copy of this page.

Follows every change by itself

local-apps reload runs after every agent turn and brings each running app to its newest code: it restarts, rebuilds or releases what changed. Apps start at Mac login when that is turned on.

Why it exists

Its author runs some forty local projects on one Mac. Remembering which port belongs to which project, where each one's docs are and which tests just failed is work nobody should do by hand.

local-apps lived in its author's utilities repository until 2026-11-14 and moved to its own repository, Lochost, with its history.

What it does not do

  • Serve anything to the internet: every address it gives is on the Mac itself.
  • Host other people's apps or offer accounts: it serves one person's projects on one Mac.
  • Replace a project's own production hosting: a local app is the dev version of its prod.

Where the data stays

Everything local-apps serves stays on the Mac: the apps, their docs and their test runs. The pages it writes are served by Caddy at *.localhost addresses only. What this public page itself collects is in its privacy policy.

Questions

Can I install Lochost?

Not today. It is built around one person's projects, folders and tools, and it is not packaged for anyone else.

Why .localhost and not a port?

Browsers resolve every *.localhost name to the Mac itself, so each project gets a name that stays the same, with no change to /etc/hosts. Caddy sends each name to that project's server.

What is the Admin Banner?

The strip Caddy adds to the top of every page of a local app. It names the app and links its Bug and Feature reports, Notion, Docs, Tests and admin panel.

What does reload do after an agent turn?

It compares each running app with its newest code and restarts, rebuilds or releases the ones that changed, so a page in the browser shows the work an agent just finished.

Contact

Questions about the tool or how it is built go to its author. Email Max Onyx at me@maxim.run or call +1 778 984 0698.