1,432 places to submit your product

Publish an open-source Sensu check/handler for your tool, create GitHub releases and bonsai.yml, then register it with description and tags.

Upload an original conference-quality PDF deck explaining privacy-safe tooling or accessibility testing, with a useful description, correct category, references, and an honest profile link.

Create a useful StackStorm integration or automation pack for your workflow, then submit it through the official Exchange Incubator pull-request process.

Join a relevant chapter, complete the founder profile, attend suitable events, and share your tool only in genuine networking context.

Create an authentic founder profile, add your tool as a startup page and include verified website/social links.

Publish an original dashboard using public your tool benchmark or ecosystem data and add an appropriate project permalink in workbook details.

Add your tool’s real company, founder, and team structure with website and role details to create a trustworthy organization profile.

Create your product page for discovery, comparison, and reviews.

Build a production-quality Traefik middleware plugin for your privacy or security use case and publish it to the public catalog.

Build a TYPO3 backend extension for selected content or media PII, metadata, and accessibility checks.

Create your Umbraco integration package and point its NuGet project URL plus documentation to your tool.

Register your concrete ongoing initiative with measurable milestones, dates, resources, SDG targets, partners and website evidence.

Build and publish a real Crossplane provider, function, configuration or add-on that integrates your capability and exposes accurate project documentation.

Build a production Webex integration or bot for deliberate sharing of your tool checklists or sanitized files, then submit its branded App Hub profile.

Build a tool that genuinely interacts with Wikimedia, publish accurate toolinfo.json metadata, and register it through Toolhub UI, crawler, or API.

Package your reproducible privacy or redaction workflow, join or create a team, and register it with rich metadata and source links.

Submit your tool as a developer or productivity tool for editorial launch coverage.

Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.

Build an OAuth Asana component that launches your audit or attaches a generated report, then submit complete company and support details.

Claim and verify your tool’s legitimate business entity or location and keep name, address, phone, and website consistent.

If your tool ships a legitimate genomics or bioinformatics utility, package it for R with complete vignettes and submit it for review.

Build a Bitrise Step that runs your tool secret, privacy, or accessibility checks on explicitly chosen build artifacts.

Build a practical Blender add-on for media privacy, metadata or workflow automation and upload its tested extension package with documentation.

Submit your tool with a clear business use case, logo and optional demo video.

Build your useful privacy or security Caddy module, publish the Go package, then register it for module docs and custom builds.

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.

Package your genuine Windows desktop or CLI release and set project, documentation and package-source URLs.

Publish your tested public orb for privacy, secret, or document-safety checks with a homepage URL and usage examples.

Package a secure self-hosted your app for Cloudron, publish its version catalog and documentation, then request inclusion in Community Apps.

Build a current CodeMeta validator, privacy linter, or integration and propose inclusion through the official website repository.

Publish a useful C/C++ SDK or client for your API and contribute its tested recipe to ConanCenter.

Submit a tested recipe for your real package with upstream homepage, source archive, license and tests.

Build a Kafka Connect source or sink that sends only explicitly selected records to your tool privacy or redaction checks and returns structured results.

Create a real designer profile and publish your original UX/accessibility case study with process artifacts, outcomes, and the official project link.

Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages.

Create a free owner account, submit your tool and manage the approved public listing.

Create a defensive parser, scenario, or collection for your real -supported log source, document and test it, then submit it to CrowdSec Hub.

Create a TypeScript or Go module that runs your tool web audits in CI and returns machine-readable JSON/SARIF with useful pass/fail thresholds, then publish it to Daggerverse.