Skip to main content
BUNDL
Back to Bundl.run

Submit your Mac app

Makers list a Mac app in the Bundl.run directory from this page. Fill in the form, we email a verification link, and the listing stays a draft until you open that link.

In short

This form creates a directory draft for an app you publish. Homebrew cask, Mac App Store, or a direct download all work. After you verify your email, we review the listing. It does not go live from submit.

Pre-submit checklist

  • Links work (homepage, download, screenshots)
  • Screenshots are your own
  • Price is current
  • Description is specific
  • You have permission to list

Read the guidelines and the review policy before you send.

How listing works

  1. Fill in the app, at least one install path, capabilities, two or more screenshot URLs, and your contact details.
  2. Submit. We store a draft and email a one-time link. That link expires after 24 hours.
  3. Open the link. The draft moves into the review queue.
  4. We check the listing against the guidelines. If something is missing we write back.

Looking for an app you use but do not publish? Request it for the catalog instead. Browse live listings on the apps index.

App

0/80

0/5000 (500 minimum)

Install

At least one

Capabilities

Screenshots

https URLs. Two required, up to six.

Maker

We send the verification link here. Use a permanent address.

Questions makers ask

How do I submit a Mac app to Bundl.run?

Use the form above. You need the app name, a description of at least 500 characters, a https homepage, at least one install path (Homebrew cask, Mac App Store id, or a https dmg/pkg/zip), two screenshot URLs, and a permanent email we can verify.

What happens after I submit?

The listing is saved as a draft. We email a one-time link. After you open it, the listing enters the review queue. Nothing goes live from this form.

What install paths does Bundl.run accept?

A Homebrew cask token, a Mac App Store numeric id, or a direct https URL that ends in .dmg, .pkg, or .zip. You need at least one. Extra paths help reviewers confirm the binary.

Who should use this form versus the request page?

Use this form if you publish the app or have permission to list it. If you want an app added that you use but do not own, use the request page.