1,432 places to submit your product

Package a narrow, safe your tool plugin with a public repository, validate it with the Claude plugin validator, and submit it through the in-app directory flow.

Build and test a free Dify plugin for your distinct privacy or file-analysis capability, package it, add a privacy policy, and submit the required pull request.

Create your tool company profile with accurate product, team, media, and website details, then submit it for verification.

Submit as Show HN: your tool - privacy-first toolbox people can try instantly.

Build a maintained Linear integration that sends approved your tool audit findings into issues, then submit its listing and assets.

Create a supported Mattermost plugin or app that scans user-approved text for sensitive data before sharing, with docs and a public issue tracker.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Create a vendor account and submit your tool under the closest B2B software categories with an accurate feature summary.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Submit the production web app, then verify domain ownership to manage its official listing, assets, and analytics.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Submit your tool as useful no-signup online toolbox.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Submit your working AI utility with a clear under-80-character tagline, correct category, pricing model, logo and honest description.

Use the free official flow to submit one genuine your tool AI tool, then claim and maintain it using a matching domain email.

Build a polished Alfred workflow that opens or securely sends selected content to your relevant utility, then submit it through the official Gallery forum flow.

Create a tested Auth0 Action that invokes your relevant privacy or security workflow and submit through the Marketplace Partner Portal.

Build a small founder-written knowledge blog with genuinely useful local-first privacy and file-safety guides.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Create a public digital-privacy magazine, curate reputable third-party resources, and occasionally add strong your tool guides with commentary.

Open-source a meaningful component and prepare a community-focused talk, demo, or joint stand proposal for the next FOSDEM CFP rather than a company sales presentation.

Build a useful Home Assistant privacy or local-security integration, publish stable GitHub releases, pass HACS and Hassfest checks, then request inclusion.

Launch your tool with a unique tagline, screenshots and founder profile linking to your tool.

Run the website and email tests, fix IPv6, DNSSEC, HTTPS, security headers, DMARC/DKIM/SPF, STARTTLS/DANE, and RPKI gaps, then retain a 100% score.

Submit your tool as a polished tool website with its strongest public page and a concise explanation of the design system.

Build a signed Nextcloud app for local document sanitization or privacy checks, publish releases, and maintain App Store compatibility.

Publish @your tool/embed or utility package with homepage.

Submit one mature privacy tool, disclose ownership, publish its exact threat model and limitations, and engage transparently with the community review.

Build a maintained Redmine plugin that creates privacy or security audit tasks, document supported versions, then register it under an authenticated developer account.

Build a valuable public start page of privacy and productivity resources, then submit it to Community Pages after adding your tool selectively.

Create an account and submit your tool with positioning, category, logo and 3–6 accurate tags.

Create or claim your tool company profile and add its official URL, product summary, founders, location, and verified company facts.

Create a developer account, request access, verify ownership, and publish a complete app profile with screenshots and description.

Publish a well-organized privacy-toolkit collection containing authoritative resources plus selected your tool utilities.

Create tutorials for top your tool tools with links.

Create a sandbox-compatible Zed extension for local secret, Unicode, or privacy checks, test it, publish its repository, and submit the registry pull request.