1,432 places to submit your product

Create account, wait cooldown if new, submit your tool as platform alternative.

Request an Analyst Briefing and complete the company survey with product, customer, growth, funding, and market evidence.

Deploy your maintained MCP server from GitHub, Docker, npm, or PyPI, verify maintainer ownership, and switch it public only after production testing.

Launch your platform first; prepare maker comment and assets.

Submit platform, add competitor alternatives, verify domain email.

Publish a genuine hosted, external, or stdio MCP server exposing a small set of consent-based your tool utilities with complete metadata and documentation.

Submit the company website and concise product, market, founder, funding, and traction details for analyst review.

Build and test your useful piece with real actions, publish the package under a unique organization scope, and maintain version compatibility.

Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.

List product under software categories.

Create a transparent human profile and publish a beginner-friendly build log or tutorial showing how one your tool privacy utility works and what tradeoffs it has.

Publish a small open demo that explains one your tool algorithm or UI pattern and add the product website to the founder profile links.

Complete the founder's developer profile, add your tool as real project experience, and publish useful privacy or security engineering posts with contextual links.

Create the founder developer profile, add your tool as a real project, and link the live product and supporting repository where applicable.

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

Audit every your tool subdomain, stage HSTS safely, then submit the base domain only after long-term HTTPS readiness is proven.

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

Build a complete founder profile, add your tool as a shipped startup, and keep milestones, revenue visibility, and product details truthful.

Build and test a Joplin plugin that locally detects or removes sensitive note content, provide a valid manifest and publish a maintained release for discovery.

Create the founder Keybase profile and cryptographically prove control of your tool so the public identity record links the verified domain.

Register the legal company and complete a global B2B profile with accurate IT services, contact data, and your tool website.

Join as your tool founder, create a product page, and document meaningful launches, milestones, and lessons learned.

Create maker profile and launch your tool as project.

Submit your tool widgets plugin after /embed is live.

Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket.

Create startup profile and link website.

Use atlas to find more open-form launch sites and request listing if available.

Create your truthful /founder profile or content page and add the website link where allowed.

Create software vendor listing.

Post how to embed your tool calculators in Ghost after /embed live.

Mirror open-source embed SDK or examples with homepage link.

Submit B2B software listing.

Build a real founder profile and answer narrowly relevant questions, linking to your resource only when it directly substantiates the answer.

Create your truthful /founder profile or content page and add the website link where allowed.

Create startup profile if hiring/startup positioning.

Publish UI/brand case study for your tool.

Create public repo for embed SDK/example package.

Create founder/brand profile linking your tool.

Create business citation profile.

Host privacy-friendly OSS helper repo linking your tool.