osFoundry / Platform
Private workspace
No telemetry, no cloud upload, no third-party LLM calls. BYOK only.
What it is
A private workspace in osFoundry means the application does not collect telemetry, does not upload your data to the cloud, and makes no third-party LLM calls on its own. osFoundry is a desktop app that runs on your machine. Your chats, documents, code, and knowledge are stored locally by default, so the baseline state of the product is one where nothing leaves your device unless you deliberately send it somewhere.
The one path data takes off your machine is a model call you configure yourself. osFoundry is bring-your-own-key (BYOK): you supply your own API keys for the model providers you want to use, and only then does the app talk to them, going straight to the provider with no osFoundry reseller or proxy in the middle and no markup. Those keys are held in your operating system's native secret store (Keychain on macOS, Credential Manager on Windows, the secret service on Linux) rather than on any osFoundry server. If you would rather keep everything on-device, you can point the workspace at a local or self-hosted model and run privacy-sensitive work with no outbound network calls at all.
This matters because most AI tools assume the opposite: they route your prompts through a vendor's backend, log usage, and hold your data on their servers. osFoundry inverts that default. The same workspace holds your chat and agents, apps, code, knowledge, and data, so keeping work private does not mean giving up capability or scattering it across separate privacy-focused tools. You decide, per key and per model, what is allowed to leave your device.
Key capabilities
- No telemetry and no usage analytics: the app does not phone home, and your prompts, files, and activity are never collected or sent to osFoundry
- No cloud upload by default: your chats, documents, code, and knowledge live locally on your device rather than on a vendor's servers
- No third-party LLM calls unless you make them: nothing is routed to any model provider until you configure a key and choose to send it
- BYOK only, stored in your OS-native secret store (macOS Keychain, Windows Credential Manager, Linux secret service), never on our servers
- Run local, self-hosted, or cloud models from one workspace, so privacy-sensitive work can stay fully on-device with a local model
Use cases
- Privacy-conscious professional: keeps client documents and drafts entirely on-device by running a local model, with no telemetry and no cloud copy of the work
- Regulated-industry engineer: reviews and refactors proprietary code in a workspace that makes no third-party LLM calls except to the self-hosted endpoint they approve
- Security-minded team lead: adopts an AI workspace they can verify sends nothing home, storing provider keys in the OS secret store instead of a vendor account
Frequently asked questions
Does osFoundry send my prompts or files to its own servers?
No. osFoundry collects no telemetry and does not upload your workspace data. Your chats, files, code, and knowledge stay local on your device. The only data that leaves is a model request you configure with your own API key, which goes directly to that provider, not to osFoundry.
Can I use osFoundry without calling any cloud AI service at all?
Yes. Because the workspace can run local or self-hosted models, you can do AI work with no third-party LLM calls. Nothing is sent to a cloud model provider unless you add a key and choose to route requests there, so a fully on-device setup is possible.
Where are my API keys stored, and does osFoundry ever see them?
Your keys are stored in your operating system's native secret store: Keychain on macOS, Credential Manager on Windows, and the secret service on Linux. They are not kept on any osFoundry server. osFoundry is BYOK only, so calls go straight from your device to the provider using your own key, with no reseller markup.