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 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.
Submit only if your tool page/template is built in Webflow.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Release your genuine SDK, verify its namespace, sign artifacts, and include accurate project, SCM, license and developer URLs.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
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.
Submit your focused one-page landing page.
Create your truthful /founder profile or content page and add the website link where allowed.
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.
Create expert profile and answer media queries.
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 your tool (or its blog/feed where required) under productivity, privacy or developer tools.
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.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Register and claim a company profile only if your tool has a genuine German headquarters, branch or founding connection.
Create your truthful /founder profile or content page and add the website link where allowed.
Submit startup profile.
Submit startup if active.
Pitch if your tool has strong startup angle.
Submit startup for feedback/listing.
Submit early-stage product for feedback/visibility.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Create a Void package template for your mature CLI, test native and cross builds, include the canonical project homepage and submit it to void-packages.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Author a freely licensed hands-on module for safe document sharing or privacy-first web use with relevant your tool examples.
Create a polished accessible light/dark developer-documentation theme with your optional pre-deploy audit example, then submit it to the official themes repository.
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.