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.
Submit only after public privacy policy and client-side privacy proof.
Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket.
Release a genuine Clojure or JVM client library with a POM, description, homepage and source metadata.
Create your public package repository for genuine releases and complete its namespace, description, licence and source/homepage metadata.
Publish a genuine iOS or macOS your tool SDK and set homepage/source URLs in its podspec.
Publish a genuine Perl module or CLI through PAUSE with project URLs and clear distribution documentation.
After releasing a genuinely Django-relevant open-source component, sign in and add its GitHub or GitLab repository and accurate project links.
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.
Publish your genuine versioned Nix flake under the correct GitHub owner and maintain its README and project links.
Submit your real maintained open-source release with accurate categories and project metadata.
Create a founder/developer portfolio, pin your tool repository/project and add the official website link.
Release a useful Haskell library or command-line client with homepage, source and bug-report metadata.
Release a useful Haxe SDK or privacy utility and set haxelib.json's URL to your relevant documentation page.
Create a truthful scholarly profile and deposit an original privacy, accessibility, or digital-humanities paper or teaching resource with its related your tool URL.
Create a useful Lua client or helper, publish its rockspec and include homepage, license and source links.
Release your reusable -related security or privacy module from a correctly named public GitHub repository.
Submit your maintained open-source component for community review.
Publish and maintain a tested Scoop manifest for your actual portable Windows CLI or app.
Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.
Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.
Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.
Create a genuinely useful package of tested security-header, HTML-meta, JSON-LD and webhook snippets with your tool validation examples, then submit it to the official Hub.
Create a COPR project, build maintained RPMs and add your official homepage and package documentation.
Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.
Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.
Release your useful JVM or Android library from GitHub with a working build, release tag, README and canonical project links.
Package your real CLI or desktop utility, set accurate homepage metadata, test it, and submit the Nixpkgs pull request.
Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Open-source your component, then add its website and repositories through the official oss-directory PR.
Publish an open-source Lua/OpenResty package that integrates your privacy or security workflow and includes honest package metadata.
Publish a real multi-language Pulumi provider or component for deploying or configuring your tool, with binaries, SDK packages, schema, documentation, examples, tests, and a registry pull request.
Build and test a Puppet module for supported your tool setup or security policy, complete metadata.json, package it, and publish through a Forge account.
Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata.
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.