Publish your app

Apps in the catalogue show up on this site and in every DeepBot, under Apps. Each version is reviewed by people before anyone can install it.

Sign in with GitHub to submit

Your app lives in a public GitHub repository, so your GitHub account is how we know it is yours. We only read your public profile, and you need push access to the repository you submit.

Publish, or keep it to yourself

You do not have to publish. An app runs just as well from developer mode, for you or for a team. Publishing is for when you want anyone to find it and install it with one click.

In the catalogue

Anyone finds it under Apps in DeepBot and installs it with one click, nothing to download or link.
Its own page on deepbot.studio, made from your listing, to share and link to.
Updates reach everyone who has it: you submit a new version, DeepBot offers it to them.
Reviewed by people and installed from a signed package, so people can trust it. It is not marked "Not reviewed".
Works with developer mode off, which is how most people use DeepBot.

Takes: a public GitHub repository, a tag for each version, and a review before it goes live.

In developer mode

No review and no waiting: link it and use it right away.
From a folder on your computer, a .zip, or GitHub, including a private repository with a token.
Changes show as you save, so it is where you build and test.
Good for apps only you or your team need, and for anything you do not want public.

Keep in mind: it is marked "Not reviewed", it loads only while developer mode is on, and everyone who uses it links it and updates it themselves.

How it works

Test it in developer mode. In DeepBot, Apps, Developer mode, link the app's folder and go through the test pass.
Push it to a public GitHub repository. One app at the root, or several apps in folders.
Tag the version. Set version in app.json, commit, then git tag v1.0.0 && git push --tags.
Submit it here. Paste the GitHub link of the repository or of the release. The checks run at once; errors come back with the reason.
We review it. Your dashboard shows the status and our notes. Once approved, the app is in the catalogue and in every DeepBot.

Updates go the same way: raise version in app.json, tag it, paste the link. Every version is reviewed, and DeepBot offers the approved one to everyone who has the app. What we look at and what we turn down is in Test and publish.

A version, once approved, does not change. We keep the exact package we reviewed, signed, and DeepBot installs only that. Moving the tag or pushing new code under the same version reaches nobody; a version number that was approved cannot be submitted again, so a change needs a new one.