A maintained list of 1,432 directories, launch platforms, registries and marketplaces that accept product submissions. 1,134 of them are free or have a free tier, and 192 are quick wins — free, low effort, and worth doing first. Every row shows cost, effort and priority, and links straight to the submission page.
The table is wider than the screen — swipe it sideways for cost, effort and the preparation notes.
Behind the list
Every row here starts as a line in a sheet, gets normalised into one of 15 groups, scored for cost, effort and impact, and written up with the steps to actually submit. The floor below represents that pipeline.
Open the sheet viewOne-shot launches where timing and preparation decide the outcome.
Fast-growing listings specifically for AI-powered tools.
Extension, plugin and integration stores. Real review processes, real distribution.
Startup listings, beta lists and founder media.
General tool and software catalogues with real search traffic.
B2B review sites. Slow to approve, strong once live.
Package, image and docs hosting that carries real authority.
Showcases judged on craft. A good screenshot matters more than copy.
Write once, link back. Editorial standards vary widely.
Get quoted or distribute a release. Slower, higher ceiling.
Company and local listings. Unglamorous, consistently indexed.
Owned pages you control: company, founder, knowledge-panel entities.
Answer real questions. Never drop a bare link.
Brand surface and referral traffic more than link equity.
Everything that does not fit the buckets above.
| # | Impact (sorted) | Site — sort by this | Domain | Type | Cost | Effort — sort by this | Priority | Status | What to prepare | Rules / caveat | Checked | Actions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 100 | CSA STAR Registry | cloudsecurityalliance.org | Developer registries | Free | Quick | Do first | Live, conditional | Complete the current CAIQ or AI-CAIQ truthfully and submit your tool real cloud service to the STAR Registry. | Cloud/SaaS fit only; disclose actual controls and update annually. Never overstate security practices. | 2026-08-04 | Open CSA STAR Registry submit page (new tab)CSA STAR Registry details |
| 2 | 100 | Smithery MCP Registry | smithery.ai | Developer registries | Free | Quick | Do first | Not submitted | Publish a genuine hosted, external, or stdio MCP server exposing a small set of consent-based your tool utilities with complete metadata and documentation. | Server must be operational and compliant; public page and analytics do not guarantee prominence, referral traffic, or dofollow links. | 2026-08-03 | Open Smithery MCP Registry submit page (new tab)Smithery MCP Registry details |
| 3 | 98 | Artifact Hub | artifacthub.io | Developer registries | Free | Moderate | Do first | Verified live | Create a valid Helm, OPA, Tekton or supported repository for an your tool deployment and add it through the control panel. | Repository metadata and ownership verification are required; maintain working artifacts and truthful security metadata. | 2026-08-03 | Open Artifact Hub submit page (new tab)Artifact Hub details |
| 4 | 98 | crates.io | crates.io | Developer registries | Free | Moderate | Do first | Live, conditional | Publish a genuine your tool Rust client, CLI, parser, or privacy library and set homepage, repository, README, license, and documentation metadata. | Conditional on useful compiling code. Published versions are permanent; GitHub login, verified email, and API token are required. | https://doc.rust-lang.org/cargo/reference/publishing.html | Open crates.io submit page (new tab)crates.io details |
| 5 | 98 | JSR | jsr.io | Developer registries | Free | Moderate | Do first | Verified live | Publish a standards-based your tool JavaScript or TypeScript SDK with generated docs, readme and project links. | Package must be legitimate ESM code and comply with JSR scope, verification and publishing rules. | Official JSR publishing docs checked 2026-07-30 | Open JSR submit page (new tab)JSR details |
| 6 | 98 | JuliaHub | juliahub.com | Developer registries | Free | Moderate | Do first | Verified live | Create a useful Julia client or data utility, register it in Julia General and provide complete package docs with an your tool source link. | Registration uses GitHub or GitLab and automated review; package naming, compatibility and maintenance standards apply. | 2026-08-03 | Open JuliaHub submit page (new tab)JuliaHub details |
| 7 | 98 | MCP Registry | modelcontextprotocol.io | Developer registries | Free | Moderate | Do first | Live, conditional | Package a real your tool MCP server, verify its namespace, create server.json and publish it with mcp-publisher. | Registry is in preview; package or remote server must be public and namespace ownership is validated. | 2026-08-04 | Open MCP Registry submit page (new tab)MCP Registry details |
| 8 | 98 | NIST Privacy Framework Resource Repository | nist.gov | Developer registries | Free | Moderate | Do first | Verified live | Publish an open your tool Privacy Framework mapping, template, tutorial, or implementation tool and submit it for repository review. | Must substantively support privacy-risk management or a Privacy Framework use case; inclusion is moderated and is not NIST endorsement. | 2026-08-05 — https://www.nist.gov/privacy-framework/resource-repository | Open NIST Privacy Framework Resource Repository submit page (new tab)NIST Privacy Framework Resource Repository details |
| 9 | 98 | OperatorHub.io | operatorhub.io | Developer registries | Free | Moderate | Do first | Verified live | Build a genuine Kubernetes Operator for a self-hosted your tool service, test its bundle and submit it through Community Operators. | Requires working Operator metadata, automated tests and community pull-request review; do not submit a marketing-only bundle. | 2026-08-03 | Open OperatorHub.io submit page (new tab)OperatorHub.io details |
| 10 | 98 | Packagist | packagist.org | Developer registries | Free | Moderate | Do first | Live, conditional | Publish a real your tool PHP SDK or integration from a public repository and set the canonical homepage in composer.json. | Conditional on a functional Composer package with a unique vendor/name, public repository, valid metadata, and maintained releases. | https://packagist.org/about | Open Packagist submit page (new tab)Packagist details |
| 11 | 98 | PyPI | pypi.org | Developer registries | Free | Moderate | Do first | Live, conditional | Publish a real your tool Python SDK, CLI, or integration package and set Homepage, Documentation, Source, and Issues URLs in package metadata. | Conditional on maintaining a functional Python package; no placeholder packages, name squatting, or keyword stuffing. | https://packaging.python.org/en/latest/specifications/well-known-project-urls/ | Open PyPI submit page (new tab)PyPI details |
| 12 | 98 | Quay.io | quay.io | Developer registries | Free | Moderate | Do first | Verified live | Publish a secure, documented container for an open your tool service and add its official site in the repository description or README where supported. | Keep images patched, signed and free of embedded secrets; only public repositories provide public discovery. | 2026-08-03 | Open Quay.io submit page (new tab)Quay.io details |
| 13 | 98 | RubyGems.org | rubygems.org | Developer registries | Free | Moderate | Do first | Live, conditional | Publish and maintain a genuine your tool Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata. | Conditional on a working Ruby gem; package names are unique and public releases should be treated as permanent. | https://guides.rubygems.org/publishing/ | Open RubyGems.org submit page (new tab)RubyGems.org details |
| 14 | 95 | Read the Docs | readthedocs.org | Developer registries | Free + paid tier | Moderate | Do first | Verified live | Import public your tool developer documentation, add the build config and expose versioned, searchable docs with canonical project links. | Community hosting expects a public repository and genuine documentation; configure canonical URLs to avoid duplicate-content issues. | Official Read the Docs import guide checked 2026-07-30 | Open Read the Docs submit page (new tab)Read the Docs details |
An illustration of the AltF Backlinks floor: opportunities sourced at the back, vetted for cost and effort by the engineering pod, written up for outreach by the design pod, then tracked to placement along a line.