Plugins
Customize platform behavior without forking core code.
Plugins provide a controlled extension model for teams that need behavior beyond the default platform surface. They are intended to support customer-specific requirements while keeping core platform upgrades manageable.
Extension Areas
Plugin scenarios can include:
- additional integration connectors
- custom automation logic
- reporting exports and transforms
- specialized collectors
- workflow-specific UI enhancements
Why Plugins Over Forking
Forking core code can create long-term maintenance cost and difficult upgrade paths. Plugins provide a cleaner separation so teams can extend capabilities without diverging from upstream platform updates.
Operational Guidance
Use plugins where policy, automation, and built-in APIs do not fully satisfy requirements. Keep extensions scoped and purpose-specific to preserve maintainability.
Organizational Value
For MSP and enterprise teams, plugins enable tailored service delivery while preserving a consistent operational core across customers and environments.
Capabilities
Extension Module Model
Plugins add integrations, custom automation logic, reporting transforms, collectors, and workflow-specific UI.
Non-Forking Extensibility
Extensions are scoped to plugins rather than core code, preserving maintainability and upgrade compatibility.
Purpose-Scoped Design
Plugins satisfy specific gaps where built-in policy, automation, and APIs fall short, avoiding unnecessary bloat.
MSP and Enterprise Adaptability
Plugin model enables tailored service delivery across customers while preserving a consistent operational core.