Publish once, install anywhere

You publish as an organisation: a publisher account you create for your team, with its own members and its own page on the marketplace. Before your first module goes out it needs somewhere people can reach you for support, and the module itself needs a name, a description and a line about each thing it does.

Every version is checked automatically before it can be installed anywhere, and you can run that check yourself while you are still building. Once your module is public, one of us reads each new version on top of that. The check looks at whether the module does what its page says, whether member data stays inside the server that installed it, and whether it follows the content rules.

Every decision names its reasons, and you can appeal it from your own listing. While a new version is being read, the version servers already installed keeps running.