For home lab & home networks
A home server is still a Linux estate, only smaller. Olivares AI runs as one artifact on that box. The kernel stays on the LAN. Nothing phones home by default.
Home networks already run agents: a coding session on the workstation, an MCP server on the NAS, a local model on Ollama. The kernel is the missing map — what those processes can read and write — without sending that map to anyone else.
Loopback is the default listen address. Seeded demo data exists for trying the console, not as production facts. Air-gap is real for the kernel’s own data; it is not a claim that Claude runs offline.
Related: Linux servers, small teams, honesty & limits.
No mandatory telemetry and no control-plane egress by default: the engine opens no vendor telemetry channel and makes no mandatory outbound call at boot. What crosses your perimeter is what you configure to cross it — hosted-model APIs you attach, SIEM or webhook sinks you wire, an embedding provider if you provision one, and the upgrade command when you run it. Hosted models still reach their provider. This is a product default, not a perimeter absolute.
No. It is the same open-core artifact the rest of the site describes, installed on a machine you operate. There is no consumer store listing and no “home edition”.
Olivares AI is open-core (AGPL-3.0) and self-hosted. Deploy it and see what your agents can reach.