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.
Apply as the actual designer and publish a manually designed, consistent privacy or accessibility icon pack with an accurate public author profile.
Publish a genuinely useful KDE or Plasma asset or integration with accurate project and homepage details.
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.
Build a safe MISP import, export, hover, expansion, or workflow module for a legitimate privacy or scam-analysis use case, document it, test it, and submit a PR.
Contribute a working collector or alert integration for measurable your tool service/privacy signals with metadata and documentation.
Build a working OnePageCRM integration and apply for testing, verification and a dedicated marketplace page.
Build a secure OpenCTI connector that imports or exports your legitimate -supported CTI workflow, add tests and documentation, and contribute it for library integration.
Contribute a functional privacy/security integration, dashboard or ingestion-to-visualization content pack through the OpenSearch Catalog workflow.
Package your useful browser feature as an Opera extension and submit it for moderation.
Build a useful ownCloud app that invokes or embeds your privacy, document or URL-audit workflow, code-sign it and publish it through the official marketplace.
Develop an OJS/OMP/OPS plugin for a genuine accessibility, privacy or publication-validation workflow, release it with gallery metadata and submit through PKP's review flow.
Create your maintained exporter or native Prometheus metrics integration and submit it to the official exporters list.
Distribute your Android or Galaxy app and add its official website and support information.
Adapt your privacy-first web utility to Sandstorm's grain model, package and sign the SPK, add complete metadata and tests, then publish it for review.
Build a genuine SMath plugin or reusable worksheet resource and register it for the public Extensions Manager gallery.
Build and test your useful Visual Studio or Azure DevOps extension, then publish it with truthful homepage, repository and overview metadata.
Build an XWiki extension for a useful privacy, accessibility or link-audit workflow, release it as a valid XAR/JAR and publish or import it into the official extension repository.
Build table functions that import, normalize and query your tool report JSON or NDJSON with typed findings, then submit the extension descriptor for central build and distribution.
Publish design asset or privacy checklist template.
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.
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.
Build a production-grade Camel component for your tool APIs and propose it upstream with generated component docs and tests.
Only submit if you build a Bubble-related app/template.
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.
Build a tested Galaxy wrapper for your medical-data privacy or de-identification workflow and publish it in the main ToolShed.
Create a genuine media-metadata privacy or local-safety add-on and submit it to Kodi's official repository.
Build a WASI/LSP Volt that surfaces useful your tool diagnostics for HTML or SEO configuration files, then publish it with the official Volts CLI.
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.
Create a meaningful NWB extension for privacy, provenance, or consent metadata and submit its staged-extension YAML through an official pull request.
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 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.
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.