Loading page
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 | 86 | Ansible Galaxy | ansible.com | Developer registries | Free | Quick | High | Not submitted | Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token. | Publish only maintained, useful collection content with accurate metadata and versioning; acceptance does not guarantee discovery, referrals, or followed links. | 2026-08-03 | Open Ansible Galaxy submit page (new tab)Ansible Galaxy details |
| 4 | 86 | GitHub | github.com | Developer registries | Free | Quick | High | Not submitted | Create org/repo README linking your tool; submit to relevant awesome lists. | Only publish original/clean licensed code; no fake stars. | 2026-07-30 | Open GitHub submit page (new tab)GitHub details |
| 5 | 86 | Nimble Directory | nimble.directory | Developer registries | Free | Quick | High | Verified live | Release a maintained Nim client or utility for your tool and publish it through Nimble with accurate repository and homepage metadata. | The package must meet Nimble manifest and source-hosting requirements and remain installable. | 2026-08-03 | Open Nimble Directory submit page (new tab)Nimble Directory details |
| 6 | 86 | Node-RED Flow Library | nodered.org | Developer registries | Free | Quick | High | Verified live | Create a functional your tool Node-RED node, publish it to npm, and add it to the Flow Library with documentation and support metadata. | Must follow Node-RED naming, package metadata, node UX, testing, and documentation conventions and avoid thin wrappers. | Official Node-RED custom node documentation checked 2026-08-07 | Open Node-RED Flow Library submit page (new tab)Node-RED Flow Library details |
| 7 | 86 | NuGet | nuget.org | Developer registries | Free | Quick | High | Verified live | Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata. | Requires a Microsoft account and API key; packages undergo validation and indexing. | Official Microsoft NuGet docs checked 2026-07-30 | Open NuGet submit page (new tab)NuGet details |
| 8 | 86 | PlatformIO Registry | registry.platformio.org | Developer registries | Free | Quick | High | Verified live | Package a real embedded privacy or security library for supported boards, add complete PlatformIO manifest and examples, test it, and publish it publicly. | Published name-version pairs are immutable; package must be functional, properly licensed, documented, versioned, and maintained. | Official PlatformIO package-publish documentation checked 2026-08-05 | Open PlatformIO Registry submit page (new tab)PlatformIO Registry details |
| 9 | 86 | PowerShell Gallery | powershellgallery.com | Developer registries | Free | Quick | High | Verified live | Publish a stable your tool module or script with ProjectURI, LicenseURI, tags, help and examples. | Requires an account and API key; pass PowerShell Gallery validation and avoid placeholder packages. | Official Microsoft publishing docs checked 2026-07-30 | Open PowerShell Gallery submit page (new tab)PowerShell Gallery details |
| 10 | 86 | pub.dev | pub.dev | Developer registries | Free | Quick | High | Verified live | Publish an your tool Dart package with homepage, repository, issue tracker, documentation and a complete readme. | Must satisfy pub.dev policy and quality checks; a verified publisher is preferable for a branded package. | Official Dart publishing docs checked 2026-07-30 | Open pub.dev submit page (new tab)pub.dev details |
| 11 | 86 | Pulsar Package Registry | pulsar-edit.dev | Developer registries | Free | Quick | High | Verified live | Build a maintained Pulsar editor package that performs a real your tool workflow, then publish it to the official package registry with a useful README and project link. | Package must be hosted on GitHub and include valid package.json metadata, SemVer and Pulsar engine constraints; it must provide real editor functionality, not a backlink wrapper. | 2026-08-05 | Open Pulsar Package Registry submit page (new tab)Pulsar Package Registry details |
| 12 | 86 | Terraform Registry | registry.terraform.io | Developer registries | Free | Quick | High | Live, conditional | Publish a maintained Terraform provider for your tool stable API, or a genuinely reusable deployment module, with signed releases, generated documentation, examples, tests, and semantic versions. | A provider must use a public lowercase terraform-provider-* GitHub repository, signed cross-platform release assets, a valid manifest, docs, and SemVer tags. A module has separate public-repository, naming, structure, documentation, and tag requirements. Publish only a functional reusable artifact. | 2026-08-03 | Open Terraform Registry submit page (new tab) |
| 13 | 86 | WorkflowHub | workflowhub.eu | Developer registries | Free | Quick | High | Verified live | Package a reproducible your tool privacy or redaction workflow, join or create a team, and register it with rich metadata and source links. | Requires a real executable workflow file, team membership, accurate authorship/licence metadata, and a maintained public entry. | 2026-08-05 — https://about.workflowhub.eu/docs/registering_workflows/registering-a-workflow/ | Open WorkflowHub submit page (new tab)WorkflowHub details |
| 14 | 68 | Awesome Privacy | awesome-privacy.xyz | Developer registries | Free | Quick | Medium | Needs checking | Submit only after public privacy policy and client-side privacy proof. | Human-written PR; no AI-generated PR text. | 2026-07-30 | Open Awesome Privacy submit page (new tab)Awesome Privacy details |
| 15 | 68 | Chef Supermarket | chef.io | Developer registries | Free | Quick | Medium | Not submitted | Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket. | Only publish functional maintained cookbooks with appropriate licensing and metadata; package pages are not guaranteed promotional or dofollow placements. | 2026-08-03 | Open Chef Supermarket submit page (new tab)Chef Supermarket details |
| 16 | 68 | Clojars | clojars.org | Developer registries | Free | Quick | Medium | Verified live | Release a genuine Clojure or JVM client library with a POM, description, homepage and source metadata. | Requires an account and deploy credentials; use a unique group or verified domain and maintain releases. | Official Clojars publishing interface checked 2026-07-30 | Open Clojars submit page (new tab)Clojars details |
| 17 | 68 | Cloudsmith | cloudsmith.com | Developer registries | Free | Quick | Medium | Live, conditional | Create a public your tool package repository for genuine releases and complete its namespace, description, licence and source/homepage metadata. | Only host real maintained artifacts; the open-source plan requires public licensed software and public distribution can incur usage limits. | 2026-08-05 official Cloudsmith repository docs and pricing | Open Cloudsmith submit page (new tab)Cloudsmith details |
| 18 | 68 | CocoaPods | cocoapods.org | Developer registries | Free | Quick | Medium | Live, conditional | Publish a genuine iOS or macOS your tool SDK and set homepage/source URLs in its podspec. | Requires a valid podspec and Trunk registration; package must be an actual reusable Apple-platform library. | https://guides.cocoapods.org/making/getting-setup-with-trunk.html | Open CocoaPods submit page (new tab)CocoaPods details |
| 19 | 68 | CPAN / PAUSE | cpan.org | Developer registries | Free | Quick | Medium | Verified live | Publish a genuine Perl module or CLI through PAUSE with project URLs and clear distribution documentation. | Requires a PAUSE account, unique namespace and ongoing maintenance; first uploader controls the namespace. | Official CPAN PAUSE docs checked 2026-07-30 | Open CPAN / PAUSE submit page (new tab)CPAN / PAUSE details |
| 20 | 68 | Django Packages | djangopackages.org | Developer registries | Free | Quick | Medium | Live, conditional | After releasing a genuinely Django-relevant open-source component, sign in and add its GitHub or GitLab repository and accurate project links. | Package must be useful to Django developers and hosted on a supported public repository; listings are community-maintained and not DSF endorsement. | 2026-08-05 official Django Packages FAQ, documentation and live directory | Open Django Packages submit page (new tab)Django Packages details |
| 21 | 68 | ESP Component Registry | components.espressif.com | Developer registries | Free | Quick | Medium | Verified live | Build an ESP-IDF privacy, credential-safety, secure-logging, or local-processing component, add manifest, license, docs, examples, and publish it through the registry workflow. | Must be an actual ESP-IDF component; namespace, semantic versioning, linting, licensing, dependency, documentation, and upload rules apply. | Official ESP Component Registry publishing documentation checked 2026-08-05 | Open ESP Component Registry submit page (new tab)ESP Component Registry details |
| 22 | 68 | FlakeHub | flakehub.com | Developer registries | Free | Quick | Medium | Live, conditional | Publish a genuine versioned your tool Nix flake under the correct GitHub owner and maintain its README and project links. | Published versions are archived permanently; ownership, licence and repository association must be accurate and squatting is inappropriate. | 2026-08-05 official FlakeHub homepage, usage policy and pricing | Open FlakeHub submit page (new tab)FlakeHub details |
| 23 | 68 | freshcode.club | freshcode.club | Developer registries | Free | Quick | Medium | Live, conditional | Submit a real maintained your tool open-source release with accurate categories and project metadata. | Use only for an actual open-source project and keep releases maintained. | 2026-08-05 | Open freshcode.club submit page (new tab)freshcode.club details |
| 24 | 68 | getfolio.dev | getfolio.dev | Developer registries | Free | Quick | Medium | Verified live | Create a founder/developer portfolio, pin your tool repository/project and add the official website link. | Use a real GitHub identity and maintained projects; avoid a profile created only for SEO. | 2026-08-03 | Open getfolio.dev submit page (new tab)getfolio.dev details |
| 25 | 68 | Hackage | hackage.haskell.org | Developer registries | Free | Quick | Medium | Verified live | Release a useful Haskell library or command-line client with homepage, source and bug-report metadata. | Hackage requires open-source, meaningful packages; uploaded versions cannot simply be replaced. | Official Hackage upload page checked 2026-07-30 | Open Hackage submit page (new tab)Hackage details |
| 26 | 68 | Haxelib | lib.haxe.org | Developer registries | Free | Quick | Medium | Live, conditional | Release a useful Haxe SDK or privacy utility and set haxelib.json's URL to the relevant your tool documentation page. | Requires reusable code, semantic versions and accurate metadata; promotional-only packages are not appropriate. | 2026-08-05 official Haxelib package guide | Open Haxelib submit page (new tab)Haxelib details |
| 27 | 68 | Knowledge Commons / CORE | hcommons.org | Developer registries | Free | Quick | Medium | Verified live | Create a truthful scholarly profile and deposit an original privacy, accessibility, or digital-humanities paper or teaching resource with its related your tool URL. | Work must genuinely serve scholarship or pedagogy; upload only rights-cleared material, not sales copy. | 2026-08-05 — https://registry.hcommons.org/registry/co_petitions/start/coef%3A158 | Open Knowledge Commons / CORE submit page (new tab)Knowledge Commons / CORE details |
| 28 | 68 | LuaRocks | luarocks.org | Developer registries | Free | Quick | Medium | Verified live | Create a useful Lua client or helper, publish its rockspec and include homepage, license and source links. | Only publish a working Lua module with correct dependencies and versioned source archives. | Official LuaRocks page checked 2026-07-30 | Open LuaRocks submit page (new tab)LuaRocks details |
| 29 | 68 | OpenTofu Public Registry | registry.opentofu.org | Developer registries | Free | Quick | Medium | Live, conditional | Release a reusable your tool-related security or privacy module from a correctly named public GitHub repository. | Requires standard module structure, terraform-NAME-TARGETSYSTEM naming and semantic Git tags; confirm external homepage display before investing. | 2026-08-05 official OpenTofu module publishing guide | Open OpenTofu Public Registry submit page (new tab)OpenTofu Public Registry details |
| 30 | 68 | Repoz | repoz.io | Developer registries | Free | Quick | Medium | Live, conditional | Submit a maintained your tool open-source component for community review. | Requires a genuine public open-source project; do not submit an empty promotional repository. | 2026-08-05 | Open Repoz submit page (new tab)Repoz details |
| 31 | 68 | Scoop | scoop.sh | Developer registries | Free | Quick | Medium | Live, conditional | Publish and maintain a tested Scoop manifest for an actual portable your tool Windows CLI or app. | Requires a real release, immutable URLs and hashes, silent install behavior, updates and bucket-specific acceptance. | 2026-08-04 | Open Scoop submit page (new tab)Scoop 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.