A connector lets your software use independent extension registries. You choose the sources you trust; the connector handles how their extensions appear, install and update in your system.
Why this exists
Independently distributed extensions often arrive as downloads, setup instructions and update notices spread across different websites. That can work, but it makes installation and maintenance unnecessarily manual.
ExtensionMesh aims to bring those sources into a supported system through a visible connector. You keep the choice of source while gaining a more consistent workflow.
Your path through ExtensionMesh
Install the connector for your system
The connector provides the system-specific integration required to use compatible registries.
Add a registry you trust
A registry is an independent extension source. Its operator—not ExtensionMesh—decides what it publishes and how access works.
Discover compatible extensions
The connector presents the registry information using the mechanisms available in your software and handles the installation boundary.
Receive compatible updates
When the registry publishes a new compatible release, the connector can make it available through the same system workflow.
Trust remains your decision
Open distribution does not mean that every source or extension is automatically reviewed. A registry remains responsible for what it publishes, and system administrators remain responsible for choosing sources and evaluating the code they install.
- Only add registries whose operator and policies you understand.
- Review publisher, version, compatibility and access information.
- Treat extensions as software that receives access to your system.
- Follow security guidance from the registry and extension publisher.
What ExtensionMesh is not
ExtensionMesh is not one required catalogue, a certification authority or a promise that every extension works in every system. Connectors explicitly define which systems and registry behavior they support.
What works today
The first connector targets Shopware and is still in early development. Concrete installation and configuration instructions will live with that connector as its user-facing workflow stabilizes.
What you can validate today
- Configure persistent registry sources in a Shopware 6.7 test installation.
- Use a compatible registry URL or GitHub repository URL as a source.
- Discover compatible releases and hand installation or updates to the native plugin lifecycle.
- Use credentials for private or paid sources without exposing them through the Administration API.
The current implementation is pre-stable. Evaluate it in an isolated environment before considering production use, and review the source, registry operator and extension packages as separate trust decisions.
Continue with the connector model, or check the current implementation.