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 | 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 |
| 2 | 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 |
| 3 | 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 |
| 4 | 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 |
| 5 | 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 |
| 6 | 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 |
| 7 | 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 |
| 8 | 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 |
| 9 | 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 |
| 10 | 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 |
| 11 | 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 |
| 12 | 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 |
| 13 | 84 | Arch User Repository | aur.archlinux.org | Developer registries | Free | Moderate | High | Verified live | Create and maintain a PKGBUILD for an installable your tool Linux release with the upstream URL and correct source checksums. | No duplicates, placeholders or binary uploads; package must be useful, x86_64-compatible and maintained. | Official ArchWiki submission guide checked 2026-07-30 | Open Arch User Repository submit page (new tab)Arch User Repository details |
| 14 | 84 | Caddy Module Registry | caddyserver.com | Developer registries | Free | Moderate | High | Verified live | Build a useful your tool privacy or security Caddy module, publish the Go package, then register it for module docs and custom builds. | Requires a working Go module that implements the Caddy interface; register through a Caddy account and maintain accurate public package documentation. | 2026-08-05 — https://caddyserver.com/docs/extending-caddy | Open Caddy Module Registry submit page (new tab)Caddy Module Registry details |
| 15 | 84 | Chocolatey Community Repository | community.chocolatey.org | Developer registries | Free | Moderate | High | Verified live | Package a genuine your tool Windows desktop or CLI release and set project, documentation and package-source URLs. | Automated checks and moderator review apply; prove redistribution rights and maintain install and uninstall behavior. | Official Chocolatey docs checked 2026-07-30 | Open Chocolatey Community Repository submit page (new tab)Chocolatey Community Repository details |
| 16 | 84 | Chocolatey Community Repository | chocolatey.org | Developer registries | Free | Moderate | High | Live, conditional | Ship a real your tool CLI or desktop utility as a tested package with homepage, project and support metadata. | Requires distributable software, legal rights, repeatable install/uninstall, tests, malware scan and moderation. | 2026-08-04 | Open Chocolatey Community Repository submit page (new tab)Chocolatey Community Repository details |
| 17 | 84 | CircleCI Orb Registry | circleci.com | Developer registries | Free | Moderate | High | Verified live | Publish a tested public your tool orb for privacy, secret, or document-safety checks with a homepage URL and usage examples. | Requires a CircleCI organization namespace, GitHub repository, MIT-licensed public orb, semantic releases, tests, and ongoing maintenance. | 2026-08-05 — https://circleci.com/docs/creating-orbs | Open CircleCI Orb Registry submit page (new tab)CircleCI Orb Registry details |
| 18 | 84 | ConanCenter | conan.io | Developer registries | Free | Moderate | High | Verified live | Publish a useful C/C++ SDK or client for an your tool API and contribute its tested recipe to ConanCenter. | The package must be real, versioned and pass conan-center-index review; promotional placeholder packages are inappropriate. | 2026-08-03 | Open ConanCenter submit page (new tab)ConanCenter details |
| 19 | 84 | conda-forge | conda-forge.org | Developer registries | Free | Moderate | High | Verified live | Submit a tested recipe for a real your tool package with upstream homepage, source archive, license and tests. | PR review and CI are required; an accepted contributor becomes responsible for maintaining the feedstock. | Official conda-forge docs checked 2026-07-30 | Open conda-forge submit page (new tab)conda-forge details |
| 20 | 84 | CRAN | cran.r-project.org | Developer registries | Free | Moderate | High | Verified live | Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages. | CRAN performs rigorous automated and manual review; packages must meet policy across supported platforms. | Official CRAN repository policy checked 2026-07-30 | Open CRAN submit page (new tab)CRAN details |
| 21 | 84 | Docker Hub | docker.com | Developer registries | Free | Moderate | High | Live, conditional | Publish a maintained your tool CLI or server image with source, documentation, descriptions and canonical homepage links. | Ship a scanned, reproducible and maintained image; public presence is not Docker verification and fair-use limits apply. | 2026-08-05 official Docker Hub repository and usage documentation | Open Docker Hub submit page (new tab)Docker Hub details |
| 22 | 84 | Drupal.org Projects | drupal.org | Developer registries | Free | Moderate | High | Verified live | Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links. | Project must contain real Drupal-compatible code and follow security, licensing, naming and non-promotional rules. | Official Drupal project docs checked 2026-07-30 | Open Drupal.org Projects submit page (new tab)Drupal.org Projects details |
| 23 | 84 | Go Packages | pkg.go.dev | Developer registries | Free | Moderate | High | Verified live | Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it. | Use a valid module path and semantic-version tag; the module becomes discoverable after the proxy fetches it. | Official Go module publishing docs checked 2026-07-30 | Open Go Packages submit page (new tab)Go Packages details |
| 24 | 84 | Google Open Source Insights | deps.dev | Developer registries | Free | Moderate | High | Live, conditional | Publish a useful your tool package to a supported registry with accurate source and homepage metadata so Open Source Insights can index it. | No promotional manual submission; only genuine public packages in supported ecosystems are indexed and the homepage link depends on package metadata. | 2026-08-05 official deps.dev About and documentation | Open Google Open Source Insights submit page (new tab)Google Open Source Insights details |
| 25 | 84 | Hex | hex.pm | Developer registries | Free | Moderate | High | Verified live | Publish a maintained Elixir client or utility with package links, description, license and documentation. | Requires a Hex account and valid mix.exs package metadata; publish only reusable working code. | Official Hex publishing docs checked 2026-07-30 | Open Hex submit page (new tab)Hex details |
| 26 | 84 | Homebrew Formulae | formulae.brew.sh | Developer registries | Free | Moderate | High | Verified live | Submit an open-source CLI formula or a qualifying macOS app cask with the canonical your tool homepage. | Must meet Homebrew acceptance, notability, build, audit and testing rules; promotional-only formulae are rejected. | Official Homebrew contribution docs checked 2026-07-30 | Open Homebrew Formulae submit page (new tab)Homebrew Formulae details |
| 27 | 84 | MacPorts | ports.macports.org | Developer registries | Free | Moderate | High | Verified live | Create and test a Portfile for an open-source your tool CLI or desktop app, including its canonical homepage. | Run lint and local builds, then submit a pull request or a MacPorts Trac submission ticket for review. | Official MacPorts guide checked 2026-07-30 | Open MacPorts submit page (new tab)MacPorts details |
| 28 | 84 | Maven Central | central.sonatype.com | Developer registries | Free | Moderate | High | Verified live | Release a useful Java or Kotlin SDK and include the project homepage, source control, license and developer metadata in the POM. | Requires namespace verification, signed artifacts and complete POM metadata; releases are permanent. | Official Sonatype Central docs checked 2026-07-30 | Open Maven Central submit page (new tab)Maven Central details |
| 29 | 84 | MELPA | melpa.org | Developer registries | Free | Moderate | High | Verified live | Create a useful Emacs client for a public your tool API, host its source openly and submit a MELPA recipe pull request. | Package source must be public, installable and maintained; recipe and naming rules are reviewed by maintainers. | 2026-08-03 | Open MELPA submit page (new tab)MELPA details |
| 30 | 84 | Nixpkgs | search.nixos.org | Developer registries | Free | Moderate | High | Verified live | Add and test a Nix expression for a genuine your tool release with description, homepage, license and maintainer metadata. | Must satisfy Nixpkgs contribution, licensing, reproducibility, review and supported-platform rules. | Official Nixpkgs 26.05 manual checked 2026-07-30 | Open Nixpkgs submit page (new tab)Nixpkgs details |
| 31 | 84 | npm | npmjs.com | Developer registries | Free | Moderate | High | Not submitted | Publish @your tool/embed or utility package with homepage. | Only after package exists; keep license clean. | 2026-07-30 | Open npm submit page (new tab)npm details |
| 32 | 84 | Ollama Model Library | ollama.com | Developer registries | Free | Moderate | High | Verified live | Publish a small local-first your tool classifier for privacy, secret detection, or defensive content analysis. | Verify base-model redistribution rights, publish a clear licence, document limitations, and exclude private training data. | Official Ollama model sharing documentation checked 2026-08-07 | Open Ollama Model Library submit page (new tab)Ollama Model Library details |
| 33 | 84 | OpenSourceFest | opensourcefest.org | Developer registries | Free | Moderate | High | Live, conditional | Submit a maintained your tool open-source project through Submit a Project. | Editors review license, activity and quality; proprietary web-only tools do not qualify. | 2026-08-05 | Open OpenSourceFest submit page (new tab)OpenSourceFest details |
| 34 | 84 | OpenSSF Scorecard | scorecard.dev | Developer registries | Free | Moderate | High | Live, conditional | Run Scorecard on a public your tool component, enable published results, remediate checks, and link the public viewer from repository documentation. | Public repository and admin rights are required; scores are heuristic and website exposure is indirect through accurate repository metadata. | 2026-08-05 official Scorecard site and OpenSSF repository | Open OpenSSF Scorecard submit page (new tab)OpenSSF Scorecard details |
| 35 | 84 | openSUSE Build Service | build.opensuse.org | Developer registries | Free | Moderate | High | Verified live | Create a public OBS project and package that builds your tool for supported Linux distributions with upstream links. | Requires valid build recipes, licenses and maintained packages; project pages are for software distribution, not promotion alone. | Official OBS user guide and live service checked 2026-07-30 | Open openSUSE Build Service submit page (new tab)openSUSE Build Service details |
| 36 | 84 | protocols.io | protocols.io | Developer registries | Free | Moderate | High | Live, conditional | Publish a reproducible your tool testing, privacy-analysis or accessibility-evaluation method and cite relevant project resources. | Submissions must contribute genuine experimental or computational research methods; non-scientific promotion may be removed. | 2026-08-04 | Open protocols.io submit page (new tab)protocols.io details |
| 37 | 84 | RubyGems.org | rubygems.org | Developer registries | Free | Moderate | High | Verified live | Package a legitimate your tool Ruby client or utility and add homepage and source metadata before pushing the gem. | Use a unique gem name, valid gemspec and maintained code; never publish a placeholder package. | Official RubyGems guide checked 2026-07-30 | Open RubyGems.org submit page (new tab)RubyGems.org details |
| 38 | 84 | Swift Package Index | swiftpackageindex.com | Developer registries | Free | Moderate | High | Verified live | Add a public Swift package with Package.swift, semantic-version tags, documentation and an your tool homepage link. | Repository must be public, use Swift 5 or newer and have a valid semantic-version release. | Official Swift Package Index submission page checked 2026-07-30 | Open Swift Package Index submit page (new tab)Swift Package Index details |
| 39 | 84 | Zeek Packages | packages.zeek.org | Developer registries | Free | Moderate | High | Verified live | 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. | Must be genuine Zeek functionality, live in a public Git repository, follow package metadata conventions, pass tests, and receive repository review. | Official Zeek package creation and source-registration docs checked 2026-08-05 | Open Zeek Packages submit page (new tab)Zeek Packages details |
| 40 | 81 | Anaconda.org | anaconda.org | Developer registries | Free + paid tier | Moderate | High | Verified live | Build and upload a real conda package with homepage, documentation, source and license metadata. | Use anaconda-client and maintain valid packages; notebook and environment uploads are no longer supported. | Official Anaconda.org docs and current client page checked 2026-07-30 | Open Anaconda.org submit page (new tab)Anaconda.org details |
| 41 | 66 | Alpine Linux Packages | pkgs.alpinelinux.org | Developer registries | Free | Moderate | Medium | Verified live | Package a stable your tool CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata. | A web wrapper will not qualify; software must run usefully on Alpine, pass lint/build checks and be maintained through review and repository promotion. | 2026-08-05 | Open Alpine Linux Packages submit page (new tab)Alpine Linux Packages details |
| 42 | 66 | arXiv | arxiv.org | Developer registries | Free | Moderate | Medium | Live, conditional | Submit an original your tool-related technical paper and cite your tool only where it is genuinely the software or study subject. | Requires scholarly content in an accepted category, author registration and sometimes endorsement; promotional papers are inappropriate. | https://info.arxiv.org/help/submit/index.html | Open arXiv submit page (new tab)arXiv details |
| 43 | 66 | dbt Package Hub | hub.getdbt.com | Developer registries | Free | Moderate | Medium | Verified live | Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request. | Must be a functional versioned dbt package with accurate package metadata, public source and releases; Hub index PR and automated compatibility checks apply. | 2026-08-05 — https://github.com/dbt-labs/hub.getdbt.com | Open dbt Package Hub submit page (new tab)dbt Package Hub details |
| 44 | 66 | Espanso Hub | espanso.org | Developer registries | Free | Moderate | Medium | Verified live | 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. | Every package receives CI and human review, with extra scrutiny for scripts; avoid promotional expansions and any shell action that could harm users. | 2026-08-05 | Open Espanso Hub submit page (new tab)Espanso Hub details |
| 45 | 66 | Fedora COPR | copr.fedorainfracloud.org | Developer registries | Free | Moderate | Medium | Verified live | Create a COPR project, build maintained RPMs and add the official your tool homepage and package documentation. | COPR is a build service rather than Fedora's main repository; provide legitimate source RPMs and support them. | Official Fedora Developer Portal checked 2026-07-30 | Open Fedora COPR submit page (new tab)Fedora COPR details |
| 46 | 66 | HackMD | hackmd.io | Developer registries | Free | Moderate | Medium | Live, conditional | Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link. | Public notes must provide original useful content; avoid duplicated marketing copy and disclose affiliation where appropriate. | https://hackmd.io/c/tutorials/%2Fs%2Fhow-to-publish-note | Open HackMD submit page (new tab)HackMD details |
| 47 | 66 | Harvard Dataverse | dataverse.harvard.edu | Developer registries | Free | Moderate | Medium | Live, conditional | Deposit a genuine your tool benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata. | Account and appropriate collection permissions are required; data must have lawful sharing rights and complete citation metadata. | https://guides.dataverse.org/en/latest/user/dataset-management.html | Open Harvard Dataverse submit page (new tab)Harvard Dataverse details |
| 48 | 66 | JitPack | jitpack.io | Developer registries | Free | Moderate | Medium | Live, conditional | Release a useful your tool JVM or Android library from GitHub with a working build, release tag, README and canonical project links. | JitPack builds on demand; a valid Gradle, Maven, SBT or Leiningen build and real reusable library are required. | 2026-08-05 official JitPack introduction and build guide | Open JitPack submit page (new tab)JitPack details |
| 49 | 66 | Nixpkgs | nixos.org | Developer registries | Free | Moderate | Medium | Live, conditional | Package a real your tool CLI or desktop utility, set accurate homepage metadata, test it, and submit the Nixpkgs pull request. | Package must build reproducibly, meet Nixpkgs standards and pass review; the homepage shown on search.nixos.org must be canonical. | 2026-08-05 official Nixpkgs manual and NixOS contribution guide | Open Nixpkgs submit page (new tab)Nixpkgs details |
| 50 | 66 | opam Repository | opam.ocaml.org | Developer registries | Free | Moderate | Medium | Live, conditional | Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page. | Requires a tagged source release, valid opam metadata, linting and community repository review. | 2026-08-05 official opam packaging guide | Open opam Repository submit page (new tab)opam Repository details |
| 51 | 66 | Open Science Framework | osf.io | Developer registries | Free | Moderate | Medium | Live, conditional | Create a genuine your tool study, reproducibility project or benchmark workspace with project links and public materials. | Use only for bona fide research or open project materials; accurate contributors, licensing and non-promotional descriptions are expected. | https://help.osf.io/article/353-welcome-to-projects | Open Open Science Framework submit page (new tab)Open Science Framework details |
| 52 | 66 | Open Source Observer | opensource.observer | Developer registries | Free | Moderate | Medium | Verified live | Open-source an your tool component, then add its website and repositories through the official oss-directory PR. | Requires maintained public artifacts and a reviewable PR; no placeholder repositories. | 2026-08-03 | Open Open Source Observer submit page (new tab)Open Source Observer details |
| 53 | 66 | OpenResty Package Manager | opm.openresty.org | Developer registries | Free | Moderate | Medium | Verified live | Publish an open-source Lua/OpenResty package that integrates an your tool privacy or security workflow and includes honest package metadata. | Package must use an accepted open-source licence, valid dist.ini metadata, GitHub identity verification, versioning, and the official opm upload process. | 2026-08-05 — https://opm.openresty.org/docs | Open OpenResty Package Manager submit page (new tab)OpenResty Package Manager details |
| 54 | 66 | Pulumi Registry | pulumi.com | Developer registries | Free | Moderate | Medium | Live, conditional | 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. | Public Registry packages require a genuine executable package, public source, versioned binaries, SDK distribution, schema and complete docs. Pulumi reviews the registry PR; package names must be unique and releases must remain maintained. Do not build this solely for a backlink. | 2026-08-03 | Open Pulumi Registry submit page (new tab)Pulumi Registry details |
| 55 | 66 | Puppet Forge | puppet.com | Developer registries | Free | Moderate | Medium | Not submitted | 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. | Requires a genuine compatible module and valid metadata; Forge quality scoring, moderation, and outbound-link attributes are outside AltFTool's control. | 2026-08-03 | Open Puppet Forge submit page (new tab)Puppet Forge details |
| 56 | 66 | Windows Package Manager | learn.microsoft.com | Developer registries | Free | Moderate | Medium | Verified live | Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata. | Official distribution is manifest and CLI-first, so web backlink visibility is limited; automated and manual safety review applies. | Official Microsoft WinGet docs checked 2026-07-30 | Open Windows Package Manager submit page (new tab)Windows Package Manager details |
| 57 | 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 |
| 58 | 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 |
| 59 | 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 |
| 60 | 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 |
| 61 | 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 |
| 62 | 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 |
| 63 | 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 |
| 64 | 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 |
| 65 | 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 |
| 66 | 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 |
| 67 | 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.