clenttGlossary
Glossary

Plugin platform

Also known as: extensible platform, plugin architecture

Definition
A plugin platform is software architecture in which third-party or first-party features are added through self-contained plugins that register routes, data schemas, automation actions, and AI tools with a host application, instead of being baked into a single monolithic codebase.

Plugin platforms split a product into a host application that owns the core experience (auth, data model, UI shell) and a set of plugins that contribute specific capabilities. Each plugin is independently versioned, registered with the host, and given access to defined extension points.

In GTM software specifically, plugin platforms make it possible to ship a deep integration with Instantly, Apollo, Salesforce, or HubSpot without bloating the core. A plugin contributes its routes, data schemas, automation actions, and (in AI-native products) MCP tools, then turns on or off per tenant based on plan or feature flags.

The tradeoff against monolithic architectures is complexity: plugins need a contract, a registration system, dependency management, and conditional loading. The payoff is faster integration shipping and a clearer path for enterprise customers who need specific tools without forcing the rest of the product to support them.

How Plugin platform relates to Clentt

Clentt is built around a plugin platform. Plugins like Instantly, leads, workflows, and billing are first-party today, with Salesforce, HubSpot, Outreach, and SalesLoft on the roadmap. Each plugin contributes routes, schemas, automation, and MCP tools.

Related terms

Continue