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.
Create a useful quickstart for monitoring your real deployment, with instrumentation instructions, a working data source, dashboards, alerts, documentation, and a GitHub contribution.
Build a signed Nextcloud app for local document sanitization or privacy checks, publish releases, and maintain App Store compatibility.
Add and test a Nix expression for your genuine release with description, homepage, license and maintainer metadata.
Publish @your tool/embed or utility package with homepage.
Publish a machine-readable privacy, accessibility, or scam-pattern dataset or API and complete its evidence-based public certificate.
Submit your mature privacy component for technical and security review.
Publish your small local-first classifier for privacy, secret detection, or defensive content analysis.
Suggest your tool and complete its B2B software profile.
Build a functional OPA/Rego privacy-policy integration or developer tool, document it, then add its ecosystem entry and logo through the official docs repository.
Create your genuine collective, complete its public profile, and add the official website plus repository/social links.
Submit a complete, openly licensed privacy/digital-safety textbook already used in higher education.
Create an account and submit your tool or its qualifying AI tools.
Publish a free mini-course on privacy, redaction, scam detection, or accessibility with genuine your tool exercises in the curriculum.
Publish a documented, de-identified ML-ready benchmark such as labelled phishing, homograph, or accessibility test cases with provenance and an open license.
Submit your maintained open-source project through Submit a Project.
Run Scorecard on your public component, enable published results, remediate checks, and link the public viewer from repository documentation.
Create a public OBS project and package that builds your tool for supported Linux distributions with upstream links.
Post only a self-contained initial announcement of a substantial open-source defensive tool, a major update, or a properly coordinated OSS vulnerability disclosure.
Publish a genuinely useful free privacy checklist, redaction template, or safety workbook that complements your tool and has standalone value.
Contact PeerSpot with your tool enterprise use cases and real-customer evidence to request inclusion.
Submit your valid public podcast feed and keep website and episode-link metadata accurate.
Claim your genuine show, verify ownership, and complete its official website and creator details.
Submit one mature privacy tool, disclose ownership, publish its exact threat model and limitations, and engage transparently with the community review.
Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.
Publish your reproducible testing, privacy-analysis or accessibility-evaluation method and cite relevant project resources.
Build a QGIS plugin that checks selected layers or exports for sensitive coordinates and metadata, then creates a safer copy.
Create a public Quarto extension for privacy, accessibility, or document checks with documentation, examples, and a license, then propose it for listing.
Publish your maintained open-source service template with safe variables, health checks, documentation and a demo.
Publish a carefully annotated collection of trustworthy privacy, accessibility, and safety resources, including only your tool pages that genuinely fit each section.
Build a maintained Redmine plugin that creates privacy or security audit tasks, document supported versions, then register it under an authenticated developer account.
Make your real public repository REUSE-compliant, register its Git URL, and link the resulting compliance page from project docs.
Package your legitimate Ruby client or utility and add homepage and source metadata before pushing the gem.
Create and locally test your Runtipi app with config, Compose metadata, safe secrets, screenshots, documentation, backups, and update behavior, then submit it.
Build your Sanity Studio plugin, publish it to npm, and submit it to Sanity Exchange with documentation and support links.
Publish a coherent multimedia field guide on privacy, scam evidence, or accessible documents with cited your tool demonstrations.
Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.
Find an existing question where your specific utility is a genuine option, add it accurately, and document balanced pros and cons.
Publish a public reproducible privacy-safe research workflow with a Snakefile, README, configuration, catalog metadata, and tests.
Ship your installable Linux app or CLI as a snap with a complete store listing and website link.
Build a useful Splunk app or add-on for legitimate your tool security, audit, or operational data; package it with clear documentation, icons, screenshots, release metadata, and support details.
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.