osFoundry / Platform
Data residency
Pin your workspace to a region. Multiple regions supported with replication and failover.
What it is
Data residency in osFoundry lets you pin a workspace to a specific region so its stored data lives where your policy, contracts, or local law require. You choose the region when you set up the workspace, and osFoundry keeps that workspace's data anchored there instead of letting it drift to wherever a default happens to land. This is the control that answers the plain question auditors and customers ask: "where does our data actually sit?"
Inside osFoundry the setting works alongside the product's local-first design. Because osFoundry is a bring-your-own-key desktop workspace, a large amount of your working data can stay on your own device and never leave it, and model calls go directly to the provider whose key you supply rather than through a reseller. Region pinning governs the workspace-level data that does get stored on the platform side, so residency and the local-first posture reinforce each other rather than competing. For teams that need more than a single location, osFoundry supports multiple regions with replication between them, and failover so the workspace keeps working if a region becomes unavailable.
Practically, you set the region once and it becomes a durable property of the workspace under Settings, in the Settings & Security area. Replication keeps a copy in another region for resilience, and failover promotes that copy when needed, so continuity does not force you to abandon your residency choice. The goal is a workspace whose location is a deliberate decision you can point to, not an accident of infrastructure defaults.
Key capabilities
- Pin any workspace to a chosen region so its stored data stays in that location by policy, not by default
- Support for multiple regions with replication that keeps a resilient copy in a second location
- Automatic failover promotes the replica so the workspace stays available if a region goes down
- Region is a durable workspace setting under Settings & Security, chosen at setup and enforced thereafter
- Complements osFoundry's local-first, BYOK design: much of your data stays on-device and model calls go direct to your provider
Use cases
- Compliance lead: pins each customer workspace to the region named in that customer's contract so the residency answer is provable, not assumed
- Regulated-industry admin: keeps workspace data in-region to satisfy local data-protection law while still running BYOK models from external providers
- Platform operator: relies on cross-region replication and failover so a regional outage does not take a team's workspace offline
Frequently asked questions
Can I choose which region my workspace data lives in?
Yes. You pin a workspace to a region and osFoundry keeps that workspace's stored data anchored there. The region is set as a workspace property under Settings, so it stays fixed rather than defaulting to an arbitrary location.
What happens if my primary region goes down?
osFoundry supports replication to a second region and failover, so a resilient copy of the workspace can take over and keep the workspace available if the primary region becomes unavailable.
Does region pinning cover the AI models I use through my own API keys?
Region pinning governs where your workspace's stored data resides. osFoundry is bring-your-own-key, so model calls go directly to the provider you supply a key for, and much of your working data can stay local on your device by design. Residency and the local-first, BYOK model work together to limit where data goes.