Submit a Module: Type Check & Certification

Already a publisher? Sign In — your provider details will then be pre-filled.

1Provider

2Module

3Technical

4Documentation

5Review & Submit

Provider

Who is publishing the module? These details will later appear in the Marketplace profile.

Company / developer name *

Contact person *

Email *

Website (optional)

Publisher ID (if available)

VAT ID (required for revenue share)

Module basics

This is how your entry appears in the catalog.

Type of submission *

Extension of a master module New module Script

Which master module is being extended? *

Note: community submissions are published open source under AGPL-3.0 — distribution via the Marketplace fulfills the publication obligation. Private functions from the Enterprise SDK (dual licensing) are not submitted here.

Name *

Version * (SemVer)

Format: MAJOR.MINOR.PATCH, e.g. 1.0.0

Category *

Distribution model *

Short description * (max. 160 characters — appears on the catalog card) Supported channels (optional)

Technical details

The basis for the automated type check against the Module SDK and the validation of calls at the service broker.

Repository URL *

Alternatively, you can upload a package in the next step.

SDK version *

Scope isolation *

Offered contracts * (one per line) Consumed contracts (one per line, optional) External dependencies (optional — services, libraries, APIs) The module passes the local type check (wiresphere test) without errors. *

Documentation & Assets

Required for certification: a complete README. Assets improve your presentation in the Marketplace.

README.md * Drag README.md here or click — contents: purpose, configuration, contracts, examples Documentation chapter (Markdown, optional — appears in the instance documentation of customers who activate your module) Drag doku-kapitel.md here or click CHANGELOG.md (optional) Drag CHANGELOG.md here or click

Logo (PNG/SVG, square)Choose logo

Screenshots (PNG/JPG, up to 5)Choose screenshots

Documentation URL (optional)

Support contact *

Review & Submit

Please review your details. After submitting, the automated type check starts.

Automated type check against the Module SDK (usually < 24 h)
Compatibility and quality review by the certification team (approx. 5 business days)
Feedback or approval by email — the entry then appears in the Marketplace

I accept the certification terms, grant Wiresphere the right to review the submitted code, and publish the submission open source under AGPL-3.0. * I accept the Marketplace terms & conditions, including the revenue share model. * I have taken note of the privacy notice. *