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.
Apply with a code-heavy observability, Node, Ruby, Python, or Elixir tutorial using your real engineering problem as the case study.
Launch a consistent Trustworthy Tools digest that mixes independent sources with occasional relevant your tool research, adding original commentary to every selected link.
Send one current, technically substantive frontend or accessibility article/tool after publishing it, explaining the concrete reader value and disclosing your tool ownership.
First publish a strong JavaScript/browser engineering article or genuinely novel developer utility, then reply to a current issue with one concise, disclosed editorial tip.
Create company page and publish case-study posts.
Publish original, text-first notes about building local-only privacy and accessibility tools, with restrained links to your relevant live implementation.
Submit your founder-written product or privacy case study with concrete decisions, evidence, failures, and lessons for product practitioners.
Use your tool or founder social-web identity to publish original technical/privacy articles with relevant references.
Create your original engineering field-notes publication with human-approved privacy, accessibility, and local-first essays rather than republished marketing copy.
Create your publication or original Japanese engineering article with reproducible examples and contextual links to source or documentation.
Create your genuine publication and post substantial product research, tutorials or engineering notes.
Create a structured open handbook on digital privacy or accessibility with reproducible your tool labs.
Create a public searchable board that teaches a privacy workflow and links to supporting standards, guides, and relevant your tool utilities.
Build and test a Particle Device OS privacy, local-processing, or credential-safety library with examples, license, README, and repository URL, then publish it via the CLI.
Create a structured collection about privacy-preserving web utilities and mix selected your tool pages with respected references.
Submit only original, deep security research or a durable technical guide with reproducible evidence; your tool may be mentioned solely as the research implementation when material.
Apply as an author and publish original privacy, security or accessibility articles with contextual your tool references.
Upload your original research-backed guide and reference relevant tools naturally in the document.
Create a truthful author account and submit your substantive privacy, security or accessibility working paper with legitimate citations.
Publish a public Webmix of trustworthy privacy resources with clearly labeled your tool tiles among independent sources.
Create a useful public learning list with annotations about privacy, accessibility, and scam prevention, placing relevant your tool resources beside independent references.
Propose a vendor-neutral, reproducible cloud-native security tutorial or case study, then write it in Markdown and submit the draft by pull request after community discussion.
If the maker qualifies as a mentor, build a credible technical profile and publish a useful privacy or browser-safety tutorial.
Publish your original privacy or accessibility guide and add contextual clickable links within the document.
Post technical/product story with canonical link.
Convert your original guide into a public flipbook and add contextual links or web embeds for cited tools and resources.
Curate a public online-privacy topic page and add expert notes to a diverse mix of industry sources and your tool guides.
Create a developer portfolio and publish your original build story or project showcase.
Upload a useful original presentation on privacy, accessibility, or tool workflows with your natural reference.
Publish an original, useful privacy or digital-safety guide and mention your resource only when it directly supports the guidance.
Pitch/write article about privacy-first browser tools.
Apply with a genuine technical portfolio and propose an original mobile privacy tutorial aligned with Kodeco's listed subject areas.
Publish founder/productivity article linking your tool.
Build a focused public portfolio for your real designer/team and publish one detailed product, privacy, or accessibility design case study with the project link.
Join the free guest-request emails and pitch only relevant shows with a useful privacy, security, accessibility, or tooling angle.
Pitch an original Python privacy, document-safety, or local-processing tutorial based on real your tool engineering lessons.
Publish an original, media-rich tutorial or founder case study with useful screenshots and your contextual reference, using a complete real profile.
Publish your original guide or annual privacy report and add useful contextual website links through the Hotspot Editor.
Create official your tool update/tutorial blog if needed.
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.