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.
Submit your concise profile with its best differentiating utilities.
Create your truthful /founder profile or content page and add the website link where allowed.
Have a qualified founder or senior team member apply as a privacy, accessibility, product, or engineering mentor and add your tool only as truthful experience/personal-site evidence.
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.
Submit one genuinely AI-powered your tool route with its free-access details, official URL, privacy terms and relationship disclosure.
Contribute a working collector or alert integration for measurable your tool service/privacy signals with metadata and documentation.
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.
Develop a safe, useful Nmap NSE script related to your security check and include accurate author or homepage metadata.
Use ORCID to publish genuine research stages—problem, method, data or analysis—with contextual your tool code/data links.
Create a maintained Omeka S module for collection metadata privacy, accessibility or link auditing, package it correctly and register the add-on with project and author links.
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 a rigorous structured comparison of published privacy, redaction, or accessibility studies and include your tool only when supported by research.
Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.
Open-source your component, then add its website and repositories through the official oss-directory PR.
Build a secure OpenCTI connector that imports or exports your legitimate -supported CTI workflow, add tests and documentation, and contribute it for library integration.
Publish an open-source Lua/OpenResty package that integrates your privacy or security workflow and includes honest package metadata.
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.
Create a public reproducibility project for your tool research, datasets, test methods, or privacy benchmarks and link the genuine project/site.
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.
Create a public searchable board that teaches a privacy workflow and links to supporting standards, guides, and relevant your tool utilities.
Build and test a Particle Device OS privacy, local-processing, or credential-safety library with examples, license, README, and repository URL, then publish it via the CLI.
Create a structured collection about privacy-preserving web utilities and mix selected your tool pages with respected references.
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.
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.
Build a working mini-project showing your browser-side feature and publish its indexed share page with useful documentation.
Create a public case-study portfolio and add your tool with screenshots, live demo and build rationale.
Submit your complete launch profile, then answer relevant discussions authentically.
Create high-confidence defensive templates for authorized checks of privacy leaks or misconfigurations, include safe matchers and test evidence, then submit them for review.
Create your maintained exporter or native Prometheus metrics integration and submit it to the official exporters list.
Apply as an author and publish original privacy, security or accessibility articles with contextual your tool references.
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.
Build and test a Puppet module for supported your tool setup or security policy, complete metadata.json, package it, and publish through a Forge account.
Post to relevant subs with context: SideProject, SaaS, webdev.
After your tool has eligible ReliefWeb content, request publishing access and submit humanitarian reports or training from verified owned URLs.
Create your reproducible evaluation project with code, data connectors, environment, narrative, and a public session launcher.
Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.
Submit your tool with its official URL, concise value proposition, category, logo and only currently working capabilities.
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.