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.
Build your working automation Actor, publish it to the Store and include contextual project/documentation links.
Package your legitimate desktop app as an official AppImage, then file the requested issue or pull request for inclusion.
If your property genuinely uses Astro, use the Submit site action to propose it for the public showcase.
Create your public package repository for genuine releases and complete its namespace, description, licence and source/homepage metadata.
Publish a genuine iOS or macOS your tool SDK and set homepage/source URLs in its podspec.
After releasing a genuinely Django-relevant open-source component, sign in and add its GitHub or GitLab repository and accurate project links.
Publish your genuine versioned Nix flake under the correct GitHub owner and maintain its README and project links.
Submit your real maintained open-source release with accurate categories and project metadata.
Release a useful Haxe SDK or privacy utility and set haxelib.json's URL to your relevant documentation page.
Publish a genuine browser or desktop your tool utility with screenshots, documentation and an official-site link.
Build your functional Joomla integration and submit a complete listing with an approved download route.
Create your project team, connect verified project accounts, and describe the official website and repository contextually.
Release your reusable -related security or privacy module from a correctly named public GitHub repository.
Search for your tool; submit an accurate profile update or request research coverage with authoritative company data and website.
List your legitimate documented API in the relevant developer category using the normal or Pro review queue.
Build your tool actions as a Raycast extension and publish through the official GitHub PR workflow.
Submit your maintained open-source component for community review.
An eligible active researcher can publish genuine your tool studies, code or datasets and add the official website where appropriate.
Publish and maintain a tested Scoop manifest for your actual portable Windows CLI or app.
Archive your genuine public source repository and add its resulting SWHID permalink to release and citation metadata.
Build a functional privacy, accessibility or security add-on, publish it on Packagist and create its Marketplace product page.
If your tool maker genuinely offers related services, add the project as a detailed portfolio item with role, outcomes, visuals, and permitted project links.
Create your accurate startup profile and complete its product, team, traction and website details.
Publish genuine authored your tool research and add matching project or supporting-material URLs in the paper metadata.
Use an authentic maker profile to publish your portfolio piece containing original images, article, code, video, or audio samples.
Create your public repository and distribute real signed DEB, RPM, npm, Maven, Helm or other supported packages with accurate metadata.
Contact the curator with your maintained self-hostable edition, repository, documentation and project website.
Host your useful open-source SDK, CLI or example project with documentation and a canonical homepage link.
Submit your maintained voice/audio utility with licensing and a clear creator or voice-AI use case.
After publishing a mature security policy and VDP, contact the Secretariat to apply as a signatory to all four principles.
Submit a working AI feature with accurate categorization, pricing, description, and screenshots for quality review.
Build a Homey app only if your tool adds a genuine IoT privacy or local-device workflow; package, test, validate, and submit it for certification.
Host your maintained open-source component with complete README, homepage/source metadata, releases and optional pages.sr.ht docs.
Submit only your specific AI tool with the official site and contact email, not the platform as a generic tools directory.
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.