The digital transformation of local government is back on track. For two years, municipalities, inter-municipal bodies, metropolitan areas and public institutions have watched large private-sector groups rack up considerable productivity gains thanks to generative AI. The question is no longer whether the public sector will get on board — that is inevitable. The question is how, and with what guarantees.
Because for a local authority, deploying Claude, ChatGPT or Copilot as-is is not an option. Three structural constraints forbid it. And it is precisely by starting from those constraints — not by working around them — that you build AI that genuinely serves the public.
Why the public sector has a specific AI problem
A private-sector SME that adopts ChatGPT to save time takes a measured risk on the confidentiality of a few internal documents. A local authority that does the same exposes administrative data, citizens' files, and public contracts in progress. The risk is not of the same order. And the responsibility — political, legal, reputational — does not rest on the same shoulders.
Three constraints structure the public sector's AI question, and each one eliminates a portion of the solutions on the market.
Constraint 1 — Data sovereignty
French public data cannot casually transit through American servers. The CLOUD Act theoretically allows the US government to access any data stored by an American company, wherever it physically sits. For a municipality managing a land registry, civil status records or local litigation, that exposure is politically and legally unacceptable.
Concretely, this means that using GPT-5 via the OpenAI API, Claude via Anthropic or Gemini via Google is not compliant with the requirements of a serious local authority — even if the terms of service mention a training opt-out. The opt-out covers model training, not potential access by a foreign authority.
Constraint 2 — GDPR, in its reinforced version
GDPR applies to every European organization. But public bodies are subject to reinforced obligations: a systematic data protection impact assessment (DPIA) for any automated processing of personal data, mandatory appointment of a DPO, and full traceability of automated decisions affecting citizens.
A generative AI that drafts a reply letter to a citizen, pre-processes a grant application or triages a social-services file must be auditable. Every output must be explainable, and a human must validate any decision with individual impact (Article 22 of the GDPR). A system that fails to respect this chain of traceability exposes the authority to litigation and to CNIL sanctions.
Constraint 3 — The French Public Procurement Code
Buying an AI solution for a local authority is not signing a standard SaaS contract. Above a threshold of €40,000 excl. VAT, you must go through a public tender with its publication procedure, its timelines, its specifications, and its objective award criteria. And even below that threshold, the fundamental principles of public procurement apply: transparency, equal treatment, competitive bidding.
That closes the door on many solutions on the market: a simple individual subscription to an AI service, paid by credit card, is not a valid purchasing method for a public service. And a vendor that cannot respond to a DCE (Dossier de Consultation des Entreprises — the official tender documentation) is de facto disqualified.
A viable stack: 100% French, compliant, high-performing
The good news is that these three constraints are not a wall. They define a perimeter — a narrow one — within which technically excellent solutions do exist. We have proven this on several projects, including our collaboration with Experts Publics.
The model: Mistral AI
Mistral AI, a French company based in Paris, offers models that are competitive with those of OpenAI or Anthropic on most local-government use cases: drafting, summarization, document analysis, classification, structured generation. The models can be deployed in managed mode with Mistral, self-hosted on Scaleway, or in hybrid mode. And the data never leaves European territory.
For more reasoning-intensive use cases, open-weight models such as Mixtral or DeepSeek can be deployed on sovereign infrastructure — at the cost of a heavier setup but with total independence.
The infrastructure: Scaleway or OVH Cloud
Scaleway (Iliad group) and OVH Cloud are the two French players offering sovereign cloud services, certified SecNumCloud for sensitive workloads. The servers are physically in France, the operator is French, the jurisdiction is French. Zero exposure to the CLOUD Act.
For less sensitive workloads, the European zones of the hyperscalers (AWS Frankfurt, Azure France Central) remain a transitional option — but they do not resolve the underlying legal question.
The architecture: RAG over a domain-specific document base
A local authority does not need a generalist model that knows everything about everything. It needs an agent that masters its domain: the French Public Procurement Code, the General Code of Territorial Authorities, administrative case law, past deliberations, contracts in progress.
RAG (Retrieval-Augmented Generation) architecture answers exactly that need. Instead of trusting what the model learned in pre-training, you force it to draw its answers from a closed document base whose content the authority fully controls. Sources are cited explicitly. The traceability required by GDPR is automatically satisfied.
The Experts Publics case
We built Experts Publics on this architecture. The platform connects specialized public-sector freelancers (project managers, legal experts, project-owner-assistance consultants, public procurement specialists) with local authorities that have one-off needs — without going through the heavy structures of temp agencies or large consulting firms.
Three technical components, all sovereign:
- A complete webapp (freelancer registration, mission posting by local authorities, matching, admin moderation area) hosted on Scaleway.
- An AI agent trained on the French Public Procurement Code, powered by Mistral, which assists freelancers in drafting their tender responses and helps authorities qualify their needs.
- A GDPR-by-design architecture: no personal citizen data ever passes through the AI, full traceability of actions, and the right to erasure implemented natively.
The collaboration continues with the progressive integration of new building blocks: native messaging, automated legal monitoring, new domain-specific agents (drafting technical proposals, analyzing tender documentation, summarizing meetings). At every step, the same rule: no compromise on sovereignty.
→ Watch the full Experts Publics demo on video (YouTube)
Where to start, concretely
A local authority that wants to equip itself with compliant, useful AI does not need to launch a €500,000 tender over three years. In fact, an overly ambitious project from day one is the main driver of failure — just as in the private sector, but with heavier political consequences.
The sensible sequence comes down to four steps:
- Map your priority use cases. Which 2-3 processes are costing you the most administrative time? Responding to citizen requests, processing files, drafting letters, preparing briefing notes for elected officials, monitoring contracts? Quantify the time lost — you will be surprised.
- Launch a structuring AI audit, over 4 to 8 weeks depending on the size of the organization. It is a modest investment (€2,000 to €10,000 excl. VAT) that produces a defensible deliverable: a map of the frictions, identification of AI-ready use cases, and costed scenarios.
- Test one isolated use case before industrializing. Not the entire scope — one case with a measurable before/after and a controlled risk. An agent that pre-drafts responses to citizen requests, for example.
- Industrialize in waves. Like a large company, but at your scale. Start with the staff who are most comfortable technically, formalize the practices, then extend progressively.
This sequence respects three structural constraints of the public sector: it fits within a local authority's budgetary framework, it stays within common public procurement thresholds, and it does not place a disproportionate political risk on an experimental project.
The cost of doing nothing
The standard counter-argument to any caution is this: if you wait, you lose. That is particularly true in the public sector, where citizens now hold digital-experience standards forged by their use of private services. When a citizen gets an answer from Amazon within two hours on a complex problem, they cannot understand why their town hall takes three weeks to process a request for an administrative document.
The pressure comes both from above (the State, which imposes ever more demanding digitalization standards) and from below (citizens, who unconsciously compare their town hall to their online bank or their energy provider). The authorities that equip themselves now — with discernment, respecting the three constraints described above — build a lead that will be hard to catch up.
Those that wait will pay three times over: in attractiveness (the best public servants go where the tooling exists), in productivity (each employee processes fewer files), and in citizen trust (the gap with private-sector user experience keeps widening).
Conclusion
AI for local government is not a topic for geeks. It is a matter of sovereignty, of law, and of the service delivered to citizens. The right solutions exist — French, compliant, high-performing. The question is no longer technological. It is political and organizational.
If you lead a local authority, an inter-municipal body or a public institution and want to take this reflection seriously, we would be delighted to talk. Our AI Audit is calibrated precisely to structure these first steps — in 4 weeks, with a defensible deliverable and a costed roadmap.
Do you lead a local authority or a public institution?
Book 30 minutes to frame your AI approach — free, no commitment.