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 individual your tool tools that are free, secure and usable without registration.
Make your tool generate or consume valid SPDX, document validation, then file the requested supplier-information issue with its canonical URL.
Create a vendor account and submit your tool under the closest B2B software categories with an accurate feature summary.
Submit the production web app, then verify domain ownership to manage its official listing, assets, and analytics.
Submit your tool with a clear business use case, logo and optional demo video.
Build a current CodeMeta validator, privacy linter, or integration and propose inclusion through the official website repository.
Build and verify your Discord app, then enable Discovery in the Developer Portal.
Publish your containerized research workflow or tool using CWL, WDL, Nextflow, Galaxy, or a supported notebook descriptor.
Apply with a signed, downloadable open-source or qualifying freeware build that needs reliable binary hosting, malware scanning, and a public project page.
Create your company profile using your official email.
Create a vendor account and submit accurate your tool features, logo and pricing.
Propose eligible your tool client-side or offline-first tools to the public directory with accurate site and source links.
Submit your tool as a polished tool website with its strongest public page and a concise explanation of the design system.
Submit your mature privacy component for technical and security review.
Suggest your tool and complete its B2B software profile.
Post only a self-contained initial announcement of a substantial open-source defensive tool, a major update, or a properly coordinated OSS vulnerability disclosure.
Contact PeerSpot with your tool enterprise use cases and real-customer evidence to request inclusion.
Submit one mature privacy tool, disclose ownership, publish its exact threat model and limitations, and engage transparently with the community review.
Create your real OSPO function or a tool that materially supports OSPO work, then contribute the logo and canonical URL by issue or pull request.
Email your complete listing with a concise description, URL, tags, pricing, logo, screenshots and real features.
Build a reusable Typst privacy, accessibility, or document-checking package with a valid manifest, docs, examples, and tests, then submit it to the official packages repository.
Publish your genuine open dataset, benchmark, software release, poster, or reproducible research artifact and connect its related identifier to your tool.
Register as your tool vendor and add its software/service profile.
If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.
Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Discuss your substantive -backed research-software quality task or resource with the Editorial Board, then contribute through its approved workflow.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
Deposit your research-level open-source component or related preprint/report with accurate project and source links.
If your tool ships a macOS CLI or desktop helper, create a maintained tap with a real release, version, checksum, and official homepage metadata.
Archive your authentic release, manual or research artifact with accurate metadata and official source URL.
If your tool releases a suitable open-source Android app, request inclusion with public source, tagged APK releases, Fastlane metadata and website links.
Package a complete computational privacy or accessibility learning module and submit its reusable artifact plus Markdown paper.
Submit your tool product, website, owner, and category information.
Submit only your substantive free-software component that runs primarily on free systems and needs authentic Savannah project hosting and collaboration.
Register your tool and complete the product, company, and category fields.
Suggest one mature your tool utility through the official Codeberg issue path only if it is an easy-to-use, privacy-respecting replacement for a clearly identified invasive service.
Contribute a substantive accessibility role template, translation or toolkit improvement with useful source attribution.
Build your Trello Power-Up, register it, sign the developer agreement, and submit it.
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.