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 | 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 |
| 3 | 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 |
| 4 | 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 |
| 5 | 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 |
| 6 | 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 |
| 7 | 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 |
| 8 | 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 |
| 9 | 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 |
| 10 | 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 |
| 11 | 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 |
| 12 | 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 |
| 13 | 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 |
| 14 | 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 |
| 15 | 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 |
| 16 | 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 |
| 17 | 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 |
| 18 | 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 |
| 19 | 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 |
| 20 | 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 |
| 21 | 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 |
| 22 | 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 |
| 23 | 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 |
| 24 | 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 |
| 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 | 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 |
| 32 | 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 |
| 33 | 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 |
| 34 | 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 |
| 35 | 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 |
| 36 | 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 |
| 37 | 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 |
| 38 | 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 |
| 39 | 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 |
| 40 | 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 |
| 41 | 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 |
| 42 | 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 |
| 43 | 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 |
| 44 | 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 |
| 45 | 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 |
| 46 | 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 |
| 47 | 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 |
| 48 | 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 |
| 49 | 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 |
| 50 | 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 |
| 51 | 58 | Global Forum on Cyber Expertise | thegfce.org | Developer registries | Paid | Quick | Medium | Verified live | Apply as an eligible Member or Partner and contribute resources or expertise to real cyber-capacity-building working groups. | Companies may apply as Members with commitment/resources; NGO, civil-society, academic or technical Partners need Member endorsement. | 2026-08-05 — https://thegfce.org/become-a-member-or-partner/ | Open Global Forum on Cyber Expertise submit page (new tab)Global Forum on Cyber Expertise details |
| 52 | 58 | Max Package Manager | cycling74.com | Developer registries | Paid | Quick | Medium | Verified live | Publish a Max package for media metadata inspection, audio privacy, or accessibility analysis. | Package structure, package-info.json, README, licence, documentation, and icon are expected before form submission. | Official Cycling '74 package submission documentation checked 2026-08-07 | Open Max Package Manager submit page (new tab)Max Package Manager details |
| 53 | 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 |
| 54 | 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 |
| 55 | 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 |
| 56 | 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 |
| 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 | 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 |
| 59 | 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 |
| 60 | 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 |
| 61 | 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 |
| 62 | 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 |
| 63 | 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 |
| 64 | 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 |
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.