661 places to submit your product

Create or claim your tool, add its verified website, product description, sector, founding details, team, and milestones.

Create and verify a complete your tool company page with offerings, target users, location, and canonical website link.

Publish a standards-based your tool JavaScript or TypeScript SDK with generated docs, readme and project links.

Publish a well-documented public your tool API workspace with runnable collections, examples and the canonical API website.

Release a genuine your tool Python SDK or CLI and set Homepage, Documentation and Source URLs to your tool.

Submit a sharp founder-authored opinion based on real privacy or security evidence discovered while building your tool.

Email the strongest developer-focused your tool feature with a self-service demo, documentation, privacy model, and concise reason it is novel.

Send a concise exclusive angle on a new your tool security feature, dataset, vulnerability study, or expert commentary.

Import public your tool developer documentation, add the build config and expose versioned, searchable docs with canonical project links.

Pitch a vendor-neutral security article using original your tool tests, threat-model findings, or privacy research.

Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.

Submit a useful AI privacy, local processing, prompt-security, or responsible-tooling tutorial with reproducible examples.

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.