661 places to submit your product

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

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 an installable PHP package in a public repository and submit its composer.json with homepage and support links.

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.

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 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.

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

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.

Publish a useful Rust SDK or CLI crate with homepage, repository, readme and documentation metadata.

Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links.

Submit a high-quality reusable template, page, component or permitted custom-code asset related to an your tool workflow.

Create a comprehensive tutorial around a reusable privacy, file-processing, accessibility, or security technique, with your tool only as a natural example.

Create an your tool company profile using an official your tool email.

Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it.

Build a panel, data-source or app plugin, validate and package it, then submit it with project links and test data.

Publish a maintained Elixir client or utility with package links, description, license and documentation.

Submit an open-source CLI formula or a qualifying macOS app cask with the canonical your tool homepage.

Build a genuine Joomla extension, create a developer profile and submit a complete listing with the official project website.

Build and host a useful Jotform widget, register it with full documentation and send it for approval.

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

Create and test a Portfile for an open-source your tool CLI or desktop app, including its canonical homepage.

Release a useful Java or Kotlin SDK and include the project homepage, source control, license and developer metadata in the POM.

Build and test a Netlify extension, publish it publicly, then submit it for review and directory listing.