When your plugin is built and packaged, publishing takes a key, a signature, and one command. This is the path it follows.
Sign in
spirefy login
spirefy whoami # confirm who you are signed in as
Have a signing key
Marketplace plugins are signed with ML-DSA-65. Generate a key and register its public half with your account:
spirefy key-gen --label my-key --register
Keys live in your local keystore. The fingerprint, the SHA-256 of the public key, is how the marketplace identifies your signature. See signing for detail.
Build, sign, and publish
spirefy build
spirefy pack --sign --key my-key
spirefy publish my-plugin-1.0.0.zp
pack --sign embeds the signature in the package, and publish uploads it. Plugin identifiers are flat and lowercase, like my-importer.
Public or private
A plugin does not have to be public. An organization can publish to its own members only, keeping internal tooling proprietary, and use organization roles to decide who may publish, update, or remove a plugin on its behalf.
Getting paid
Publishing is free. If you charge for a plugin, you start at an 80 percent revenue share, rising to 90 percent as it reaches a larger audience, paid out through Stripe Connect. Pricing for an individual plugin is up to its author.