I often get asked: “If our data is hosted in Montréal, are we sovereign?”

It's a great question. And the answer is less simple than it seems.

A server located in Canada can belong to a company that answers to the laws of another country. The data is here, but who can actually access it? And who can decide, tomorrow morning, to change the rules of the game?

With artificial intelligence, these questions multiply. Every question asked of a model, every document entrusted to it, every trace it leaves behind is one more flow. Do you know where they go?

Renting, buying a condo or building your own house

Choosing your AI architecture is a bit like choosing where to live.

You can rent an apartment, turnkey. It's fast, inexpensive up front, and someone else takes care of the plumbing. But the landlord sets the rent, the rules and the length of the lease. That's what you do when you use a major vendor's AI directly.

You can buy a condo. You have more control, you're at home, but you live with the rules of the condo board and the decisions of the building. That's the equivalent of a dedicated environment or a sovereign cloud.

You can build your own house on your own land. You decide everything, but it takes capital, time and skills to maintain. That's infrastructure you host and run yourself.

None of these options is better in itself. Many organizations actually live in several at once without knowing it. The real risk is not choosing the wrong option; it's choosing without having seen the full menu.

What does being sovereign actually mean?

To me, it means being able to make your own technology choices and enforce them. Being able to examine, modify, move or replace your tools without a third party imposing its decision on you.

It is not absolute. Sovereignty comes in degrees, and the right degree depends on what you are protecting.

Nor is it the same thing as security. A tenant in a well-guarded building can be better protected than an owner who forgets to lock the door.

Five dimensions, five questions

An organization can be sovereign on one aspect and entirely dependent on another. In the guide, we distinguish five:

  • Data: who controls what you entrust to the system, and what it keeps in memory?
  • The model: if your vendor changed its behaviour or its prices tomorrow, what could you do?
  • Infrastructure: where does processing really run, and under whose authority?
  • The application layer: do your rules and guardrails belong to you, or do they disappear with the model?
  • Operations: could you maintain, fix or replace the system without asking anyone's permission?

Taken one by one, these questions often reveal surprises. A model you thought you controlled may run on infrastructure you don't. Documents carefully kept in-house may travel with every request.

Public or private: not the same stakes

A public body answers first to the trust of its citizens. A private company is more concerned with protecting its know-how, its customers and its ability to innovate.

What should be sovereign is therefore not the same for a municipality, a ministry, a manufacturing SME or a professional firm. And that is precisely where the decisions get interesting.

A trajectory, not a leap

Few organizations go from tenant to owner overnight. Most move forward in stages, at the pace of their needs and capabilities.

One simple question often shows where you stand: if your vendor doubled its prices tomorrow, how long would it take you to move out?

To go further

These choices are not primarily technical. They involve the budget, the risks and the ability of the whole organization to innovate.

The Brigade IA Sovereign AI Architectures guide, a workstream I lead, explores each of these dimensions in depth: the options, the trade-offs and the most common pitfalls. It is being finalized and will be free.

And if you would rather explore these questions from your own reality, that is also what I do with the leaders I support in my AI coaching program.

Ready to validate your next project?

Let's discuss your challenges. A 30-minute consultation to assess how independent technical validation can secure your project.

Would you rather pick a time yourself? Book a consultation.

Your information is used to answer your request. To learn more, see our privacy policy.

This site is protected by reCAPTCHA. Google's privacy policy and terms of service apply.