Run on open source in the EU
You can compose an Evolve project entirely from open source components that you run yourself: Medusa for commerce, Payload for content, and Meilisearch for search. Hosted at a European provider, that gives you a runtime on infrastructure of a European company, under European jurisdiction. We call this setup Evolve Sovereign.
It is the same Evolve as on any other stack. The storefront, the gateway, and the GraphQL contract do not change; only the components behind the contract and the place they run do. This page puts the components together and lists what else to check. Each component has its own guide, which this page links to.
Two conditions
Section titled “Two conditions”A project that runs in the EU needs both:
- Components you run yourself: commerce, content, and search run on open source software you deploy and operate, so you choose the versions, own the configuration, and decide where each one runs.
- A European provider: software on Azure, AWS, or Google Cloud falls under US law such as the CLOUD Act, also in a European region. What counts is the jurisdiction of the company that operates the infrastructure, not where its data centre is.
The stack
Section titled “The stack”| Layer | Component | Evolve package | Set it up |
|---|---|---|---|
| Commerce engine | Medusa | @evolve-framework/medusa |
Switch commerce engine |
| Content | Payload | @evolve-framework/payload |
Add a CMS |
| Search | Meilisearch | @evolve-framework/search-meilisearch |
Add search |
| Databases | PostgreSQL | One database for Medusa and one for Payload | |
| Cache | Redis | See Infrastructure |
The licenses, as of November 2026:
| Component | License |
|---|---|
| Medusa | MIT, except the Enterprise Edition materials |
| Payload | MIT |
| Meilisearch | MIT for the Community Edition |
| PostgreSQL | PostgreSQL License |
Put it together
Section titled “Put it together”-
Run Medusa as the commerce engine. Follow Switch commerce engine to compose the Medusa modules in your services. They call Medusa’s Store API with a publishable key per store, set in
MedusaConfig, so no admin credentials end up in a public-facing service. -
Add Payload as the CMS. Follow Add a CMS and pick the Payload tab.
PayloadModuleruns Payload’s Local API inside your service, so there is no CMS API to call at request time. To publish content changes as events, passcontentEventstoevolveCms(), as in Publish content changes. -
Add Meilisearch for search. Follow Add search and pick the Meilisearch tab. On Medusa, the catalog reads its products through
MedusaProductDocumentSource; see the note on Medusa at the end of that guide. Run the Community Edition of the Meilisearch server. -
Choose your building blocks at a European provider. Infrastructure lists what a project needs: containers, Redis, a message bus, object storage, a config and secret store, and a CDN. Pick each one from a European provider, and the adapters that fit it, as in Run on your cloud.
Check the rest of the runtime
Section titled “Check the rest of the runtime”The stack above covers commerce, content, and search. Everything else your project calls while it serves a shopper counts too. Go through these before you say your runtime is in the EU:
- Payments: each payment provider is a service of its own. See Add a payment provider.
- Email: transactional email goes out through the provider you configure. See Send emails.
- Observability: traces go to the OpenTelemetry endpoint you set, and errors to Sentry. See Observability.
- Schema registry: the gateway reads the supergraph from the Hive schema registry.
- Analytics, consent, and AI assistants: anything the storefront loads or the services call.
- Telemetry: turn off the telemetry of Medusa and Payload in production.
Some parts sit outside the runtime: the Evolve npm registry and the gateway
image on ghcr.io are used at build and deploy time, as are your source
hosting and CI.

