SLOCK
Learn · Local & private AI

Helmsman — frontier openmodels, under your control

Helmsman is S◉LOCK’s path for installing and controlling frontier-class open models on Lab hardware — curated plugins, smaller pilot intelligence, honest latency.

Updated 2026-08-12Learn · S◉LOCK guides
On this page
  1. The problem Helmsman solves
  2. Catalog plugins
  3. Pilot + deep model
  4. Honesty on speed
  5. Who it is for

The problem Helmsman solves

Frontier-class open libraries are huge. Dumping terabytes of weights on disk is not a product. Users need catalogs, install paths, hardware floors, and a control plane so a smaller on-box intelligence can drive deep jobs.

Catalog plugins

Models install as plugins with purpose docs, licence notes, and profiles (Home vs Lab). Example CLI: the SILOCK model catalog CLI.

Pilot + deep model

A capable small model (or agent) plans and steers; deep sparse models execute hard steps under budgets. That is how you use Lab hardware without fantasy always-on chat.

Honesty on speed

Multi-trillion-parameter class local runs can take substantial wall time. Helmsman optimises control and residency — not fake cloud-chat marketing.

Who it is for

Pro / Lab and Enterprise hardware owners. Home seats get everyday catalog models; frontier plugins switch on when the machine qualifies.

Next step: Open the full Helmsman model catalog, confirm Lab-class hardware floors, or request Founding Preview access.

FAQ

Is Helmsman a cloud service?
No. It is the local control path for frontier open models on capable machines you own.
Are weights included in the OS image?
No. Large libraries download or link onto your disk when enabled.

Related guides

Frontier-class models, operated from your own chair

Helmsman ships inside the Founding Preview: limited early access, EU-born, local-first, and no quiet rerouting of your prompts to a cloud.

Request Founding access