Release evidence
Every sellable release is expected to carry version, changelog, checksum, runtime range and immutable artifact metadata.
Trust center
WMTAN Software Marketplace is structured for companies that need to understand what a plugin installs, how it is delivered, how it is supported and what evidence comes with a release.
Every sellable release is expected to carry version, changelog, checksum, runtime range and immutable artifact metadata.
Artifacts stay behind entitlement checks, short-lived download URLs and account or license-key based access.
Product dossiers list routes, install commands, permission assumptions and operational boundaries before purchase.
Pilot, production rollout, maintenance window and update expectations are framed before handoff.
Procurement checklist
The marketplace copy and plugin-side documents are designed to answer buyer, IT, security and operations questions without turning every sale into a custom investigation.
Delivery model
Use this as the default enterprise sales and delivery rhythm for NocoBase plugin projects.
01
Plugin dossier, use cases, compatibility, security posture and commercial fit.
02
Install in a controlled NocoBase instance, validate routes, permissions and rollback path.
03
Publish verified artifact, issue license, document activation and handover contacts.
04
Track changelog, update window, support issues, renewal and compatibility changes.
No product page should claim certification before a real audit exists. The current posture is reviewable engineering evidence and controlled delivery.
Paid releases should be published from immutable artifacts with changelog, checksum and compatibility range.
Database-backed products issue license keys only after payment or manual approval, with rotation and private download controls.