Sovereign AI & Data Residency for Regulated Enterprises
Three weeks for regulated organisations deciding what can leave their boundary and what cannot — with the architecture, cost model and evidence to support the decision.
Join the waitlistWho should take this program?
You'll get the most from this if
- Architecture, data and risk stakeholders together
- A real residency or sovereignty requirement
This is not for
- Organisations without a genuine residency constraint
What you will build
- A workload map showing what can and cannot leave the boundary
- A reference architecture with a routing design
- A total cost of ownership comparison
What you learn, week by week
Week 1 — Map the constraint
- Separate legal requirement from institutional preference
- Classify workloads by sensitivity
- Identify what genuinely cannot leave
Week 2 — Architecture
- Design the local and frontier split
- Benchmark open-weight viability on your own tasks
- Size infrastructure realistically
Week 3 — Cost and evidence
- Build the total cost comparison
- Assemble evidence for your regulator
- Plan the migration honestly
How this program handles evaluation and governance
The honest version of sovereignty is the point of this course. Teams routinely over-claim what must stay inside the boundary, and under-estimate what self-hosting costs to operate. Both errors are expensive, and both are avoidable with a week of proper analysis.
Tools and stack you will use
Fees
Request pricing
Fees depend on cohort, format, and whether this runs for an individual or a team. We'll send the full breakdown.
Get fee detailsQuestions people ask
Will you tell us to self-host everything?
No. Most correct answers are mixed, and we will say so even when it is less impressive.
Can you work under our security requirements?
Yes. Exercises can run entirely inside your environment.