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.
Implement applicable ACT Rules, execute official test cases, publish the implementation report, join ACT-R CG, and propose your tool as an implementation.
Apply as a company and accurately describe your tool C2PA or content-provenance tools and intended participation.
Add standards-valid CycloneDX support, then submit your structured entry through the official contribution workflow.
Submit one or more free your tool utilities that work without registration.
Publish a genuinely reusable privacy or accessibility lesson on your tool, give it a stable URL and open license, then add its educational metadata to MERLOT.
List your stable API with OpenAPI definitions, clear endpoints, health checks and its official website in the permitted listing field.
Register your tool as an Indian startup, complete its offering profile, and use Product Expo or Startup Connect when relevant.
Create a valid Helm, OPA, Tekton or supported repository for your deployment and add it through the control panel.
Create or claim your tool, add its verified website, product description, sector, founding details, team, and milestones.
Create and verify your complete company page with offerings, target users, location, and canonical website link.
Upload or design your useful privacy report and add contextual external links before public sharing.
Create your original interactive privacy or accessibility guide and add relevant external actions to cited live tools.
Create a useful Godot editor add-on or privacy-safe asset pipeline tool, release it under an accepted license and submit its repository.
Publish your standards-based JavaScript or TypeScript SDK with generated docs, readme and project links.
Create a useful Julia client or data utility, register it in Julia General and provide complete package docs with your source link.
Register your genuine open-source component, complete its project summary and link its official homepage and source repository.
Write and publish a substantial original handbook on local-first privacy, web safety, or accessible-tool engineering, including reproducible examples and relevant your tool references.
Publish your open Privacy Framework mapping, template, tutorial, or implementation tool and submit it for repository review.
Submit individual your tool tools that are free, secure and usable without registration.
Create a sequenced, classroom-ready module on practical browser privacy or accessible web testing, with learner activities, instructor notes, and your relevant resource link.
Build a genuine Kubernetes Operator for your self-hosted service, test its bundle and submit it through Community Operators.
Publish your well-documented public API workspace with runnable collections, examples and the canonical API website.
Publish a secure, documented container for your open service and add its official site in the repository description or README where supported.
Package a genuinely useful open model or reproducible AI utility, publish it publicly with examples and cite your related documentation naturally.
Make your tool generate or consume valid SPDX, document validation, then file the requested supplier-information issue with its canonical URL.
Search for your tool, verify ownership with official-domain OTP, and claim or request an accurate privacy/security/AI profile.
Submit your tool as a live security, productivity or founder utility.
Submit a sharp founder-authored opinion based on real privacy or security evidence discovered while building your tool.
Publish your real privacy, redaction, or local-AI demo Space and add your canonical URL in its README/metadata.
First publish a fresh, human-authored accessibility case study or tutorial with real lessons and disabled-user perspective where available, then suggest that single article by email.
Launch a human-reviewed Privacy & Accessibility Field Notes newsletter with original experiments, implementation lessons, and contextually relevant links to your tool resources.
Email your strongest developer-focused feature with a self-service demo, documentation, privacy model, and concise reason it is novel.
Build a maintained Craft CMS plugin for your genuine workflow, publish its code and documentation, then submit a complete store listing.
Propose a text-based, interactive course on web privacy, security headers, local-first tools, or accessible frontend testing, with practical code exercises and clear outcomes.
Send a concise exclusive angle on your new security feature, dataset, vulnerability study, or expert commentary.
Import public your tool developer documentation, add the build config and expose versioned, searchable docs with canonical project links.
Pitch a vendor-neutral security article using original your tool tests, threat-model findings, or privacy research.
Submit your tool with homepage URL, privacy-first positioning, logo, screenshots and accurate pricing.
Pitch a short, beginner-friendly, human-authored accessibility post through an issue, or submit one established free your tool accessibility resource under the correct Resources category.
Submit a useful AI privacy, local processing, prompt-security, or responsible-tooling tutorial with reproducible examples.
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.