Skip to content

root / tags / bedrock

#Bedrock

2 fiches

Economy & Market Auto-verified translation

Mistral AI wants to build 1 gigawatt of European compute by 2030 — and lock in customers now.

News article analyzed, published on **VentureBeat** on **August 11, 2026** by **Michael Nuñez**, based on an **exclusive interview with Timothée Lacroix**, co-founder and CTO of **Mistral AI**, conducted ahead of the announcement, ~2,000 words. Mistral is expanding its infrastructure offering in three parts: **Mistral Regional Endpoints** in general availability (pinning inference and its associated processing to Europe or the United States), a **Priority Tier** in public preview (committed service levels, custom quotas, availability SLA), and a **coalition of European enterprises** whose multi-year commitments are meant to fund **200 MW by the end of 2027** and **1 GW by the end of 2030**. The vehicle is called the **European Compute Unit (ECU)**: a claim on capacity built by Mistral, fungible across inference, training, model adaptation, or managed Kubernetes, over a targeted five-year horizon. Lacroix describes the mechanism bluntly — *"The whole point of compute units is to have commitment"* — and, on early exit: *"There is no getting out."* The article scales the ambition: Mistral states it operates *"less than 200 MW"* and details three sites totaling **77 MW** (44 MW near Paris, 23 MW in Sweden with EcoDataCenter, 10 MW in Les Ulis); **Epoch AI** puts the initial capex for a one-gigawatt AI datacenter at **~$38B**, and **Goldman Sachs Research** puts next-generation facilities at **$15-20M/MW excluding chips**, against the **~$4B** Mistral has raised in total (PitchBook). Added to this is a decision that *"is likely to raise a few eyebrows among sovereignty purists"*: Mistral is starting to **host third-party open models**, beginning with **GLM-5.2** from **Z.ai**, a Chinese lab — *"It's a great model. Everyone loves it. It's open-weight, so there was no good reason for us not to do it."* The article digs into the fine print of Mistral's documentation, which mentions *"limited, controlled transfers"* to subcontractors outside the region; pressed for detail, Lacroix points to **tool calls**, web search in particular, and states that **gating is the feature, not the bug**. The author's framing: *"full regional control is available, but the moment an AI agent reaches out to the open web, sovereignty becomes a configuration decision, not a default."* Two dependencies remain: **GPUs** come from Nvidia, and **Microsoft** — anchor tenant of Mistral's European datacenters since July — is presented as what de-risks the buildout.

#Mistral AI#digital sovereignty#AI sovereignty

**Michael Nuñez** — journaliste **VentureBeat** · couvre l'IA et l'infrastructure ; déjà présent au corpus. L'article est bâti sur un **entretien exclusif avec Timothée Lacroix** · cofondateur et CTO de Mistral AI · conduit **avant l'annonce** · et fait suite à un entretien de juin avec le même interlocuteur. Publié le **11 août 2026**.

AI Coding Agents & Skills Machine translation

graphify — « Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store. »

Skill entry: **graphify** by **Safi Shamsi** (Graphify Labs, Y Combinator S26) turns an entire project — code, docs, PDFs, images, videos — into a **queryable knowledge graph**, invoked via `/graphify` from Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, and about fifteen other clients. Observed on **August 6, 2026**: **103,187 stars**, **10,024 forks**, repository created on **April 3, 2026**. Apache-2.0, Python 3.10+, default branch **v8**. **Three design choices**, stated in the README. *"Code maps for free, fully local"*: code is parsed into a **tree-sitter AST**, deterministically and without an LLM, nothing leaving the machine. *"Every edge is explained"*: each edge is labeled **`EXTRACTED`** (explicit in the source) or **`INFERRED`** (resolved by graphify), with a third value `AMBIGUOUS` appearing in the report. *"Not a vector index"*: *"no embeddings, no vector store: a real graph you traverse"*. **Three outputs**: `graph.html` (interactive graph), `GRAPH_REPORT.md` (god nodes, surprising connections, suggested questions), and `graph.json` (persistent graph, queryable weeks later without rereading the files). **Three query modes** replacing grep: `query` (subgraph for a natural-language question), `path A B` (shortest path between two entities), and `explain` (neighborhood of a concept). **Coverage**: 36 tree-sitter grammars (~40 languages), plus Terraform, Apex, MCP configurations, package manifests, Office, Google Workspace, PDFs, images, and video/audio transcribed locally by faster-whisper. Communities detected via **Leiden**, labeled without an LLM. **Benchmarks**: on LOCOMO, recall@10 of **0.497** versus 0.149 for supermemory and 0.048 for mem0, but lower QA accuracy (45.3% versus 49.7%); on LongMemEval-S, **76%**, on par with a dense RAG; and *"Graph build — LLM credits: 0"*. **Points to record**: the `main` branch carries a v1-era README describing a different product (Claude Code-only skill, the "71.5× fewer tokens" claim); the PyPI package is named **`graphifyy`** with two *y*s, while the `graphify` name is being reclaimed; and a **query log** is written by default to `~/.cache/graphify-queries.log`, which can be disabled via an environment variable.

#skill#knowledge graph#knowledge graph

**Safi Shamsi** — créateur et mainteneur de graphify · et de **Graphify Labs** · société passée par **Y Combinator (promotion S26)** selon le badge du dépôt. Il maintient aussi le site d'annuaire `graphify.net` (cf. [[graphify-net-annuaire-ia-coding-2026-08-06]]) et publie un livre · *The Memory Layer* · sur les idées et l'architecture derrière le projet.