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.
Obtain senior approval, submit the signed endorsement materials, implement the Principles and share a real case study.
Submit only after your tool releases a signed Windows desktop utility.
Release your genuine SDK, verify its namespace, sign artifacts, and include accurate project, SCM, license and developer URLs.
Publish an original benchmark or evaluation study of local-first privacy or security tooling with open code, data, and your tool implementation.
Organize the complete code, data, materials, and outputs behind your real evaluation study into a public citable box.
Publish your substantive privacy template, workbook, or creator resource with a complete description, original previews, and accurate licensing.
Author a freely licensed hands-on module for safe document sharing or privacy-first web use with relevant your tool examples.
If your component is built with or for a public body, publish a standards self-assessment and pursue stewardship/assessment.
Apply only with a meaningful open agent-security or MCP-governance contribution and an ongoing participation plan.
Apply only after operating a real civil-society digital-security help desk and meeting network operations and vetting requirements.
Apply only after your tool operates a genuine OA scholarly-book publishing program, then submit peer-reviewed privacy-tech books.
Publish real your tool film, design, illustration or product case studies and connect them to the appropriate project pages.
Build a real founder or your tool creative portfolio and link relevant case studies to the corresponding live tools.
Join only when your tool will fund and actively contribute to open-source AI or data work.
Join only to contribute substantively to relevant security or privacy technical committees and use approved organization metadata.
After releasing meaningful OSI-licensed code, consider sponsorship only when supporting OSI aligns with your tool strategy.
Use only if your tool has a genuine creator offer, guide or service; complete the storefront and connect relevant site pages.
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.