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 your profile and add genuinely useful homepage, privacy-tool and accessibility-tool links.
Build table functions that import, normalize and query your tool report JSON or NDJSON with typed findings, then submit the extension descriptor for central build and distribution.
Apply only after your tool becomes a legally registered nonprofit with software central to scalable public impact.
Prepare and test a policy-compliant ebuild for your stable CLI, including accurate HOMEPAGE and source metadata, then work with a Gentoo developer or proxy maintainer for repository inclusion.
Port your functional desktop or CLI utility to Haiku, write and test a compliant recipe, then submit a feature-branch pull request to HaikuPorts.
Submit a licensed computational neuroscience model with code ZIP, publication citation, overview, contributors, and tags.
Build a maintained OctoPrint plugin for your credible -related workflow such as privacy-safe print logs or metadata checks, then register it through the official repository pull request.
Register only after your tool launches a genuine open repository for reusable privacy/security research outputs.
Implement a genuine OpenFeature provider, hook or integration around your configuration or audit-health use case, publish it and add it to the ecosystem documentation.
Submit your tool with the verification badge or use the no-badge paid option.
Build a production-grade Camel component for your tool APIs and propose it upstream with generated component docs and tests.
Submit your -related astronomy utility only after it has been used in research submitted to or published by a refereed journal.
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.
Contribute a documented bioimaging privacy or de-identification model, application integration, or other qualifying resource linked to your tool.
Publish a documented social, ecological, or computational model with source, narrative documentation, contributors, and reproducibility metadata.
Open-source a relevant geoscience model or component, complete the model questionnaire, and provide its code archive for CSDMS testing.
Build a Cytoscape 3 app for a genuine graph privacy, provenance or network-audit workflow, provide website/source metadata and submit its first release for administrator approval.
Create a policy-compliant Debian package for your stable useful CLI, file the appropriate intent-to-package request, include accurate upstream metadata and secure a Debian sponsor for upload.
Create and thoroughly test a FreeBSD port for your stable CLI or desktop utility, include its canonical project website in WWW metadata and submit the patch through FreeBSD Bugzilla.
Build a tested Galaxy wrapper for your medical-data privacy or de-identification workflow and publish it in the main ToolShed.
Develop a stable ioBroker adapter for your credible privacy/security API, publish the npm package, test it with users and request inclusion in the official latest repository.
Build a WASI/LSP Volt that surfaces useful your tool diagnostics for HTML or SEO configuration files, then publish it with the official Volts CLI.
Create a Lua plugin with real commands for your tool URL audits or JSON validation and add a conforming manifest entry to the official Lite XL plugin repository.
Package your stable cross-platform 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.
Propose and contribute your standards-compliant -related bioinformatics privacy module, subworkflow, or full Nextflow pipeline.
Create a meaningful NWB extension for privacy, provenance, or consent metadata and submit its staged-extension YAML through an official pull request.
Organize a rigorous life-science privacy-tool benchmark or participate with your eligible method and publish validated results.
Build a real openHAB add-on that integrates your home-network privacy or safety service, provide addon.xml, tests and documentation, then submit it upstream.
Build your OpenWrt-compatible service or utility for a real router/privacy/security workflow, add correct package metadata and tests, then submit it to the official feed.
Publish an original benchmark or evaluation study of local-first privacy or security tooling with open code, data, and your tool implementation.
Create your truthful /founder profile or content page and add the website link where allowed.
Submit a mature scientific Python package related to your privacy or accessibility workflow for public review and listing.
Build and test a legitimate QIIME 2 plugin for a microbiome-data privacy, validation or provenance use case, then distribute it through the QIIME 2 Library.
Independently reproduce a published computational privacy or security result with open code and data, using your tool only where scientifically justified.
Organize the complete code, data, materials, and outputs behind your real evaluation study into a public citable box.
If your tool produces a research-grade R package, submit a presubmission inquiry and the package for open review.
Build a real ROS package for your robotics/privacy/safety workflow, release it through rosdistro and expose maintained README, documentation and source links in ROS Index.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Publish your substantive privacy template, workbook, or creator resource with a complete description, original previews, and accurate licensing.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
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.