Publishing to Avanora Market

Preview of the third-party module submission flow (marketplace operator review).

Avanora Market is the cross-plane catalog: operators curate listings in Control; tenants install from Core Marketplace. Third-party publishers ship immutable semver bundles with manifest, config schema, and pricing metadata.

Operator workflow (Control)

1. Create module listing and version row with manifest JSON.
2. Upload signed .tar.gz bundle → Verify → Preview extensions.
3. Sandbox install on a test tenant before Publish.
4. Grant entitlements and push-sync catalog to production tenants.

Submission checklist (preview)

1. Pass manifest validation (@avanora/module-sdk validator) in CI.
2. Provide README, support contact, and changelog per version.
3. Declare availabilityType and pricing model (free, paid add-on, trial, etc.).
4. Complete security questionnaire (permissions justification, data residency, webhook endpoints).
5. Submit bundle hash to Control; operator approves listing before tenants can install.

Partner program

Contact the Avanora platform team for early-access publisher credentials and sandbox tenants. Production listings require signed artifacts and automated vulnerability scanning in a future pipeline phase.

Module SDK package

Install @avanora/module-sdk from the private Verdaccio registry (http://127.0.0.1:4873 via pnpm publish:module-sdk) or the packed release tarball under packages/module-sdk/release/. The package README links to the third-party module developer guide.