1,432 places to submit your product

Implement applicable ACT Rules, execute official test cases, publish the implementation report, join ACT-R CG, and propose your tool as an implementation.

Create account, wait cooldown if new, submit your tool as platform alternative.

Request an Analyst Briefing and complete the company survey with product, customer, growth, funding, and market evidence.

Apply as a company and accurately describe your tool C2PA or content-provenance tools and intended participation.

Complete the current CAIQ or AI-CAIQ truthfully and submit your tool real cloud service to the STAR Registry.

Add standards-valid CycloneDX support, then submit your structured entry through the official contribution workflow.

Submit one or more free your tool utilities that work without registration.

Deploy your maintained MCP server from GitHub, Docker, npm, or PyPI, verify maintainer ownership, and switch it public only after production testing.

Publish a genuinely reusable privacy or accessibility lesson on your tool, give it a stable URL and open license, then add its educational metadata to MERLOT.

Open-source your well-scoped component, document its governance, tests, security process, and complete the passing-badge self-assessment.

Create your public workspace with sanitized API collections, examples, documentation, and a canonical homepage link on the publisher profile.

Launch your platform first; prepare maker comment and assets.

List your stable API with OpenAPI definitions, clear endpoints, health checks and its official website in the permitted listing field.

Submit platform, add competitor alternatives, verify domain email.

Register your tool as an Indian startup, complete its offering profile, and use Product Expo or Startup Connect when relevant.

Publish a genuine hosted, external, or stdio MCP server exposing a small set of consent-based your tool utilities with complete metadata and documentation.

Use the official Register flow and build your verified company profile if Tamil Nadu startup rules are met.

Submit the company website and concise product, market, founder, funding, and traction details for analyst review.

Build and test your useful piece with real actions, publish the package under a unique organization scope, and maintain version compatibility.

Build a privacy-safe macOS Alfred workflow that opens or runs useful your tool actions, publish it on the forum, gather feedback, and seek Gallery inclusion.

Build a useful Anki privacy, study-safety, or accessibility add-on, package it as .ankiaddon, and upload it through AnkiWeb.

Create a tested Ansible collection for supported your tool deployment or audit automation, complete galaxy.yml, version it, and publish with a Galaxy token.

Create your real Airflow provider with hooks/operators and documentation metadata, publish it, then add it to Airflow’s Ecosystem page by PR.

Recommend your official API with its documentation URL, concise Markdown description, category, and technical details.

When your tool exposes a stable public API, host an official OpenAPI definition at a permanent URL and submit it with accurate ownership, category, logo, and metadata.

Submit your tool once with its strongest free-use case, correct category, concise copy, and product URL.

Submit your mature self-hosted edition using the required YAML entry and canonical website/source links.

Build a pipeline plugin that runs your tool checks on selected artifacts and posts configurable pass, warn, or fail annotations.

List product under software categories.

Create a transparent human profile and publish a beginner-friendly build log or tutorial showing how one your tool privacy utility works and what tradeoffs it has.

Build an original interactive demo of your utility, document the use case in Pen Details, and add your tool as one of the public profile links.

Publish a small open demo that explains one your tool algorithm or UI pattern and add the product website to the founder profile links.

Create a complete founder and startup profile for your tool and participate in relevant founder discussions or connection requests.

Submit a genuine international cyber-capacity-building project, tool, publication or webinar with evidence and a live resource URL.

Complete the founder's developer profile, add your tool as real project experience, and publish useful privacy or security engineering posts with contextual links.

Build your privacy or security field plugin, publish the npm package, and use your tool as its homepage and support site.

Publish your genuine Directus extension to npm and complete author, documentation, support, and website metadata.

Build a DokuWiki privacy, redaction, accessibility, or secure-export plugin, publish its code and create the canonical plugin page used by the extension directory.

Publish a functional Eclipse plugin for your developer use case, then create a complete marketplace listing with official support and source links.

After open-sourcing a maintained component, submit the TOML project file and website through GitHub PR.