Open Ecosystem

Kiket encourages teams to extend the platform without deploying code into our infrastructure. You control execution, we provide the contract and tooling.

Extension Principles

• Federated hosting – Extensions run on your infrastructure. Kiket only calls your HTTPS endpoints.
• Manifest-driven – Each extension ships with a manifest.yaml describing permissions, triggers, UI surfaces, and configuration fields.
• Scoped access – Every install receives an API key limited to the scopes enumerated in the manifest.
• Event-first – Webhooks deliver lifecycle events (issue created, workflow transitioned, analytics refreshed) so extensions can react in real time.

Sharing & Marketplace

• Publish extensions to the marketplace so other organizations can install them.
• Marketplace metadata includes pricing, documentation links, and support contacts.
• Versioning lets you deprecate older releases while keeping running installations stable.

Internal Tooling

• Private extensions can stay inside your organization, providing custom automations, data pipelines, or UI widgets.
• Use repository precedence to ship shared .kiket/extensions/* manifests so projects inherit standard tooling.

Integration Examples

• Deliver deployment status updates to Slack when the workflow transitions to deploying.
• Sync issue metadata with an internal CMDB when new records are created.
• Attach AI-generated summaries to issues via the REST API.

The open ecosystem ensures you never outgrow Kiket—build the features you need and share them across the community when you are ready.