Marketplace

The marketplace showcases vetted extensions that enhance Kiket. It supports discovery, installation, billing, and reviews.

Browsing

• Filter by category (Automation, Analytics, DevOps, Communication, AI).
• Sort by popularity, rating, or newest.
• Preview permissions, pricing, screenshots, and documentation links before installing.

Extension Installation Flow

1. Choose an extension and click Install.
2. Review requested permissions and scopes.
3. Select projects and repositories that should use the extension.
4. Provide configuration values defined in the manifest.
5. Confirm installation. Kiket issues API keys and registers webhooks.

Workflow Templates

Templates (also called definitions) are pre-built project configurations available in the marketplace. Unlike extensions which provide organization-wide integrations, templates are installed to specific projects.

Template Installation Flow

1. Browse to Marketplace → Templates (or access from project setup)
2. Select a template that fits your methodology (Scrum, Kanban, etc.)
3. Click Use this template and select a project from the dropdown
4. A Workflow Repository is created pointing to the template's GitHub repo
5. The template is synced and configuration is applied automatically
6. Workflows, boards, and dashboards are created in your project

Templates use the same sync mechanism as custom workflow repositories, which means you can re-sync to get updates and track versions.

Quick Start Templates

When creating a new project connected to a GitHub repository without a .kiket/ folder, Kiket displays the Workflow Setup Required page with featured templates. Click Use Template to instantly apply the configuration.

See Definitions Overview for detailed template documentation.

Billing

• Free extensions install instantly.
• Paid extensions display cost breakdown (per user/month, usage-based, or flat fee).
• Charges appear on the organization invoice; revenue shares are distributed to creators.

Product Blueprints

• Blueprint definition files live in config/marketplace/blueprints/*.yml. Each blueprint describes repositories, projects, extensions, pricing, and prerequisites.
• Installing a blueprint:
• Clones the referenced definition repositories and records the version installed.
• Provisions the projects listed in the YAML (workflow templates, analytics dashboards, default GitHub repos) and runs the standard ConfigurationLoader import pass so workflows/boards/prompts are live immediately.
• Enables required extensions and records any missing extensions or secrets so admins can finish configuration via CLI or UI.
• CLI commands (kiket marketplace list|info|install) read the same metadata surfaced by /api/v1/marketplace/products.
• Blueprint YAML fields:
• identifier, version, name, description
• metadata.categories, metadata.pricing, metadata.prerequisites
• metadata.repositories[] (type, path, description)
• metadata.projects[] (key, name, definition_path, repository_url, description)
• metadata.extensions[] (extension_id, name, required, secrets[] { key, description })

Reviews & Ratings

• Organization admins can rate extensions and leave feedback.
• Creators respond to reviews to address feature requests or issues.
• Ratings influence marketplace ranking.

## Security & Compliance - Extensions undergo automated scans (endpoint health, TLS, headers). - Manual review checks data handling, least-privilege permissions, and documentation quality. - Extensions can earn “Verified” badges for providing SOC2/ISO attestations and incident response SLAs.

The marketplace makes it easy to extend Kiket while maintaining trust and transparency across the ecosystem.