Marketplace

A marketplace is a catalog of plugins that developers can browse, install, and update from within Syntic Code. Rather than passing plugins around as zip files or asking people to clone repositories by hand, you publish to a marketplace and let syntic handle discovery and installation. For an organization, a private marketplace becomes the single source of truth for internal tooling: if it is in the catalog, it is approved and supported.

Public and private catalogs

Developers can install from a public marketplace of community plugins, but most organizations also run a private one for internal work. A private marketplace holds plugins that reach your systems, encode your conventions, or are simply not meant to leave the company. Because you control what it contains, it doubles as an approval gate: publishing to the catalog is the moment a plugin becomes officially available, and removing it is how you retire something.

Publishing a plugin

Add a plugin to a marketplace by packaging it with its manifest and pushing it to the catalog source your organization uses, then point syntic at that marketplace so it appears for developers:

syntic marketplace add https://plugins.internal.example.com
syntic plugin install issue-linker

Give each plugin a clear name, a description, and a version so developers understand what it does and which release they are getting before they install it.

Running a marketplace well

Treat the catalog like any other internal service. Review plugins before they are published, since a plugin can run commands and reach your systems, and keep the review bar high for anything with broad permissions. Document what each plugin is for and who owns it so developers know where to send questions. Combine the marketplace with version pinning so the fleet runs known-good releases, and with organization recommendations so the catalog’s best plugins actually reach the people who would benefit from them.