Plugins. Stay lean. Grow outward.
Mezusphere stays simple at the center: one Warpgate, one Console, one deployment pattern. Plugins let you extend the platform with advanced capabilities when you need them, without re-architecting your stack or adding another vendor.
Why plugins matter
Mezusphere's core promise is simplicity: one platform instead of many vendors, one deployment pattern centered on the Warpgate, one Console for routing, identity, and security.
That simplicity should not be sacrificed when you need more specialized capabilities. Plugins solve that problem. They let Mezusphere stay lean for the common case while giving you a path to advanced capabilities when you truly need them.
Keep the core simple
You don't want a giant enterprise platform on day one. You want the base workflow, Warpgate plus Console, to be clean and understandable. Plugins make advanced capabilities optional, not mandatory.
Extend without re-integration
Instead of buying a separate tool and wiring it into routing, auth, and traffic handling manually, you enable capabilities through Mezusphere. No new vendor integration. No new deployment model.
Support regulated use cases
Some industries need features beyond the mainstream baseline: financial-grade API security, advanced compliance controls, specialized authorization models. Plugins give Mezusphere a path to support those requirements without forcing you to absorb that complexity.
How plugins work
A plugin is a packaged extension that adds a capability to Mezusphere without changing your basic workflow.
1. Deploy as usual
Run your workload with a Warpgate. The deployment model does not change when you add a plugin.
2. Enable in the Console
Browse the plugin catalog, activate the capability, and configure it through Mezusphere's management interface.
3. Applied automatically
Mezusphere applies the plugin capability at the edge, near the workload, or in the control layer, wherever it makes sense. No manual wiring required.
Plugins can operate in three layers of the platform:
Control layer
Configuration, provisioning, and lifecycle
Plugins in the control layer handle setup, policy management, and service coordination. Examples: advanced authorization engines, identity federation, compliance modules.
Edge layer
User-facing request handling
Plugins in the edge layer run in the traffic path, making policy decisions before requests reach the workload. Examples: WAF rulesets, AI guardrails, advanced authentication flows.
Warpgate side
Workload-near processing
Plugins near the Warpgate handle processing where lower latency or reduced bandwidth matters. Examples: request transformations, local security checks, egress controls.
Example: Advanced API authorization with FAPI
Mezusphere provides simple and lean built-in OAuth 2.0 and OpenID Connect support for common needs: customer login, SSO, API authorization, route protection, and user management. For most teams, this is all you need.
But regulated industries, such as financial services, open banking, and healthcare, need capabilities that go beyond the mainstream baseline: Financial-grade API (FAPI) profiles, advanced authorization-server features, and protocol-heavy compliance requirements. Through plugins, Mezusphere can leverage third-party services to extend this functionality without forcing that complexity into the base product.
Here is how a third-party authorization engine integrates with Mezusphere's architecture to deliver FAPI-grade API security:
& API Clients
Engine (Plugin)
FAPI • OAuth 2.0 • OIDC
Edge layer
FAPI policy enforcement
Mezusphere's global edge applies FAPI-grade token validation, proof-of-possession checks, and request signing requirements before traffic reaches the Warpgate, using policies configured by the plugin.
Control plane
Authorization delegation
The control plane delegates advanced OAuth/OIDC operations, including token issuance, client management, and consent flows, to the third-party authorization engine via API calls, while keeping the management experience in the Console.
Warpgate
Identity-enriched forwarding
Warpgate receives traffic that has already been validated against FAPI standards and forwards identity context, including proof-of-possession confirmations, to your workload as trusted headers.
Plugin categories
The plugin ecosystem covers the capabilities you might need but not everyone does, keeping the core product lean while extending reach into specialized and regulated markets.
Identity
Advanced OAuth/OIDC and FAPI
Standards-heavy and regulated API features, including financial-grade profiles, advanced authorization-server capabilities, and proof-of-possession, without Mezusphere turning into a full banking-spec platform.
Authorization
External authorization engines
Fine-grained policy and entitlement engines for teams that need more specialized access models than the base platform carries by default.
Enterprise
Enterprise identity integration
Additional SSO, identity brokering, and federation packages for larger organizations connecting Mezusphere to existing enterprise identity estates.
Security
Security and compliance modules
Specialized WAF rulesets, regulated-industry controls, and compliance add-ons for teams that need deeper protection or vertical controls without another edge project.
AI
AI protection and policy
Advanced guardrail and abuse-detection services for AI-facing workloads: content safety, data exfiltration prevention, and prompt inspection with stronger controls than static rules alone.
Extensibility
Third-party extension runtime
A future runtime that lets specialized partners attach extension services to Mezusphere's traffic and control surfaces, opening the door to niche vertical features without returning you to vendor sprawl.
The marketplace direction
The goal is not just "plugins exist." It is that you can discover, install, configure, and manage advanced services through Mezusphere itself. The marketplace will grow as the extension model matures.
Service catalog
A browsable catalog of plugins and third-party services in the Console. Find what you need, understand what it does, and activate it.
One-click activation
Enable a plugin, configure it through Mezusphere's existing management interface, and start using it immediately. No separate vendor onboarding.
Integrated billing
Plugin costs show up on the same Mezusphere invoice. One bill, one relationship, clear visibility into total platform spend.
Partner with us
We are actively looking for third-party solution providers to partner with us in building the plugin ecosystem. We see this as a mutually beneficial opportunity:
For partners
Reach Mezusphere's customer base through a pre-integrated distribution channel. Your capabilities are delivered through a platform that users already trust and operate, with lower integration friction and higher adoption potential.
For Mezusphere
Extend platform value into specialized and regulated markets without building every niche capability in-house. Stronger platform defensibility and broader addressable market.
For customers
Access advanced capabilities through a familiar interface: the same Console, the same deployment model, the same billing relationship. No new integration projects, no new vendor relationships to manage.
If you provide advanced OAuth/OIDC, FAPI, authorization, enterprise identity, security, compliance, or AI protection services and are interested in partnering with Mezusphere, we would like to hear from you.
Simple at the center. Powerful at the edges.
Mezusphere's plugin ecosystem lets you start lean and grow outward, adding advanced capabilities without changing your deployment model or returning to vendor sprawl. Interested in building on the platform? Contact hello@mezusphere.com for partnership opportunities.