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.
Build a Zoho extension for document privacy, text cleanup, or data-export checks and submit its support, policy, guide, and website links.
Build your useful Budibase component or data-source plugin, publish the package or repository, and seek inclusion in community plugin resources.
Build a functional Contao bundle for your site-audit use case, publish tagged releases on Packagist with contao-bundle and manager-plugin metadata, and let the official index discover it.
Build and publish a real fluent-plugin-* RubyGem that redacts/routes privacy-sensitive logs and includes your tool as its project homepage.
Build a functional Jellyfin privacy, metadata-cleanup, or local-safety plugin with a maintained manifest repository, then propose its repository and documentation entry.
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.
Build a stable open-source RabbitMQ plugin for your legitimate security/privacy workflow and ask the RabbitMQ team to list it.
Publish a substantial open-source Backstage plugin that integrates your tool privacy/security checks, then request inclusion if the directory does not discover it.
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.
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.
Build a maintained Cinnamon applet that launches or monitors your useful local privacy workflow and submit it by pull request.
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 your Ecwid app, propose it, sign the partner agreement, and submit it for review with website and support links.
Build an open-source FreeCAD privacy/metadata or document-cleanup workbench, add package.xml metadata, and submit it to the curated Addons index.
Publish a substantive Glide template for privacy-safe records, evidence organization, or accessibility audits and link its your tool documentation where permitted.
Create a narrowly useful GNOME Shell extension, provide metadata and homepage or source information, and submit it for review.
Ship a genuinely useful Gradle plugin for your developer check such as secret, licence, or configuration auditing; publish with your tool documentation and support URLs.
Build a GRASS GIS add-on for location anonymization, sensitive-zone generalization, or privacy-safe geospatial export, include docs and tests, then submit it to the official add-ons repository.
Apply as the actual designer and publish a manually designed, consistent privacy or accessibility icon pack with an accurate public author profile.
Publish a genuinely useful KDE or Plasma asset or integration with accurate project and homepage details.
Build a safe MISP import, export, hover, expansion, or workflow module for a legitimate privacy or scam-analysis use case, document it, test it, and submit a PR.
Contribute a working collector or alert integration for measurable your tool service/privacy signals with metadata and documentation.
Build a secure OpenCTI connector that imports or exports your legitimate -supported CTI workflow, add tests and documentation, and contribute it for library integration.
Contribute a functional privacy/security integration, dashboard or ingestion-to-visualization content pack through the OpenSearch Catalog workflow.
Build a useful ownCloud app that invokes or embeds your privacy, document or URL-audit workflow, code-sign it and publish it through the official marketplace.
Develop an OJS/OMP/OPS plugin for a genuine accessibility, privacy or publication-validation workflow, release it with gallery metadata and submit through PKP's review flow.
Create your maintained exporter or native Prometheus metrics integration and submit it to the official exporters list.
Adapt your privacy-first web utility to Sandstorm's grain model, package and sign the SPK, add complete metadata and tests, then publish it for review.
Build a genuine SMath plugin or reusable worksheet resource and register it for the public Extensions Manager gallery.
Build an XWiki extension for a useful privacy, accessibility or link-audit workflow, release it as a valid XAR/JAR and publish or import it into the official extension repository.
Join the vendor program and package your tool as a legitimate one-click app or supported SaaS add-on with documentation and website links.
Use Become a Vendor to publish your tool business-software profile.
Build a production-ready PrestaShop module or theme and submit its technical package, product page and support links.
Create a scoped ServiceNow application that performs your real workflow for selected records or attachments and submit it through the Store.
Package your privacy, file-safety, or accessibility assistant for a supported Autodesk product.
Build a robust Concrete CMS package for your privacy, accessibility or site-audit workflow, package it correctly and submit the add-on through the official marketplace manager.
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.