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.
Create your working public integration or reusable Mastra template with repository and documentation for review and cross-listing.
Create a useful npe2 napari plugin for image privacy, metadata inspection or scientific redaction, publish it correctly on PyPI and let the official hub index its project metadata.
Document a real participatory public-decision deployment as a Case, Method or Organization entry with evaluations and project URL.
Create your genuine publication and post substantial product research, tutorials or engineering notes.
Build a ProcessWire admin module for external URL, metadata, accessibility or security audits, register as a module author and submit it to the official directory.
Build a stable open-source RabbitMQ plugin for your legitimate security/privacy workflow and ask the RabbitMQ team to list it.
Request access, then publish your rich research-software page with source, getting-started URL, DOI, contributors, and research mentions.
Publish a substantial open-source Backstage plugin that integrates your tool privacy/security checks, then request inclusion if the directory does not discover it.
Register a stable, genuinely research-used your tool software, service, or database with accurate maintainer and version metadata.
Build a maintained Silverstripe CMS module for your useful privacy, accessibility or URL-audit workflow, publish it with correct Composer metadata and submit it to the public directory.
Publish an original educational 3D asset connected to your real tutorial, with accurate credits and a contextual project link in the description.
Add your tool as a SaaS or online service with its official URL.
Build a Python keyword extension that runs useful your tool URL, domain or metadata checks and displays concise results, then submit its public repository through the official form.
Create a founder profile, add your tool as a startup and share authentic milestones or metrics.
Build and upload a genuinely useful Vim privacy or secret-checking plugin with your tool documentation and a relevant project link.
Build a WebThings adapter, notifier, or interface extension for local privacy or device-risk controls, follow the add-on APIs, test on Gateway 2.x, and publish it to the directory.
Build and test a Slicer extension for medical-image de-identification, metadata inspection or privacy validation, then add its .s4ext metadata to ExtensionIndex by pull request.
Apply only if the founder or team member has real design/engineering leadership experience and intends to provide genuine mentoring, then add an accurate personal website/profile reference.
Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.
Register as your tool vendor and add its software/service profile.
Publish an original UI/UX visual case study showing your tool interaction design, accessibility states, and design process, with a contextual project URL.
Build a deployable edge privacy utility or reusable block, add balena.yml metadata, public source, configuration and multi-device tests, then publish it on balenaHub.
Package your maintained self-hosted deployment as a Juju charm with canonical documentation, source, and support links.
Build a maintained Cinnamon applet that launches or monitors your useful local privacy workflow and submit it by pull request.
Create an age-appropriate digital-citizenship or privacy FlexBook chapter with practical your tool exercises.
Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.
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.
Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.
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.
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.
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.