ExtensionMesh

Open project · Early development

Publish extensions. Use them where they connect.

ExtensionMesh connects independent extension sources with the software that installs them. Creators keep control of their releases. Users get a practical way to discover, install and update them.

I build extensions I use extensions
First implementation

Independent registries

R1 Registry Metadata · Releases
R2 Registry Independent source

Explicit boundary

C1 Connector System integration

Supported system

S1 Shopware Current integration

The 1,000-foot view

A shared, open distribution layer between extension creators and users.

Plugins, add-ons and modules are all extensions. Publishing them independently often means building downloads, release metadata, installation and updates again for every system. ExtensionMesh aims to turn that repeated work into open, reusable infrastructure.

01 · Publish Extension creators

Release through an independent registry.

02 · Connect Supported software

A connector translates what the system needs.

03 · Use Extension users

Choose trusted sources and use their extensions.

ExtensionMesh is the connection layer—not a single catalogue, vendor or required source. The first implementation connects independent registries with Shopware; broader conventions will grow from working integrations.

Choose your perspective

What does ExtensionMesh do for me?

The same open infrastructure serves two very different jobs. Start with the side that matches yours.

For creators

I build extensions.

Publish releases through infrastructure you run or choose, while keeping packages, metadata and release decisions under your control.

  • Use an independent registry as your extension source.
  • Avoid rebuilding the full distribution workflow for every release.
  • Reach supported systems through explicit, open connectors.
Follow the creator path
For users

I use extensions.

Connect sources you trust, find their extensions from the software you already use, and keep installed releases up to date.

  • Choose which independent registries your system should trust.
  • Discover and install available extensions through a connector.
  • Receive compatible releases without tracking manual downloads.
Follow the user path

Project model

Distribution without a single required source.

ExtensionMesh separates extension sources from system integration. Registries remain independent; connectors make them usable in a specific environment.

01

Independent registries

Registry operators control their infrastructure, publication process and available extensions.

02

Explicit connectors

System-specific behavior stays in a visible integration boundary instead of being hidden behind broad claims.

03

Open development

Source, documentation and technical decisions are intended to be accessible and shaped by real implementations.

How it fits together

Clear roles.
Practical boundaries.

ExtensionMesh is not presented as a finished universal standard. The current model grows from a working connector and the requirements of independent registries.

Understand the concepts
  1. 01

    A registry publishes extension information.

    It owns its catalogue, releases and distribution infrastructure.

  2. 02

    A connector translates system requirements.

    Discovery, installation and updates are integrated where the system needs them.

  3. 03

    The implementation shapes shared conventions.

    Common interfaces are extracted only when real use cases demonstrate them.

Working vertical slice

See what works.
See what is not stable yet.

Buyer, seller and paid-distribution flows exist in source. The status page separates implemented capabilities from release promises and future ideas.

View project status