EU Tech Stack

The seed

A modern application is a tower of dependencies — hosting, storage, identity, payments, analytics, the libraries underneath all of it. Most of those layers default to providers governed by non-EU law, which means the data and the operation can be reached by jurisdictions outside the one you answer to. The risk is rarely visible until it matters, and by then the stack is too entangled to swap.

The EU Tech Stack is the deliberate alternative: a complete, layer-by-layer mapping of European technology that can fill each role, curated for fit and quality, and built out where gaps remain. The goal is a stack where every dependency sits under EU jurisdiction — not as a compromise, but as a coherent whole.

Why it matters

Sovereignty fails at its weakest dependency. One layer governed by foreign law can expose an entire system, however careful the rest. Treating the stack as a single object to be mapped and curated — rather than assembled ad hoc from whatever is convenient — is what makes jurisdictional independence achievable instead of aspirational.

• Mapped — every layer of the stack and the European options that fill it.
• Curated — chosen for quality and fit, not just for the EU label.
• Built — where no adequate option exists, the gap becomes a thing to make.

What building it out looks like

• Enumerate the layers a real project needs — from infrastructure to libraries — as the map’s skeleton.
• Survey and curate the European options for each layer, noting maturity and jurisdictional standing.
• Flag the gaps — layers with no adequate EU option — as candidates to build (this is where quests like the Netlify alternative come from).
• Assemble a reference stack and run an EvoBioSys project on it end to end.

Status

Growing. The principle — no non-EU jurisdictional risk anywhere in the stack — is settled, and the active work is the mapping and curation that turns it into a usable reference. Gaps surfaced here feed the build-it-yourself quests around them.