evolve sovereign
your commerce stack, your rules
Choose, change or leave every layer of your stack: that’s digital autonomy. Host it at a European provider and only European law applies: that’s digital sovereignty. Evolve and your storefront stay the same.
- MIT-licensed core components
- self-hosted
- European provider
- no fork, no separate product
- commercecommercial or US-operated
- contentcommercial or US-operated
- searchcommercial or US-operated
- hostingUS law applies
every layer swappable: that’s digital autonomy
EU-hosted: that’s sovereignty
what it is
digital autonomy plus European jurisdiction
Digital autonomy means you can choose, change and leave your components. Digital sovereignty goes a step further: only European law applies to the infrastructure they run on. Evolve Sovereign gives you both, with the regular Evolve product.
01 · digital autonomy
open source you run yourself
Commerce, content and search run on Medusa, Payload and Meilisearch. You pick the versions, own the configuration and decide where each component runs.
02 · European jurisdiction
hosting at a European provider
Infrastructure of a European company under European jurisdiction. Your own software on a US cloud doesn’t meet this condition.
= digital sovereignty
every layer on record: component, licence and operator
Sovereignty Bill of Materials
first version · we keep it up to date per release
| layer | component | licence | what Sovereign leaves out | status |
|---|---|---|---|---|
| commerce engine | Medusa, self-hosted | licence: MIT (core) | what Sovereign leaves out: Enterprise Edition features: admin roles, single sign-on | available |
| content management | Payload, self-hosted, runs in-process | licence: MIT | what Sovereign leaves out: nothing | available |
| search | Meilisearch Community Edition, self-hosted | licence: MIT (CE) | what Sovereign leaves out: Enterprise Edition | available |
| hosting | Scaleway, Amsterdam region | licence: n/a | what Sovereign leaves out: n/a | early 2027 |
Evolve is vendor-agnostic: you can also combine open source components with commercial engines and services such as commercetools, layer by layer.
jurisdiction
an EU region is not EU jurisdiction
What counts is who operates the infrastructure. A US company running a data centre in the EU still falls under the US CLOUD Act, and so does open source you run on Azure or AWS.
any vendor, hosted by a US provider
- data stays in the EU
- depends on the vendor
- operator only under EU law
- no
- outside the reach of the US CLOUD Act
- no
- you can fork, migrate or move it
- no
Convenient, but under US law.
Whoever the vendor is, a US company runs the infrastructure, so the US CLOUD Act applies. Where the data sits depends on the vendor.
your stack on a US cloud
- data stays in the EU
- yes
- operator only under EU law
- no
- outside the reach of the US CLOUD Act
- no
- you can fork, migrate or move it
- depends on the services you use
Data in Europe, operator under US law.
Your data stays in an EU data centre, but the company that runs it still falls under the US CLOUD Act.
built for data residency
- data stays in the EU
- yes
- operator only under EU law
- no
- outside the reach of the US CLOUD Act
- no
- you can fork, migrate or move it
- depends on the services you use
Data in Europe, but still a US operator.
These offerings keep data in Europe, but they remain services of US companies under US law.
open source at an EU provider
- data stays in the EU
- yes
- operator only under EU law
- yes
- outside the reach of the US CLOUD Act
- yes
- you can fork, migrate or move it
- yes
Open source you run, under European law.
Every layer is software you run yourself, on infrastructure of a European company under European jurisdiction.
| compare setups | ||||
| data stays in the EU | depends on the vendor | yes | yes | yes |
| operator only under EU law | no | no | no | yes |
| outside the reach of the US CLOUD Act | no | no | no | yes |
| you can fork, migrate or move it | no | depends on the services you use | depends on the services you use | yes |
Convenient, but under US law.
Whoever the vendor is, a US company runs the infrastructure, so the US CLOUD Act applies. Where the data sits depends on the vendor.
Data in Europe, operator under US law.
Your data stays in an EU data centre, but the company that runs it still falls under the US CLOUD Act.
Data in Europe, but still a US operator.
These offerings keep data in Europe, but they remain services of US companies under US law.
Open source you run, under European law.
Every layer is software you run yourself, on infrastructure of a European company under European jurisdiction.
Some sovereign offerings run through partners operated in the EU: check which entity operates the service, and under which law. Evolve Sovereign meets the last two rows once you host at a European provider; Scaleway as a deployment target arrives early 2027. SaaS from a European vendor, hosted at a European provider, can meet the first three rows too.
two routes
you don’t have to move everything at once
The storefront talks to the Evolve GraphQL schema and doesn’t know which engine is behind it. Every layer you move to open source you run yourself adds digital autonomy. Once it runs at a European provider, it’s sovereign too.
route A
start on the Sovereign stack
A new initiative that has to run in the EU starts directly on Medusa, Payload and Meilisearch, from the Evolve reference implementation for this stack.
step 1 of 5
put Evolve on top of your current stack
Your storefront moves to Evolve and talks to its GraphQL schema. Nothing behind it changes yet.
step 2 of 5
move search to Meilisearch
The Community Edition, self-hosted. The storefront keeps calling the same schema.
step 3 of 5
move content to Payload
Payload runs in-process, inside your own deployment.
step 4 of 5
move commerce to Medusa
Catalogue, carts and orders on Medusa, self-hosted. Same schema, same storefront.
step 5 of 5
move hosting to a European provider
Deploy the whole stack at Scaleway in Amsterdam. This is the step from digital autonomy to digital sovereignty. This deployment target arrives early 2027.
- 1. put Evolve on top of your current stack
- 2. move search to Meilisearch
- 3. move content to Payload
- 4. move commerce to Medusa
- 5. move hosting to a European provider
The order is an example. Move the layers in whatever order suits you.
- commerceyour current enginecommercial or US-operated
- contentyour current CMScommercial or US-operated
- searchyour current searchcommercial or US-operated
- hostingyour current cloudcommercial or US-operated
- digital autonomy
- 0 of 3
- digital sovereignty
- not yet
in production
the same Evolve that runs in production today
Evolve Sovereign uses the schema, modules, storefront and licence model of every other Evolve stack. Scaleway becomes the fourth deployment target in early 2027.
- in production
Microsoft Azure
Frasers Group, Rensa Family, EDCO
- in production
Google Cloud
HBM Machines
- in production
Amazon Web Services
Zeeman, Knives and Tools
- early 2027
Scaleway
European provider, Amsterdam region. The first two projects on the full Sovereign stack are starting now.
closest to Sovereign today
Toppy.nl
- Magento
- Tweakwise
- Payload
- Google Cloud
Toppy put Evolve on top of the stack they run themselves: Magento and Payload, with Tweakwise for search. It’s hosted on Google Cloud, so it isn’t sovereign. But it shows digital autonomy in production: a stack they can change themselves, route B in practice.
These customers don’t run the Sovereign stack. They show that the platform holds up in production. Proof for the Sovereign stack itself follows: the first two projects on the full stack at Scaleway are starting now, and a demo environment arrives early 2027.
questions
Digital autonomy means you’re not locked in: you run open source yourself and can choose, change or leave each component. Digital sovereignty adds jurisdiction: the infrastructure is operated by a European company, under European law only. You can have autonomy on any cloud today; sovereignty needs hosting at a European provider, which Evolve supports from early 2027.
Medusa and Meilisearch each have an Enterprise Edition under a different licence. Evolve Sovereign doesn’t use those features, such as admin roles and single sign-on in Medusa. Roles and single sign-on run through your own identity provider instead.
Yes. Evolve is vendor-agnostic, so you can combine open source components with commercial engines and services such as commercetools, layer by layer. Only the layers on open source at a European provider count as sovereign.
Scaleway becomes the fourth deployment target in early 2027, together with a demo environment of the Sovereign stack. The first two projects on the full open source stack at Scaleway are starting now.
No. The components in the Bill of Materials are MIT-licensed. Evolve has its own licence, the same on every stack. See our plans for how it works.
Evolve’s own AI features run on EU inference, at Scaleway or a European model provider such as Mistral. The MCP server works with whichever assistant your customers choose, so whether their assistant is sovereign too is their own call.
let’s map your route
Two questions, and we know where to start the conversation.
route A looks like a fit
Start directly on Medusa, Payload and Meilisearch from the Evolve reference implementation, built for a public-sector organisation.
route B looks like a fit
Your storefront already talks to the Evolve schema. We map which layers to move first for a public-sector organisation.
route B looks like a fit
Put Evolve on top of your current platform first, then move the layers behind it at your own pace.
