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.
Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.
Create org/repo README linking your tool; submit to relevant awesome lists.
Release a maintained Nim client or utility for your tool and publish it through Nimble with accurate repository and homepage metadata.
Create your functional Node-RED node, publish it to npm, and add it to the Flow Library with documentation and support metadata.
Publish a real .NET library or CLI package with ProjectUrl, readme, repository and license metadata.
Package a real embedded privacy or security library for supported boards, add complete PlatformIO manifest and examples, test it, and publish it publicly.
Publish your stable module or script with ProjectURI, LicenseURI, tags, help and examples.
Publish your Dart package with homepage, repository, issue tracker, documentation and a complete readme.
Build a maintained Pulsar editor package that performs your real workflow, then publish it to the official package registry with a useful README and project link.
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.
Package your reproducible privacy or redaction workflow, join or create a team, and register it with rich metadata and source links.
Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.
Build your useful privacy or security Caddy module, publish the Go package, then register it for module docs and custom builds.
Package your genuine Windows desktop or CLI release and set project, documentation and package-source URLs.
Ship your real CLI or desktop utility as a tested package with homepage, project and support metadata.
Publish your tested public orb for privacy, secret, or document-safety checks with a homepage URL and usage examples.
Publish a useful C/C++ SDK or client for your API and contribute its tested recipe to ConanCenter.
Submit a tested recipe for your real 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 your maintained CLI or server image with source, documentation, descriptions and canonical homepage links.
Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links.
Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it.
Publish your useful package to a supported registry with accurate source and homepage metadata so Open Source Insights can index it.
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 your canonical homepage.
Create and test a Portfile for your open-source 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.
Create a useful Emacs client for your public API, host its source openly and submit a MELPA recipe pull request.
Add and test a Nix expression for your genuine release with description, homepage, license and maintainer metadata.
Publish your small local-first classifier for privacy, secret detection, or defensive content analysis.
Submit your maintained open-source project through Submit a Project.
Run Scorecard on your public component, enable published results, remediate checks, and link the public viewer from repository documentation.
Create a public OBS project and package that builds your tool for supported Linux distributions with upstream links.
Publish your reproducible testing, privacy-analysis or accessibility-evaluation method and cite relevant project resources.
Package your legitimate Ruby client or utility and add homepage and source metadata before pushing the gem.
Add a public Swift package with Package.swift, semantic-version tags, documentation and your homepage link.
Build a defensive Zeek script or plugin for privacy-safe log inspection, include zkg metadata and tests, then register it in the default Zeek package source.
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 viewAn 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.
One-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.