How osFoundry and Microsoft 365 Copilot differ for organisations in South Africa — model choice, pricing, data protection and sovereignty — and how dgm helps with adoption.

dgm is an independent integration partner for osFoundry — it is not affiliated with osFoundry’s maker (OS LLC) and has not yet completed an integration project for any client.

When South African organisations compare osFoundry and Microsoft 365 Copilot, they are usually choosing between two different kinds of product rather than two versions of the same thing. osFoundry is a model-agnostic AI orchestration platform built on a bring-your-own-key (BYOK) principle: usage-based pricing with no per-user fee, local-first and self-hostable operation, the option to pin your data region (US, EU or Japan) or to deploy it inside your own private cloud. Microsoft 365 Copilot is AI embedded in Microsoft 365 (Word, Excel, Teams, Outlook), priced per user and tied to the Microsoft ecosystem.

osFoundry and Microsoft 365 Copilot at a glance

DimensionosFoundryMicrosoft 365 Copilot
Model choiceModel-agnostic, bring your own key (any provider)its own stack or largely tied
Pricingusage-based, no per-user fee (published offer USD 399 one-time or USD 3,999 per month)mostly per-user or subscription (check the pricing page)
Scopechat, agents, apps, knowledge and automationAI inside the Microsoft 365 suite
Deploymentcloud, self-host (BYO Cloud) or local-firstmostly provider-hosted
Data residency (South Africa)pin US/EU/Japan, or self-host in af-south-1 / Azure SA North / GCP Johannesburg; no managed SA regiondepends on the provider’s regions (check)
Vendor lock-inlower — BYOK and self-host keep model and data portablehigher — tied to the provider’s stack

The real difference

Microsoft 365 Copilot is powerful inside Microsoft 365, but it is per-user and tied to that ecosystem and its models. osFoundry is model-agnostic and BYOK-based, works across your whole tool set rather than one suite, and can be self-hosted — useful if you want to choose the model or keep data outside Microsoft.

To be fair to Microsoft 365 Copilot: For organisations that live in Microsoft 365, Copilot’s deep, native integration with Office and Teams is hard to match and needs little change management.

The choice is less about which is better and more about which shape fits: one polished product that does its job well (Microsoft 365 Copilot) versus a model-agnostic layer you can extend, self-host and pay for by usage (osFoundry). Many teams in South Africa use both together. You can read more about osFoundry’s approach at osFoundry.

What about data protection and sovereignty?

A South African buyer should look closely here. osFoundry pins your data region to the US, the EU or Japan, supports local-first inference on your own device, and lets you self-host it in your own AWS, Azure or Google Cloud account (BYO Cloud). osFoundry has an EU managed region but no managed region inside South Africa. The honest difference from many markets is that South Africa does have in-country hyperscaler regions — AWS Africa (Cape Town) af-south-1, Microsoft Azure South Africa North in Johannesburg, Google Cloud africa-south1 in Johannesburg and Oracle Cloud Johannesburg — so keeping data on South African soil is achievable by self-hosting osFoundry in one of those regions or in a local data centre, or by running it local-first. Note that the US CLOUD Act can compel a US-owned provider to produce data it controls regardless of where that data physically sits, which is why some organisations prefer self-hosting or local-first for their most sensitive workloads.

Personal information you handle is governed by the Protection of Personal Information Act 4 of 2013 (POPIA), which has been fully in force since 1 July 2021, and is overseen by the Information Regulator (South Africa), which administers both POPIA and the Promotion of Access to Information Act (PAIA). POPIA uses the terms responsible party and operator for what GDPR calls a controller and processor. Cross-border transfers of personal information are permitted under section 72 on one of five grounds, including adequate protection in the recipient country, binding corporate rules or the data subject’s consent. A security compromise (data breach) must be reported to the Regulator and affected data subjects as soon as reasonably possible — POPIA sets no fixed 72-hour deadline. POPIA does not impose a general data-localisation requirement, and South Africa does not hold an EU adequacy decision.

With Microsoft 365 Copilot, data residency depends on the provider’s available regions and contractual terms — check those directly. If keeping data in South Africa is a binding requirement, self-hosting osFoundry and its local-first mode are practical routes.

Pricing and vendor lock-in

Prices depend on the package and on usage, so always check the provider’s official pricing page for current figures. osFoundry’s published commercial offer is a one-time fee of USD 399 or USD 3,999 per month, with usage billed on top and no per-user seat fee. The structural contrast is per-user versus usage-based: osFoundry’s usage model moves cost with usage rather than headcount, which can suit small teams sharing one workspace. On lock-in, BYOK and self-hosting keep your model choice and data portable, whereas a single-vendor product ties more of the stack to one provider.

Where dgm comes in

dgm is an independent integration partner that helps organisations in South Africa adopt the osFoundry platform — from identifying the first practical use case, to setting it up, to connecting AI to the systems you already run. dgm operates separately from osFoundry’s maker (OS LLC) and has not yet completed an integration project for any client, so everything above is a proposed service rather than a delivered outcome. If you would like to weigh up a practical first step, dgm would be glad to think it through with you. Arrange an introductory call with dgm.