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 a real source connector that lets consenting users export appropriate your tool data, provide tests and documentation, and contribute it to Airbyte's public connector catalog.
Publish a stable, documented your tool API and apply as a provider with examples, uptime, support, and honest pricing.
Build an OAuth Asana component that launches your audit or attaches a generated report, then submit complete company and support details.
Create a tested Auth0 Action that invokes your relevant privacy or security workflow and submit through the Marketplace Partner Portal.
Build a practical Blender add-on for media privacy, metadata or workflow automation and upload its tested extension package with documentation.
Build a Canva app that sends chosen design assets to your accessibility, metadata, or privacy check and returns useful results inside Canva.
Package your useful service/security monitor as an MKP, create an account, and upload its description, icon and first version.
Build a Kafka Connect source or sink that sends only explicitly selected records to your tool privacy or redaction checks and returns structured results.
Apply as a Datadog Technology Partner and build a production-grade integration that sends meaningful your tool telemetry, includes dashboards and documentation, and is useful to shared customers.
Build an Elastic package that ingests legitimate your tool logs, metrics, or traces and supplies mappings, pipelines, dashboards, documentation, sample data, and automated tests.
Build a real Falco source or field-extraction plugin, publish a clear README and fields, add it to registry.yaml, sign commits, and submit the registry PR.
Build your useful privacy-preserving extension, submit a signed build, and provide honest homepage, permissions and privacy disclosures.
Submit a high-quality reusable template, page, component or permitted custom-code asset related to your workflow.
Build your real documentation/privacy integration, publish it as public, test it, then submit for GitBook review.
Build a panel, data-source or app plugin, validate and package it, then submit it with project links and test data.
Build a useful Home Assistant privacy or local-security integration, publish stable GitHub releases, pass HACS and Hassfest checks, then request inclusion.
Package your installable Haystack component, provide examples and docs, then submit it to the Haystack integrations repository.
Package an installable Haystack component or tool for your tool read-only URL, security and metadata checks, then submit a draft integration page with runnable examples.
Build and maintain a genuinely useful Home Assistant integration for your mature service, including the required Python client library, tests, documentation, and a focused Core pull request.
Publish a real Icinga-compatible check, module or integration and synchronize its public Git repository, releases and README.
Apply with a real designer portfolio and publish your original -themed privacy, safety, accessibility, icon, illustration, 3D, or Lottie pack.
Join the partner platform and create your secure service with genuinely useful triggers, queries, and actions, pass endpoint tests and review, then publish helpful Applets for real user workflows.
Build an Intercom app for intentional conversation privacy scanning or sanitized export generation and include your clear install or learn-more URL.
Build a genuine Joomla extension, create a developer profile and submit a complete listing with the official project website.
Build and host a useful Jotform widget, register it with full documentation and send it for approval.
Implement Java tasks or triggers for submitting your tool audits and fetching structured results, complete with typed properties, examples, tests and generated documentation.
Build your standalone integration package with tests and submit the required LangChain documentation PR.
Create a working Nagios check or addon for your API/privacy-health signal, register, and submit the project with source and website links.
Build and test a Netlify extension, publish it publicly, then submit it for review and directory listing.
Build a signed Nextcloud app for local document sanitization or privacy checks, publish releases, and maintain App Store compatibility.
Build a QGIS plugin that checks selected layers or exports for sensitive coordinates and metadata, then creates a safer copy.
Create a public Quarto extension for privacy, accessibility, or document checks with documentation, examples, and a license, then propose it for listing.
Publish your maintained open-source service template with safe variables, health checks, documentation and a demo.
Build a maintained Redmine plugin that creates privacy or security audit tasks, document supported versions, then register it under an authenticated developer account.
Create and locally test your Runtipi app with config, Compose metadata, safe secrets, screenshots, documentation, backups, and update behavior, then submit it.
Build your Sanity Studio plugin, publish it to npm, and submit it to Sanity Exchange with documentation and support links.
Ship your installable Linux app or CLI as a snap with a complete store listing and website link.
Build a useful Splunk app or add-on for legitimate your tool security, audit, or operational data; package it with clear documentation, icons, screenshots, release metadata, and support details.
Submit your accurate profile with its strongest software category, live URL, features, pricing and logo.
Create your factual tool, workflow, or tutorial entry that genuinely serves social-science or humanities researchers.
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.