Extension, plugin and integration stores. Real review processes, real distribution. There are 247 in this list, 183 of them free or with a free tier. Every entry shows what it costs, how much work it takes, and links straight to the submission page.
Build a Mendix connector or module that invokes your tool on user-selected records or files and displays structured reports.
Build an OBS privacy guard that detects exposed secrets or sensitive screen regions before streaming.
Build an ONLYOFFICE plugin for document redaction, metadata cleanup, or secret scanning.
Create the product in PitchGround's vendor dashboard and prepare a tested redemption, onboarding, documentation, and support flow.
Build a Sentry integration that detects PII or credentials before issue data is exported or shared.
Create a Zendesk app or marketing-only integration for selected-ticket PII and scam checks with your tool support and pricing links.
Build a Zoho extension for document privacy, text cleanup, or data-export checks and submit its support, policy, guide, and website links.
Create a genuine founder expert profile with your tool website, topics, bio, and real media appearances so relevant hosts can invite you.
Build your working automation Actor, publish it to the Store and include contextual project/documentation 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.
Build your functional Joomla integration and submit a complete listing with an approved download route.
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.
Build your tool actions as a Raycast extension and publish through the official GitHub PR workflow.
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 a functional privacy, accessibility or security add-on, publish it on Packagist and create its Marketplace product page.
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.
Submit a tested your app for compatible Amazon devices with complete descriptions, support links, privacy details and store assets.
Build and openly maintain a Backstage plugin that gives platform teams your real workflow, then announce it through the community-plugins process and meet directory metadata requirements.
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.
Publish privacy/helper extension.
Submit a mature graphical Linux your app with verified metadata, screenshots, homepage and source 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.
Create a useful Grav privacy or security plugin and request inclusion through the official repository issue process.
Publish your Android app through AppGallery Connect with official site, support and privacy URLs.
Apply as the actual designer and publish a manually designed, consistent privacy or accessibility icon pack with an accurate public author profile.