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: silock models list / install / enable / status.

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 metal 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 unlock when the machine qualifies.

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