Marketplace Bundles¶
Bundles are curated collections of templates and extensions that work together to provide complete solutions for specific use cases. Instead of installing individual components, bundles give you everything you need in a single click.
What's in a Bundle?¶
A bundle typically includes:
- Templates - Pre-configured workflows, boards, dashboards, and automations
- Extensions - Integrations with external services (email, Slack, GitHub, etc.)
- Analytics - Dashboard definitions for tracking metrics
graph TB
subgraph Bundle["Business Operations Suite"]
direction TB
subgraph Required["Required Templates"]
T1[Support]
T2[Sales]
T3[Engineering]
end
subgraph Optional["Optional Templates"]
T4[Marketing]
T5[Partners]
T6[Product]
T7[Finance]
T8[Legal]
end
subgraph Extensions["Extensions"]
E1[Email]
E2[Slack]
E3[GitHub]
end
end
T1 --> E1
T1 --> E2
T2 --> E1
T3 --> E3
T3 --> E2
Required vs Optional Components¶
Bundles distinguish between required and optional components:
| Type | Description | Installation |
|---|---|---|
| Required Templates | Core functionality that defines the bundle's purpose | Always installed |
| Optional Templates | Additional capabilities that extend the bundle | User selects during install |
| Extensions | External integrations needed by templates | Installed based on selected templates |
Example: Business Operations Suite¶
The Business Operations Suite includes:
Required Templates:
support- Customer support ticketing with SLA trackingsales- Sales pipeline and lead managementengineering- Bug tracking and incident response
Optional Templates:
marketing- Campaign managementpartners- Partner relationship managementproduct- Feature request and roadmap trackingfinance- Expense approval workflowslegal- Contract management and GDPR compliance
Installing a Bundle¶
From the Marketplace¶
- Navigate to Marketplace > Bundles
- Select a bundle to view details
- Review the dependency graph showing required and optional components
- Click Install Bundle
- Select which optional templates to include
- Configure any required extension settings
- Choose target projects for each template
From the CLI¶
# List available bundles
kiket marketplace bundles
# View bundle details
kiket marketplace bundle business_ops
# Install with all optional templates
kiket marketplace install business_ops --all-optional
# Install with specific optional templates
kiket marketplace install business_ops --include marketing,finance
# Install required only
kiket marketplace install business_ops --required-only
Bundle YAML Structure¶
Bundles are defined in YAML files with the following structure:
id: business_ops
name: Business Operations Suite
description: |
Complete business operations suite for running a SaaS company.
version: "1.0.0"
category: suite
tags:
- business-operations
- saas
featured: true
contents:
templates:
- support
- sales
- engineering
- marketing
- partners
- product
- finance
- legal
extensions:
- dev.kiket.ext.email
- dev.kiket.ext.slack
- dev.kiket.ext.github
analytics:
- operations_overview
# Dependency classification
required_templates:
- support
- sales
- engineering
optional_templates:
- marketing
- partners
- product
- finance
- legal
requirements:
min_plan: professional
maintainer: Kiket
license: MIT
Bundle Categories¶
| Category | Description | Examples |
|---|---|---|
suite |
Comprehensive multi-department solutions | Business Operations Suite |
project_management |
Project and task management | Scrum Bundle, Kanban Bundle |
operations |
Operational workflows | Customer Support Bundle |
marketing |
Marketing and campaigns | Marketing Suite |
development |
Software development | Developer Toolkit |
productivity |
General productivity | Productivity Bundle |
Viewing Dependencies¶
The bundle detail page shows a visual dependency graph:
- Blue nodes - Required templates (always installed)
- Gray nodes - Optional templates (user selects)
- Green nodes - Extensions
- Solid lines - Direct dependencies
- Dashed lines - Optional dependencies
This visualization helps you understand:
- Which templates depend on which extensions
- Which components are required vs optional
- The relationships between different parts of the bundle
Plan Requirements¶
Bundles may require a minimum subscription plan:
| Plan | Available Bundles |
|---|---|
| Free | Basic bundles with free extensions |
| Professional | Most bundles including premium extensions |
| Enterprise | All bundles including enterprise integrations |
Check the bundle's min_plan requirement before installing.
Creating Custom Bundles¶
Organization admins can create custom bundles for internal use:
- Create a YAML file following the bundle schema
- Place it in your organization's configuration repository
- Reference internal or marketplace templates and extensions
- Share with team members via the internal marketplace
See the Configuration as Code guide for details on managing bundle definitions.
Updating Bundles¶
When bundle definitions are updated:
- New templates can be added to existing installations
- Removed templates remain installed but are no longer managed by the bundle
- Extension updates are handled independently
- Version tracking shows which bundle version is installed
To update a bundle installation:
Troubleshooting¶
Bundle installation fails¶
- Check that your plan meets the
min_planrequirement - Verify all required extensions are available
- Ensure you have admin permissions for target projects
Missing dependencies¶
If a template requires an extension that isn't in the bundle:
- Install the extension separately from the marketplace
- Contact the bundle maintainer to request adding the dependency
Conflicts with existing configuration¶
Bundles won't overwrite existing workflows or boards. To reinstall:
- Remove the existing configuration
- Re-run the bundle installation