For builders

Submit an app

Submissions open with the first pipeline release. Here is exactly what will happen when they do — nothing hidden.

What submission will look like

  1. Identify. You sign in with your BellerCreatives account. A paid subscription to a Beller coding tool is what makes you a submitter — there is no anonymous intake.
  2. Declare. You name your app, describe what it does, and declare the license you ship it under. The declaration is published with the listing.
  3. Review. The same review engine BellerBuild runs on your package: exposed keys, open database rules, broken access control, stub handlers. It fails closed — an unavailable reviewer holds your submission, it never publishes on a maybe.
  4. List. A passed review publishes your listing with the scan evidence attached: what was checked, what was found, what the verified badge resolves to.

Until the pipeline opens, the review engine is live today — you can run it on your own project right now.

Run a build review on BellerBuild Code with Super Intelligence Dog

What gets an app rejected

A failed review. A missing or false license declaration. Code that is not yours to ship. Submissions are tied to a real account, and listings are tied to a real review — neither can be bought around. See the store terms, the takedown policy, and the AI disclosure.