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.
If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.
Build and openly maintain a Backstage plugin that gives platform teams your real workflow, then announce it through the community-plugins process and meet directory metadata requirements.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
If your tool documentation genuinely runs on Docusaurus, add the polished docs site through the official showcase discussion.
Submit a mature graphical Linux your app with verified metadata, screenshots, homepage and source links.
Create a useful Grav privacy or security plugin and request inclusion through the official repository issue process.
Apply as a startup with your tool website, category, location, description and product details.
Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.
Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.
After releasing your real CLI or native app, submit a tested formula or cask with its canonical homepage.
Publish your Android app through AppGallery Connect with official site, support and privacy URLs.
Archive your authentic release, manual or research artifact with accurate metadata and official source URL.
If your tool releases a suitable open-source Android app, request inclusion with public source, tagged APK releases, Fastlane metadata and website links.
Release your useful JVM or Android library from GitHub with a working build, release tag, README and canonical project links.
After your tool has a stable, commonly used JSON or YAML configuration format, contribute its accurate schema and test fixtures so editors can provide validation, completion, and tooltips.
Build your metadata-cleaning, accessibility or privacy plugin and submit its repository and cover image.
Build your real kubectl privacy or security scanner and submit its release manifest with a canonical project homepage.
Package your real CLI or desktop utility, set accurate homepage metadata, test it, and submit the Nixpkgs pull request.
Apply with your concrete privacy, security or user-autonomy FOSS work package, milestones, budget and public repository.
Build a working OnePageCRM integration and apply for testing, verification and a dedicated marketplace page.
Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Package your useful browser feature as an Opera extension and submit it for moderation.
Submit only original, deep security research or a durable technical guide with reproducible evidence; your tool may be mentioned solely as the research implementation when material.
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.
Distribute your Android or Galaxy app and add its official website and support information.
Create a truthful author account and submit your substantive privacy, security or accessibility working paper with legitimate citations.
Build your Trello Power-Up, register it, sign the developer agreement, and submit it.
Build and test your useful Visual Studio or Azure DevOps extension, then publish it with truthful homepage, repository and overview metadata.
Use the free reviewed tier for a real AI-powered tool, with a complete and accurate product profile.
Launch your real educational podcast, complete its public site, and cite relevant tools and sources in useful show notes.
Create an authentic your tool or founder design portfolio with substantive case studies and contextual links to shipped tools.
Submit your maintained developer tool with concise description, pricing and relevant tags.
Convert your original guide into a public flipbook and add contextual links or web embeds for cited tools and resources.
Build a secure Jenkins plugin that performs your real CI, privacy, or accessibility workflow; host it through Jenkins project infrastructure and publish maintained releases and documentation.
Package your tool developer/security utilities as a compatible JetBrains plugin and upload it.
Run a genuine privacy, online-tools or accessibility community and reference your tool only where it supports the group or event.
Create your organization, set its official website, and publish a real free or paid digital product or subscription.
Use pretalx for your genuine community conference or submit relevant talks to events that use the platform.
Build a legitimate Ring-device privacy/security integration, register, test, certify and publish it.
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.