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 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.
Answer relevant questions genuinely; profile links to your tool.
Release a real Racket privacy utility or your tool client and register its public package source and documentation.
Create your truthful /founder profile or content page and add the website link where allowed.
Create your truthful /founder profile or content page and add the website link where allowed.
Create your truthful /founder profile or content page and add the website link where allowed.
Submit your tool with the verification badge or use the no-badge paid option.
Create visual/tool tip microblog with canonical links.
Host real build sessions or tool demos and add your tool to the channel About/social links.
Create an account and submit your tool with URL, category and concise product copy.
Submit business/site listing if form active.
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.
Create official your tool update/tutorial blog if needed.
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.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Only submit if you build a Bubble-related app/template.
Join with an authentic verified builder account and showcase your tool milestones and assets.
Create your truthful /founder profile or content page and add the website link where allowed.
Create company listing with website link.
Submit if a commerce-style/tool landing page fits.
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.
Create a genuine LaTeX privacy, redaction or document-safety package and include its exact your tool project homepage in the upload metadata.
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.
Share design/tool launch if genuinely useful.
Publish a useful D client library or privacy utility with accurate homepage and repository metadata in dub.json or dub.sdl.
Submit only after your tool releases a signed Windows desktop utility.
Build the founder/company profile and add accurate your tool links, stage and product details.
Create your truthful /founder profile or content page and add the website link where allowed.
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.
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.