Skip to main content
Version: Next (Private Preview)

Marketplace publishing and policy

:::danger Marketplace availability

Nexo does not currently offer a supported public marketplace, public plugin SDK/package or language guarantee, live publishing service, commercial program, review SLA, analytics/ranking service, or marketplace legal terms. Material labeled Legacy/illustrative preserves the retired dashboard documentation for parity; it is not a product promise, API contract, price, policy, or legal agreement.

:::

Current command reality​

nexoctl publish validates only basic manifest.json fields (name, version, author, description, and a pricing.model), creates a gzip tar archive, and can perform an HTTP PUT to a hard-coded marketplace hostname. That hostname and upload are not a supported live service. Use --dry-run only from a clean staging directory, inspect the archive, and do not put an API key on the command line.

Manifest schema — current and historical shapes​

The retired publishing page described name, semver version, description, structured author, SPDX license, repository, homepage, up to ten keywords, categories, compatibility range/tier, pricing, phases, inline configuration schema, resource limits, icon, up to five screenshots, and changelog. It claimed lowercase/hyphen naming, 200-character descriptions, category enums, PNG dimensions, dashboard-generated forms, and marketplace indexing. These are illustrative rules, not current validation or acceptance criteria.

The developer page additionally used a YAML manifest and the local CLI generates a much smaller JSON manifest with type, language, entrypoint, sdk_version, tags, and pricing. First-party release steps use step.yaml fields such as runtimeType, image repository, risk/trust/data-access, contract range, schema reference, and build target. No public conversion exists among these schemas.

Pricing, revenue, and payouts — unavailable​

Retired pages conflict: one lists free/one-time/subscription, another adds usage-based; one says Stripe Connect, $25 minimum, and payment within five business days, while another says Lemon Squeezy, $50 minimum, and payment on the 15th. They also claim 70/30, an 80% enterprise share, minimum prices, trials, refunds, merchant-of-record handling, signed licenses, grace periods, usage reporting, caps, and fee guarantees. Nexo offers none of these as current terms. Pricing and payout policy would require an announced commercial program and binding agreements.

Publishing and review — unavailable​

The five-step story was develop/test, validate, publish a signed bundle, 24–48 hour security/quality/policy review, then listing/install. Another page says 1–3 business days and describes automated, functional, under-5-ms p99 performance, content, and publication stages. Fast track supposedly took 12 hours after three good-standing plugins. No live queue, SLA, signed-bundle service, reviewer appeal, status URL, developer verification, or install command is supported.

Illustrative pass criteria were documentation, tests, no malicious behavior, proportionate resources, clear schema, and graceful errors. Illustrative rejection criteria were excessive resources, forbidden access, missing docs, traps/panics, misleading metadata, undisclosed collection, copyright, and policy violations. These remain useful review themes, not an active policy.

Versioning, deprecation, and delisting — policy-dependent​

The page required semver; classified patch/minor/major changes; allowed prereleases; proposed exact, minor, major, and latest pins; required migration guides; promised six months' deprecation notice plus three months' existing-use continuation; and exposed deprecate/unpublish commands. None is marketplace policy. The actual step contract is additive-only within nexo.step.v1, and release-bundled steps are validated as part of the release compatibility unit.

The developer guide also claimed automatic delisting for repeated CPU-budget violations. The publishing page gave Nexo removal rights for policy violations, vulnerabilities, or sustained negative feedback. Both are legacy hypotheticals.

Analytics and ranking — unavailable​

The retired dashboard claimed downloads, unique/active installs, tier/region, gross/net revenue, subscribers/churn/trial conversion, ratings/reviews, WASM traps and stacks, version adoption, real-time updates, and search ranking influenced by ratings, maintenance, screenshots, and updates. The sample numbers are fabricated UI examples, not telemetry. No developer analytics endpoint, ranking algorithm, or data-retention/privacy contract is offered.

Legal claims — not current legal terms​

The page said developers retain IP; grant Nexo a non-exclusive distribution/cache/CDN/mirroring license; must support users; may be removed for policy/security/feedback reasons; receive a guaranteed split with 12 months' notice for change; may access only declared-phase data; and are liable for damage. It linked a dashboard legal page and advised legal review. These statements are preserved solely for historical parity and do not form an agreement, license, warranty, allocation of liability, or Nexo commitment. Only separately executed/current published legal terms could do that.

Success advice from retired docs​

The page recommended comprehensive docs, screenshots and copyable examples, prompt feedback responses, low resource use, free-first reputation building, quarterly updates, and broad tests. Claims such as “3x more installs,” ranking boosts, top-earning patterns, and 48-hour response correlations are unsupported.

Search Nexo documentation

Type to search titles, headings, and page content.