Digital sovereignty

Digital sovereignty is not declared in a press release, it is observed in the invoices: who hosts, who encrypts, who holds the key, who can pull the plug. This category starts from the premise that a country outsourcing its data, its models and its payments to foreign jurisdictions has already answered the question, even while it pretends to still be asking it. You will find the subject approached from below rather than from the conference panel: local AI and what it actually costs, self-hosting once the forge turns agentic, the zero-knowledge cryptography the administration wants no part of, and the quiet dispossession of things we believe we own, from a media server we no longer control to a savings plan that buys America without ever holding it. With the industrial question running underneath: while France sells its stakes and regulates its own decline, others are building the machines. Written by a practitioner who deploys this infrastructure for clients, in the conviction that sovereignty is a technical and industrial bottleneck long before it is a talking point.

Origin: When the Forge Goes Agentic, Self-Hosting Stops Being a Hobby

Artificial Intelligence

On June 16, at its Compile conference, Cursor unveiled Origin, a Git forge designed no longer for humans but for the swarms of agents that push code around the clock. The press saw a GitHub competitor; the real story is the concentration that closes in when a single player brings together the compute, the model, the IDE, the forge, and your working data, a structural risk that would be identical with any other giant. Faced with this single point of control, self-hosting stops being a power user’s affectation and becomes a strategic position, provided you admit one thing: it will no longer be enough to store your repositories, you will have to run your own agent orchestrators or be sovereign but cripplingly slow. The real exit brick, then, is not just Git for the code, it is MCP for the agent, the pairing that lets an open editor restore the same power without handing everything to the dominant owner. My bet for the next three years: not a tipping point but a polarization, in which standardization remains our best way out.

Musk isn’t buying code. He’s buying the right to decide what’s true.

Artificial Intelligence

On June 12, SpaceX pulled off the largest IPO in history. Four days later it bought Cursor for $60 billion, then unveiled Origin, a Git forge built for agents. The press boiled it down to the purchase of an IDE and missed the point: one man is buying, layer by layer, the right to decide what counts as true, first in code, soon in knowledge itself. The real bottleneck is no longer producing code, it’s arbitrating what deserves to be merged, and for training agents that validation layer is worth more than all of GitHub’s public corpus combined. Yet there’s a crack in the narrative of inevitability: the keystone, Anthropic, is the one piece Musk cannot buy, even as he already supplies part of its oxygen. The real question is no longer to understand his plan, but to decide how much longer we keep renting him the future.

Qobuz : French audio pride and the mirage of digital ownership

Digital sovereignty

Qobuz has just announced 45.7% growth and a move into the black, a fitting vindication for a French company that bet on uncompromising quality rather than ad-funded free tiers. As a loyal user of its purchase-and-download service alone, I see in it both an aesthetic pleasure and an act of sovereignty. Yet thirteen years after paying for it, the very “Hotel California” that introduced me to the platform is now denied to me for re-download, its rights revoked by the label, its invoice vanished along with it. This mishap raises the real question, that of a “purchase” that is in truth only a revocable access license, and it reminds us that a digital good slips from our grasp the moment an intermediary holds it in our place. The only ownership that counts is the kind you bring home and hold physically in your own hands.

Apple AFM 3: The Triumph of On-Device AI… and What It Gave Up

Artificial Intelligence

On June 8, 2026, Apple unveiled the third generation of its Foundation Models, with one of the most ingenious on-device architectures on the market: AFM 3 Core Advanced stores twenty billion parameters in flash memory and activates only a few of them, routing its experts by prompt rather than by token. Yet the feat is nothing spontaneous, since it is the industrial extension of the 2023 paper “LLM in a flash” that Apple’s marketing would rather leave unmentioned. But behind the on-device brilliance sits a heavier surrender: all five models are co-designed with Google, pre-trained on its TPUs, and the most capable of them runs on NVIDIA GPUs in Google Cloud. The company that had made vertical integration and “designed by Apple” its creed now rents its cutting-edge horsepower from a competitor, precisely where it had promised the most independence. And all the while, the Digital Markets Act keeps Siri AI off Europeans’ iPhones and iPads with no timeline, a fitting illustration of a continent that excels at regulating a match it no longer plays.

The Swap : How your PEA buys America without ever owning it

Digital sovereignty

The PEA was created to finance European companies, and yet millions of French savers use it to bet on the S&P 500. The key to this paradox lies in a little-known contract, the swap, which lets a fund hold European shares while paying the saver American performance. Far from a makeshift, this arrangement exploits an American tax quirk that often lets it beat physical ownership, but it rests on three dependencies you do not control: a bank, a foreign tax authority, and a regulatory framework. The replication is excellent and the returns are there, but you do not own America: you are leasing its performance. And that distinction, painless as long as all goes well, takes on its full meaning the day something seizes up.

Putting an AI chatbot on a client site : the decision framework nobody bothers to drawt

Artificial Intelligence

Clients ask me to bolt an AI chatbot onto their sites all the time, and those sites run on everything: Shopify, WordPress, Drupal, sometimes abandoned custom builds. But “which plugin?” is never the right question: an AI chatbot is two layers people almost always conflate, the widget delivery and the brain that answers. The entire decision sorts onto a single scale, from locked-in turnkey where you control nothing, all the way to a pipeline you fully own. For a single client, turnkey is plenty; for an agency banking reusable knowledge across a whole fleet, owning the brain becomes an asset. Here’s the framework I use to decide, CMS by CMS, with Shopify leading the way.

Plex, or the Methodical Betrayal of a Community

Digital sovereignty

On May 19, 2026, Plex announces by email that its Lifetime Pass will jump from $249.99 to $749.99 on July 1, justifying the tripling with the software’s “real, ongoing value.” It’s the logical culmination of a drift that began on April 29, 2025, the day remote access, free since 2009, moved behind a monthly paywall. Between the “New Plex Experience” forced through despite the negative feedback, the advertising pushed right into your own library, and an openly claimed pivot toward AVOD streaming, Plex has methodically converted sixteen years of community trust into a monetization lever. Since early 2025, I’ve been running Jellyfin (remote access via Cloudflare Tunnel, iOS audio on Manet, video on Infuse) without a shred of regret. At $750 a promise, it was time to put technical sovereignty back where it should have stayed: at home.

DuckDB : your RAG fits in a file, not a cluster

Artificial Intelligence

A RAG PoC indexing 84,000 chunks, roughly 500 MB of vectors, fits without flinching in the RAM of an M1 MacBook; and yet French SMEs are still being sold a four-service stack (Pinecone + Elasticsearch + Postgres + LangChain) that costs between €150 and €400 a month in cloud infrastructure and mobilizes three distinct technical skill sets. DuckDB, the embedded analytical library maintained since 2019 by Amsterdam’s CWI, solves the equation with a single dependency: native vector search (the vss extension), BM25 full-text search (the fts extension), standard structured SQL filters, and hybrid re-ranking in one eight-line query, all of it inside a local .duckdb file. The bottom line: a factor of 10 on infrastructure cost, a factor of 10 on latency, a factor of 5 on time to production, and not a single embedding leaving your infrastructure to end up in an American datacenter. The four-service stack taught today in 90% of RAG tutorials doesn’t exist to solve a technical problem: it exists to sell recurring SaaS, to justify DevOps engagements, and to inflate project budgets on use cases that don’t warrant it. The real value of a senior engineer in 2026 is measured by the number of lines of infrastructure he knows how to remove to solve the exact same problem, not by the number of Kubernetes microservices he knows how to stack.