661 places to submit your product

List product under software categories.

Build original interactive web-tool demos as public Pens, write useful details and add your tool among up to three profile links.

Package an your tool accessibility, privacy, or content utility as a Framer plugin and publish it.

Create org/repo README linking your tool; submit to relevant awesome lists.

Add product and post build-in-public story with honest numbers.

Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata.

Build a unique and useful Obsidian plugin, create valid releases and submit it to the community plugin directory.

Add or claim a genuine open-source your tool project and complete its description, code locations, tags and official homepage.

Publish a useful your tool editor extension whose marketplace metadata links to its homepage and documentation.

Publish an installable PHP package in a public repository and submit its composer.json with homepage and support links.

Create maker profile and launch your tool as project.

Build your tool triggers/actions, submit them to the public registry by GitHub PR, and address review feedback.

Publish a stable your tool module or script with ProjectURI, LicenseURI, tags, help and examples.

Publish an your tool Dart package with homepage, repository, issue tracker, documentation and a complete readme.

Build an your tool Slack app, enable public distribution, and submit it for review.

Create a genuine founder profile and share a useful build story or tutorial with a relevant link.

Add your tool’s real company, founder, and team structure with website and role details to create a trustworthy organization profile.

Create an your tool product page for discovery, comparison, and reviews.

Submit your tool widgets plugin after /embed is live.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Build an your tool redaction, accessibility, image, or privacy add-on and submit its public listing.

Submit only an your tool agent that independently decides, acts, and observes.

Submit your tool as a developer or productivity tool for editorial launch coverage.

Create and maintain a PKGBUILD for an installable your tool Linux release with the upstream URL and correct source checksums.

Register as an AWS seller, integrate your tool subscription/billing, test it, and submit for launch.

Claim and verify your tool’s legitimate business entity or location and keep name, address, phone, and website consistent.

Build an your tool Canva privacy, redaction, image, or accessibility add-on and submit it.

Package a genuine your tool Windows desktop or CLI release and set project, documentation and package-source URLs.

Submit a tested recipe for a real your tool package with upstream homepage, source archive, license and tests.

Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages.