Reliability, security and privacy are structural properties of Sabas OS, not features bolted on after the fact.
Every layer of Sabas OS is designed with a clear failure boundary so that one component going wrong never takes the whole session down.
Security in Sabas OS is structural, not bolted on. Every process boundary is a capability boundary, and every workspace is a namespace boundary.
No telemetry calls, no usage analytics, and no cloud dependencies in the core OS. Every feature that touches a network is opt-in and clearly labelled.
No usage data, crash reports, or analytics are sent anywhere. The OS makes no outbound network connections on its own. There is no opt-out — there is nothing to opt out of.
The AI subsystem runs inference locally through Ollama. Model weights live on your machine. No query, file content, or context window is sent to a remote server unless you explicitly configure a cloud endpoint.
Each workspace is a separate namespace boundary. Apps in one workspace cannot read files, inspect processes, or observe network traffic from another — enforced by the kernel, not by policy.
Every action taken by the AI agent is written to a tamper-evident audit log stored locally. You can inspect exactly what the agent read, wrote, or executed — at any time, without a network connection.
The MCP security gate automatically redacts personally identifiable information before any data crosses a process boundary — even when talking to a locally-running model.
Every line of code that runs on your machine is publicly available. There are no binary blobs, no closed-source components in the OS itself, and no obfuscated network calls.