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.
| # | Impact (sorted) | Site — sort by this | Domain | Type | Cost | Effort — sort by this | Priority | Status | What to prepare | Rules / caveat | Checked | Actions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 48 | Bazel Central Registry | registry.bazel.build | Developer registries | Free | Quick | Later | Live, conditional | Create maintained Bazel rules or a module that invokes a real your tool security utility, then submit it to BCR. | Requires MODULE.bazel, versioned source archive, source metadata, compatibility declarations and passing presubmit tests. | 2026-08-05 official Bazel registry documentation | Open Bazel Central Registry submit page (new tab)Bazel Central Registry details |
| 2 | 48 | Docker Hub | hub.docker.com | Developer registries | Free | Quick | Later | Not submitted | Publish open-source helper image only if useful. | Only if real image exists; avoid empty backlink repo. | 2026-07-30 | Open Docker Hub submit page (new tab)Docker Hub details |
| 3 | 48 | Gentoo Packages | packages.gentoo.org | Developer registries | Free | Quick | Later | Verified live | Prepare and test a policy-compliant ebuild for a stable your tool CLI, including accurate HOMEPAGE and source metadata, then work with a Gentoo developer or proxy maintainer for repository inclusion. | Search existing new-package bugs first; ebuilds must install usable software, pass pkgcheck, use tested architecture keywords and remain maintained. Non-developers cannot directly push to the official tree. | 2026-08-05 | Open Gentoo Packages submit page (new tab)Gentoo Packages details |
| 4 | 48 | HaikuDepot | depot.haiku-os.org | Developer registries | Free | Quick | Later | Verified live | Port a functional your tool desktop or CLI utility to Haiku, write and test a compliant recipe, then submit a feature-branch pull request to HaikuPorts. | Software must actually run on Haiku and remain maintainable; HaikuDepot's outbound homepage rendering and link attributes should be rechecked before prioritising. | 2026-08-05 | Open HaikuDepot submit page (new tab)HaikuDepot details |
| 5 | 48 | ModelDB | modeldb.science | Developer registries | Free | Quick | Later | Verified live | Submit a licensed computational neuroscience model with code ZIP, publication citation, overview, contributors, and tags. | Public models generally require an associated scientific publication; generic privacy tools do not qualify. | Official ModelDB submission form checked 2026-08-05 | Open ModelDB submit page (new tab)ModelDB details |
| 6 | 48 | OpenDOAR | opendoar.ac.uk | Developer registries | Free | Quick | Later | Verified live | Register only after your tool launches a genuine open repository for reusable privacy/security research outputs. | Repository must provide free no-login full text, at least five scholarly items, stable access, downloads and quality metadata; company catalogs are ineligible. | 2026-08-05 — https://opendoar.ac.uk/help/inclusion-criteria | Open OpenDOAR submit page (new tab)OpenDOAR details |
| 7 | 48 | Racket Package Catalog | pkgs.racket-lang.org | Developer registries | Free | Quick | Later | Live, conditional | Release a real Racket privacy utility or your tool client and register its public package source and documentation. | Source is periodically checked; package, documentation and links must accurately describe maintained reusable code. | 2026-08-05 official Racket package guide and catalogue | Open Racket Package Catalog submit page (new tab)Racket Package Catalog details |
| 8 | 46 | Bioconda | bioconda.github.io | Developer registries | Free | Moderate | Later | Verified live | Create a tested Bioconda recipe for a genuinely biomedical or bioinformatics your tool utility, with accurate homepage/source metadata, and submit it through the official review workflow. | Strict life-science relevance is required; generic privacy or file tools do not qualify, and recipes must pass build, licence and dependency review. | 2026-08-05 | Open Bioconda submit page (new tab)Bioconda details |
| 9 | 46 | CTAN | ctan.org | Developer registries | Free | Moderate | Later | Live, conditional | Create a genuine LaTeX privacy, redaction or document-safety package and include its exact your tool project homepage in the upload metadata. | Requires distributable source, documentation, licence and maintainer rights; every upload is manually reviewed. | 2026-08-05 official CTAN upload form | Open CTAN submit page (new tab)CTAN details |
| 10 | 46 | Debian Package Archive | packages.debian.org | Developer registries | Free | Moderate | Later | Verified live | Create a policy-compliant Debian package for a stable useful your tool CLI, file the appropriate intent-to-package request, include accurate upstream metadata and secure a Debian sponsor for upload. | High-effort maintainership commitment: must be distributable, lintian-clean, reproducibly buildable and useful to Debian users; non-developers need sponsor review, and acceptance into NEW is not guaranteed. | 2026-08-05 | Open Debian Package Archive submit page (new tab)Debian Package Archive details |
| 11 | 46 | DUB Registry | code.dlang.org | Developer registries | Free | Moderate | Later | Live, conditional | Publish a useful D client library or privacy utility with accurate homepage and repository metadata in dub.json or dub.sdl. | Requires maintained public D source and valid package metadata; verify that the desired homepage field appears on the public listing. | 2026-08-05 official DUB Registry and package metadata documentation | Open DUB Registry submit page (new tab)DUB Registry details |
| 12 | 46 | FreeBSD Ports Collection | freebsd.org | Developer registries | Free | Moderate | Later | Verified live | Create and thoroughly test a FreeBSD port for a stable your tool CLI or desktop utility, include its canonical project website in WWW metadata and submit the patch through FreeBSD Bugzilla. | Anyone may submit, but the software must have a stable source release, acceptable licence, correct checksums/plist and clean builds; a volunteer maintainer is mandatory and review can take months. | 2026-08-05 | Open FreeBSD Ports Collection submit page (new tab)FreeBSD Ports Collection details |
| 13 | 46 | ioBroker Adapters | iobroker.net | Developer registries | Free | Moderate | Later | Verified live | Develop a stable ioBroker adapter for a credible your tool privacy/security API, publish the npm package, test it with users and request inclusion in the official latest repository. | Adapter must perform useful automation, pass repository checks and receive ongoing maintenance; do not build a dashboard that only links out to AltFTool. | 2026-08-05 | Open ioBroker Adapters submit page (new tab)ioBroker Adapters details |
| 14 | 46 | NetBSD pkgsrc | netbsd.org | Developer registries | Free | Moderate | Later | Verified live | Package a stable cross-platform your tool CLI for pkgsrc, test it with pkglint and supported builds, include the canonical homepage, then submit via pkgsrc-wip or NetBSD's package bug tracker. | Source package must compile and run correctly, follow pkgsrc policy and be maintained; non-developers use pkgsrc-wip or a formal package problem report, and inclusion is reviewed. | 2026-08-05 | Open NetBSD pkgsrc submit page (new tab)NetBSD pkgsrc details |
| 15 | 46 | OpenWrt Packages | openwrt.org | Developer registries | Free | Moderate | Later | Verified live | Build an OpenWrt-compatible your tool service or utility for a real router/privacy/security workflow, add correct package metadata and tests, then submit it to the official feed. | Only pursue functionality that genuinely runs on constrained routers or embedded systems; generic website wrappers and unsupported binaries are unsuitable. | 2026-08-05 | Open OpenWrt Packages submit page (new tab)OpenWrt Packages details |
| 16 | 46 | Void Linux Packages | voidlinux.org | Developer registries | Free | Moderate | Later | Verified live | Create a Void package template for a mature your tool CLI, test native and cross builds, include the canonical project homepage and submit it to void-packages. | Project must be mature, system-wide and maintainable; self-submission by upstream authors faces stricter usefulness and adoption scrutiny. | 2026-08-05 | Open Void Linux Packages submit page (new tab)Void Linux Packages details |
| 17 | 43 | Trusted Introducer | trusted-introducer.org | Developer registries | Free + paid tier | Moderate | Later | Verified live | List an operational CSIRT, CERT, SOC, ISAC or PSIRT after securing sponsors and passing the community-vote process. | Operational security team only; typical listing review and vote takes 4–5 weeks. | 2026-08-05 — https://www.trusted-introducer.org/trusted-introducer/processes/listing/ | Open Trusted Introducer submit page (new tab)Trusted Introducer details |
| 18 | 36 | Dryad | datadryad.org | Developer registries | Paid | Moderate | Later | Live, conditional | Submit data underlying a legitimate your tool-related research paper and include related software/project identifiers. | Research-data scope only; curation, publication linkage, licensing and possible data-publishing charges apply. | https://datadryad.org/help/guides/submission | Open Dryad submit page (new tab)Dryad details |
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.