The console comes with the ground.
The Farmhouse is the Loams console. It ships with every deployment, at that deployment's own private address, and with Loams Desktop. There is nothing to sign up for: run a deployment, open its console, and work from there.
Ostrium does not host a console for you. The console runs on your deployment or in Loams Desktop. The only hosted part of Loams is the free Loams Cloud try-out, which is invite-only.
Two doors into the same house.
With every deployment
Each Loams deployment serves its own console at https://<your-deployment>/ui/. It lives where the deployment lives: on your laptop, your homelab or your servers, reachable over your own tailnet.
In Loams Desktop
The same console in a window, on Linux, macOS and Windows. It runs a local engine for you and connects to any deployment you add by URL.
Three steps, all on your own machines.
1. Run a deployment
Start the 0.1.1 stack with Docker or Podman Compose, on your machine or a VM you own. The quickstart gets one running.
2. Put it on your tailnet
The engine never gets a public address. Follow Self-hosting over Tailscale to reach it from your own devices only.
3. Open the console
Browse to https://<your-deployment>/ui/, or add the deployment's URL in Loams Desktop. If it does not answer, see troubleshooting.
One console, the whole plot.
The Field
Studio: parallel coding agents, each working in its own plot (a git worktree), side by side in the console.
The Greenhouse
The Software Factory: the toolchain beside the agents, Forgejo, Zulip, Plane, GlitchTip and more, embedded in the console.
Data
Browse and query your collections, tables and graphs on the deployment you are connected to.
Settings
Users, tokens and the deployment’s own configuration, kept on the deployment.
Open the console on ground you own.
Install Loams Desktop, or run a deployment and browse to its /ui/ address. Either way, the console and your data stay with you.