Scoping sovereignty for a national broadcaster

Why did a simple lift fail?

The broadcaster needed to reach audiences online while keeping content and citizen data inside approved boundaries. Its legacy infrastructure could not scale to streaming demand. The sovereignty requirements also ruled out a plain lift into a public cloud region. The useful question was not which cloud, but which content may leave the country, and by which path.

How do you scope sovereignty?

• A cloud-first design with a written residency split per data category, checked against the data-protection rules that applied to the broadcaster.
• Streaming through BlessBit, with a private CDN footprint serving the content that had to stay in-country.
• A petabyte-scale media archive under lifecycle policies that move cold material to lower-cost storage.
• 24×7 managed operations and documented compliance controls around all of it.

The scope was drawn around the content path, not around the whole estate. That keeps the claim narrow enough to defend in an audit.

What did the broadcaster end up with?

A broadcaster that streams reliably to a national audience while keeping sensitive content in-country. It has a documented, audit-ready architecture and operating costs that are predictable and quoted in USD by contract. The case does not claim that every dataset is local, that any particular rule is satisfied for another public body, or any certificate beyond the ones TiCON holds.

Questions to take into your own public-sector buy:

• Which data categories must stay in-country, and who made that decision?
• Which content path is local, and which runs in a named cloud region?
• Who administers the archive, and how is each access logged?
• Which operations minutes are written into the contract?