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.
Free, low effort, high priority. No account debris, no paid tier.
act-rules.github.io
alternativeto.net
cbinsights.com
contentauthenticity.org
cloudsecurityalliance.org
cyclonedx.org
Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.
Submit your specific AI-powered utility with its official URL, category and a factual description for editorial review.
Create and fully test your Docker Compose service template, add metadata, logo, and documentation, then submit it to Coolify's next branch.
Apply as a designer and publish an original template, icon pack or printable that genuinely complements your workflow.
Apply with a strong portfolio and sell your original -compatible template or design kit, using permitted shop branding and product documentation.
Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.
Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
Participate as a real developer with original lessons and honest build stories; reference your tool only if a specific discussion genuinely calls for the working example.
Sign in with GitHub or Google and add your tool as a real portfolio project with tech stack.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Use a real developer profile and contribute tested solutions on Discourse integrations, accessibility, or privacy only when the team has genuine implementation experience.
If your tool documentation genuinely runs on Docusaurus, add the polished docs site through the official showcase discussion.
Build your Ecwid app, propose it, sign the partner agreement, and submit it for review with website and support links.
Create a structured open handbook on digital privacy or accessibility with reproducible your tool labs.
Register a substantive life-science privacy, medical-data de-identification, or research-data training resource hosted by your tool.
Create a genuinely useful package of tested security-header, HTML-meta, JSON-LD and webhook snippets with your tool validation examples, then submit it to the official Hub.
Discuss your substantive -backed research-software quality task or resource with the Editorial Board, then contribute through its approved workflow.
Submit your genuine -maintained database, reusable reporting standard, or data policy with complete stewardship metadata.
Create a COPR project, build maintained RPMs and add your official homepage and package documentation.
Publish privacy/helper extension.
Submit a mature graphical Linux your app with verified metadata, screenshots, homepage and source links.
Build an open-source FreeCAD privacy/metadata or document-cleanup workbench, add package.xml metadata, and submit it to the curated Addons index.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
Publish a substantive Glide template for privacy-safe records, evidence organization, or accessibility audits and link its your tool documentation where permitted.
Create a narrowly useful GNOME Shell extension, provide metadata and homepage or source information, and submit it for review.
Join a working group and contribute a substantive building-block specification, use case, reference implementation or new proposal.
Ship a genuinely useful Gradle plugin for your developer check such as secret, licence, or configuration auditing; publish with your tool documentation and support URLs.
Build a GRASS GIS add-on for location anonymization, sensitive-zone generalization, or privacy-safe geospatial export, include docs and tests, then submit it to the official add-ons repository.
Create a useful Grav privacy or security plugin and request inclusion through the official repository issue process.
Apply as a startup with your tool website, category, location, description and product details.
Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.
Deposit your research-level open-source component or related preprint/report with accurate project and source links.
Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.
Register as source for B2B content quote opportunities.
If your tool ships a macOS CLI or desktop helper, create a maintained tap with a real release, version, checksum, and official homepage metadata.
After releasing your real CLI or native app, submit a tested formula or cask with its canonical homepage.
Publish your Android app through AppGallery Connect with official site, support and privacy URLs.
Join an approved organization and publish a documented humanitarian privacy/safety dataset with licence and responsible-access settings.
Apply as the actual designer and publish a manually designed, consistent privacy or accessibility icon pack with an accurate public author profile.
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.