Cloud API + local LLMs together · Chefe 2677 · 23 Aug 2026
For ParviDefenders (commercial), hybrid is allowed. The customer can plug in cloud APIs (Claude, Grok, others) and local models on their machine, and the agents may use both in the same job. Not “pick only one.” They still need at least one brain or the windows stay empty. ParviRange (military) is unchanged: usually local only, air-gap, unless their rules allow a cloud API.
House still uses our LLM-Hub. Defenders: their mix. Range: still local-first.
| Product | Brains they may plug in |
|---|---|
| Our house | Our LLM-Hub (several AIs) — unchanged |
| ParviDefenders | Cloud API, local LLMs, or hybrid mix |
| ParviRange | Usually local (air-gap). Cloud only if their rules allow. Not hybrid unless you say so later. |
2668 said Defenders pick API or local. That exclusive “or” was too tight. You corrected it: mix is OK. I did not change Range. I did not turn on the install lock (option b) — still waiting.
Nothing to invent on hybrid — it is the rule now. Still you, if you want it: should Defenders/Range refuse AI waves until they have named at least one brain (and Defenders may add more, including mix)? Empty windows can still open for a human.