1,432 places to submit your product

Build your useful Strapi plugin and submit its package, repository, documentation, and your tool support URL.

Deploy your educational data or AI demo from a public GitHub repository and include a useful link to the full tool or documentation.

Launch your tool with original copy, screenshots and maker details; use the free reviewed listing.

Submit a complete India-relevant product profile with accurate founder information, category, website and launch assets.

Publish your real OpenAPI definition publicly with an accurate description and external documentation URL.

Add a public Swift package with Package.swift, semantic-version tags, documentation and your homepage link.

Create the real designer/founder profile and add your original product-design or accessibility project with collaborators, role, process, and official URL.

Build a legitimate Thunderbird MailExtension, complete its add-on page and submit it through the Developer Hub.

Create your real OSPO function or a tool that materially supports OSPO work, then contribute the logo and canonical URL by issue or pull request.

Email your complete listing with a concise description, URL, tags, pricing, logo, screenshots and real features.

Create your functional ToolJet plugin with clear documentation and tests, then submit it to the marketplace through the official contribution flow.

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

Create a founder or developer portfolio and publish your build case study with screenshots, process, outcomes, and the live project link.

Build a reusable Typst privacy, accessibility, or document-checking package with a valid manifest, docs, examples, and tests, then submit it to the official packages repository.

Package your self-hosted privacy utility for umbrelOS, add required metadata and assets, test it on supported hardware, and submit the official app PR.

Build a polished Unity editor utility or SDK for your relevant service and submit it with demos, documentation and support details.

Build your Vercel integration, distribute its page, gain adoption, then apply for Marketplace visibility.

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

Develop a neutral, sourced learning project about privacy, accessibility, or online-scam literacy and cite your tool only in relevant exercises.

Publish your reusable -backed privacy or security script, flow, app, or resource type for the public Windmill Hub.

Build a genuine founder or designer profile and publish your detailed UX, accessibility, or privacy-design case study with accurate role and process credits.

Build your accounting/privacy integration, validate it with customers, certify and publish it in the Xero App Store.

Create tutorials for top your tool tools with links.

Package your free-software self-hosted deployment, implement reliable install, upgrade, backup and restore operations, then submit it to the official app catalog.

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

Build a defensive Zeek script or plugin for privacy-safe log inspection, include zkg metadata and tests, then register it in the default Zeek package source.

Publish your genuine open dataset, benchmark, software release, poster, or reproducible research artifact and connect its related identifier to your tool.

Build a minimal-scope Zoom app that sends selected meeting content to your explicit privacy or redaction workflow and links its support, privacy, and documentation pages.

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.

Apply only if the founder or team member has real design/engineering leadership experience and intends to provide genuine mentoring, then add an accurate personal website/profile reference.

Submit your public AI-enabled utility with its official URL, correct category, pricing model and an accurate quality-focused description.

Open a pull request for your genuine AI-native component with repository metadata.

Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.

Submit your tool (or its blog/feed where required) under productivity, privacy or developer tools.

Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.

Submit a tested your app for compatible Amazon devices with complete descriptions, support links, privacy details and store assets.

Register as your tool vendor and add its software/service profile.

Publish an original UI/UX visual case study showing your tool interaction design, accessibility states, and design process, with a contextual project URL.

Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.

If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.