The difference between a single AI orchestration platform and a set of separate tools, and what it means for cost and governance for South African organisations.

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.

Many organisations accumulate separate AI tools: a chat assistant here, an automation there, a separate search tool. An orchestration platform brings these together — and that has implications for cost, governance and data control.

Separate tools or one platform?

  • Governance — separate tools mean separate accounts, keys and invoices; a platform centralises this.
  • Cost — multiple per-user subscriptions add up; a usage-based platform charges by usage.
  • Data — keeping data spread across many tools inside South Africa is harder than from a single self-hosted environment.
  • Consistency — agents and apps that share your knowledge work better inside one platform.

An orchestration platform such as osFoundry combines chat, agents, internal apps and knowledge — it is model-agnostic and self-hostable.

What about data protection and sovereignty?

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.

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.