Extension guide

A plugin marketplace is useful only if discovery and adoption stay governable instead of turning into uncontrolled extension sprawl.

Plugin marketplace management matters because discoverability alone is not enough. Teams also need to know which sources are trustworthy, how plugin choices fit support expectations, and how extensions remain explainable over time. Spectra treats marketplace management as part of the extension operating layer rather than a disconnected catalog.

Last updated: 2026-03-30

Plugin marketplaceExtension governanceSource trustSupportability

Plugin growth becomes much easier to support when discovery and governance live in the same product story

A marketplace needs more than convenience. It needs operating discipline too.

What goes wrong without marketplace governance

  • Teams add plugins without a clear source or trust model.
  • Support cannot easily explain why extension behavior differs across users.
  • Plugin choice becomes harder to standardize over time.
  • Marketplace convenience turns into capability sprawl.

What a stronger marketplace model provides

  • Clearer visibility into plugin discovery and adoption paths.
  • Better alignment between plugin choice and team policy.
  • A more supportable relationship between plugins and the desktop workspace.
  • A cleaner bridge from experimentation to managed extension use.

If plugins matter, discovery should be managed in this order

Governance gets easier when discovery and source control are not treated as separate worlds.

01

Start from the broader extension layer

Understand the plugin marketplace as one part of the product's extension operating model.

02

Keep source and trust visible

Marketplace convenience is safer when users still understand what they are adopting.

03

Align plugin choice with team norms

The more visible the policy is, the easier plugin usage is to scale.

Plugin marketplace management matters most when extension discovery is becoming a shared team behavior

The value rises as soon as plugin choice starts affecting support, consistency, and trust.

Plugin-heavy users

You want discovery to stay practical without turning chaotic.

Team leads

You need plugin growth to remain explainable and manageable.

Platform teams

You want extension adoption to fit broader governance expectations.

Support owners

You want fewer surprises caused by invisible plugin differences.

Common questions about plugin marketplace management

Why does the plugin marketplace need its own page?

Because plugin discovery affects supportability and governance, not just convenience.

How is this different from MCP registry management?

Registry management focuses on extension sources and registries, while marketplace management focuses on discoverability and adoption control.

Who benefits most from a managed marketplace model?

Teams and advanced users who expect plugin growth to stay supportable and explainable over time.

If plugin governance matters, the next topics are registry control, team rollout, and extension operations

These pages continue from marketplace management into the broader extension and team support model.