Open source geospatial tools are good. I have been making some form of that argument for most of my career, especially on this blog. The mature projects are equal to or better than their proprietary alternatives. The communities that build and maintain them represent some of the best technical talent working in this space. None of that has been enough to reliably move the adoption conversations that matter.
In the last few weeks, a word has bubbled up and caught my attention. That word, “sovereignty,” started showing up in conference themes, online publications, and strategy discussions. At first glance, it’s a different argument than the one the open source community has been making for years. Because I’m in the middle of organizing two conferences on open source geospatial, my mind immediately began thinking about how sovereignty and open source intersect.
Sovereignty seems to represent a shift in how people are thinking about technology dependency. The shift hasn’t been specifically about open source, but open source is better positioned to answer it than anything else.
Sovereignty Spike
It’s been a little over a year since we released GeoFeeds and it now aggregates 119 feeds and over 1,200 individual posts covering most segments of the geospatial market. A couple of months ago, I began generating a daily briefing based on the posts over the previous 24 hours. I started putting those briefings online a few weeks ago. That was when I first noticed the uptick in talk about sovereignty. When I searched the corpus for “sovereignty” and “sovereign” across the last year, the results were striking. Before September 2025, the terms barely registered. One result, a passing mention in a Canadian conference announcement. Since then, twenty-one results across five sources, with most of the volume concentrated in the last six weeks.
The geographic concentration isn’t subtle. GoGeomatics has been running a sustained series on Canadian data sovereignty, covering everything from cloud residency requirements to GPS dependency risk (GoGeomatics, 2026a, 2026b). GeoIgnite 2026, the Canadian national geospatial conference, framed its entire call for speakers around sovereignty, resilience, and security (GoGeomatics, 2026c). Other outlets and events have followed the same thread (Geospatial World, 2026; Cadell, 2026). The conversation has surfaced in Australia as well, where similar concerns about GNSS dependency and foreign infrastructure risk have been appearing in the trade press (Goward, 2026).
The trigger isn’t hard to identify. The current US administration has been transparent about its willingness to use political, military, and economic leverage as a cudgel. Canada’s Prime Minister Mark Carney responded by calling for the world’s middle powers to reduce their dependencies on relationships that could no longer be assumed stable (Carney, 2026). The same US administration is also among the dominant customers for most of the US geospatial industry (Geospatial World, 2024). For other governments, that calculation gets uncomfortable fast. If your critical geospatial infrastructure runs on software built by companies whose largest customer is a government that has openly signaled adversarial intent toward yours, sovereignty arguments don’t just make sense, they’re overdue.
The geographic spread matters as much as the volume. Canada and Australia aren’t adversaries recalibrating against US power. They’re among the closest allies the US has. When partners at that level start asking whether they own their critical geospatial infrastructure, the dependency question has moved somewhere new (Goward, 2026).
The dependency question doesn’t stop at national borders. US state and local governments face a version of the same math domestically. Much of the geospatial data infrastructure they depend on flows from federal programs whose priorities and budgets shift with each administration. A state emergency management office that has built its operations on federal data services and centrally controlled platforms is not in a structurally different position than a Canadian ministry asking whether it should depend on those same vendors or services.
The underlying concern about technology dependency isn’t new. It has surfaced in procurement debates, open data advocacy, and vendor lock-in discussions for years, but “sovereignty” changes the stakes. “Risk” makes you think about protecting the assets you use to do your work. “Sovereignty” makes you think about protecting the mission of the work itself. At its core, sovereignty is ownership. You care more about something you own than something you’re simply answerable for. Those aren’t the same concern, and they don’t produce the same response. That’s true whether the mission belongs to a government agency or a private organization.
Elevating the Conversation
The open source geospatial community has understood the risk perception problem for a while. In 2009, OpenGeo packaged a suite of open-source geospatial tools with a commercial support model specifically to address it. I wrote at the time that “the perception of risk equals the presence of risk” and that well-run organizations don’t make acquisition decisions on technical merit alone. While that view was correct, sovereignty is a different lever on the same problem, and it reaches further into the institutions that make the decisions that matter.
Practitioners have understood the open source case for decades. The problem is that practitioners rarely set strategy. The people who do have a different risk calculus. Choosing an established proprietary vendor meant a known support structure, a single vendor to theoretically hold accountable if something went wrong, and the career safety of a defensible decision.
The sovereignty argument doesn’t ask procurement officers to weigh technical merits. It moves the conversation above procurement entirely. The question isn’t what you’re exposed to. It’s what you own and what mission you exist to protect. That question belongs to leadership, not to contracting, and it clears bureaucratic hurdles that a risk argument cannot.
The conclusion is clear: understand your mission and own as many of its critical components as you can. Control your own data. Avoid handing the keys to a vendor you can’t replace. The open source ecosystem has been making that case on its merits for thirty years. The sovereignty lens makes it on mission and ownership grounds instead, and those arguments can travel through institutions in ways that technical merit and risk arguments simply don’t.
Bridging the Gap
The predictable counter-move is already underway. Large cloud vendors offer sovereign-branded, regional managed services built on proprietary foundations, but geography isn’t sovereignty. The dependency, and therefore the risk, doesn’t go away. It gets rebranded.
For most organizations, completely re-hosting away from foreign-owned infrastructure isn’t feasible in the near term, but that’s not the question. The question is how you architect your mission-critical systems within whatever infrastructure you’re running on. Open source and open standards give you control over that architecture today and a path to move it on your own terms tomorrow. Proprietary software, regardless of where it’s hosted, closes that path.
The sovereignty question makes visible something that was always true: open source is the only path that actually transfers control. Open source licenses don’t confer ownership of the software any more than proprietary ones do, but their nature means no vendor can change the terms or the economics after you’ve built dependency on them. The community doesn’t need to outspend the sovereign-cloud pitch. It has decades of credibility, a track record of production deployments at scale, and technical foundations that proprietary wrappers are quietly built on. That track record bolsters sovereignty arguments and should be highlighted as evidence that open source can meet mission requirements.
There’s a harder risk question on the open source side of the ledger. The sovereign alternative to a large proprietary vendor isn’t another large vendor. It’s a distributed ecosystem of consultancies, maintainers, and integrators, most of them small, none of them sized to absorb enterprise procurement at scale on their own. Technologists will correctly point out that this is fine, that organizations can and should build internal capacity, that a single point of accountability isn’t required. That’s true, but it’s also not an answer to the organizational risk question sitting across the table from a procurement officer who needs to explain the support model to a CIO.
The sustainability question and the sovereignty question are connected. Organizations that want sovereign geospatial capability have a direct interest in the health of the communities that build and maintain the infrastructure that makes sovereignty possible. The open source geospatial community doesn’t need to produce a Microsoft to be credible. It needs to produce a story about how the ecosystem as a whole provides what a single large vendor would provide alone. That story is harder to tell than it should be, but it’s not impossible.
Wrapping Up
I’ve watched the open source geospatial case get made for most of my professional life. It has been made well, by smart people with legitimate standing to make it, and it has moved the needle more slowly than the merits deserved.
The sovereignty discussion doesn’t change the merits, it can change the institutional receptivity. That is valuable. It’s exactly the opening the community has needed, and open source geospatial infrastructure is positioned perfectly to answer it.
References
Cadell, W. (2026, February 26). SovereignAI: Know thyself. Strategic Geospatial. https://www.strategicgeospatial.com/p/sovereignai-know-thyself
Geospatial World. (2024, June 19). $133 billion geospatial market and $1.09 trillion socio-economic benefits. https://geospatialworld.net/news/usd133-billion-geospatial-market/
Goward, D. A. (2026, February 20). Australian PNT: Lots of potential, lots of danger. Spatial Source. https://www.spatialsource.com.au/australian-pnt-lots-of-potential-lots-of-danger/
Carney, M. (2026, January 20). Principled and pragmatic: Canada’s path [Speech transcript]. Prime Minister of Canada. https://www.pm.gc.ca/en/news/speeches/2026/01/20/principled-and-pragmatic-canadas-path-prime-minister-carney-addresses
Geospatial World. (2026, March 3). Sovereign, secure, and resilient geospatial infrastructure for national security [Video]. GeoBuiz Summit 2026. https://geospatialworld.net/videos/sovereign-secure-geospatial-infrastructure-panel/
GoGeomatics. (2026a, March 3). Beyond residency: The 2026 push for true Canadian data sovereignty. GoGeomatics. https://gogeomatics.ca/beyond-residency-the-2026-push-for-true-canadian-data-sovereignty/
GoGeomatics. (2026b, March 3). Running on borrowed time: Why Canada’s GPS dependence is a $1 billion-a-day risk. GoGeomatics. https://gogeomatics.ca/running-on-borrowed-time-why-canadas-gps-dependence-is-a-1-billion-a-day-risk/
GoGeomatics. (2026c, February 12). Call for speakers: Sovereignty, resilience and Canada’s geospatial future. GoGeomatics. https://gogeomatics.ca/call-for-speakers-sovereignty-resilience-and-canadas-geospatial-future/
