Plugin system
The plugin system is a planned mechanism for extending Gateway with integrations and operational modules.
Purpose
Section titled “Purpose”A plugin represents an extension to Gateway’s capabilities. The plugin system will define how extensions attach to the application and interact with its core.
Its intended scope includes integrations with external systems and additional infrastructure-management operations. Specific extension points have not yet been defined.
Architectural role
Section titled “Architectural role”The plugin-loading mechanism belongs to Gateway’s core. It is not a separate plan feature.
A plugin and an external API client serve different integration roles. An external client calls existing Gateway operations through REST API or MCP. A plugin is intended to extend the capabilities of the application itself. Existing integrations do not yet constitute a public plugin-system contract.
Implementation state
Section titled “Implementation state”Plugin loading and management are not implemented. The package format, core interfaces, permission model, and compatibility rules remain under design. An SDK and development and installation instructions will follow the definition of these contracts.
Integrations with current Gateway versions use REST API, OAuth, and MCP.