Extension Ecosystem

XyPriss Plugin Ecosystem

Plugins in XyPriss are fully integrated, secure modules that hook deep into the framework's lifecycle, enabling modular extensions without compromising performance.

Performance-First Architecture

Execution Lifecycle Phases

NetworkPhase 1: Ingress
SecurityPhase 2: Shielding
CachePhase 3: Storage
LogicPhase 4: Handler
Predictable Latency

Plugins execute in deterministic phases to ensure microsecond overhead.

Isolated Context

Every plugin runs in a restricted proxy to prevent global state mutation.

Why XyPriss Plugins?

If you are wondering why you should build a plugin instead of just writing standard middleware, the answer lies in the Capability-Based Security and Deep Integration.

Full Lifecycle Access

Plugins can initialize database connections on server start, monitor real-time traffic, and handle graceful resource shutdowns.

Zero-Trust Sandbox

Each plugin runs in a sandboxed PluginServer proxy. They cannot read sensitive environment variables or configs without explicit permission.

Permission Control

Plugins must declare their intentions. You hold the final keys to their permissions via the Capability-Based security model.

XFPM Distribution

Official plugins can be published to the NPM/XFPM ecosystem and instantly integrated by the community.

Secure by Default

Zero Compromise Policy
XyPriss philosophy insists that extending your application should never mean compromising it. Plugins are prohibited from overwriting core server properties or reading hardware-local secrets silently.

Get Started

Usage Tutorial

Learn how to install, trust, and authorize plugins in your server configuration.

Authoring Tutorial

Build your own plugins from scratch using TypeScript and the G3 signing protocol.

Plugin Usage Lifecycle

XyPriss enforces a strict sequence of steps to ensure that every plugin you use is verified, authorized, and audited.

1. Install & Trust

Use XFPM to install and verify the author's Public Key (TOFU Flow).

2. Authorize

Configure the $internal block with pinned signatures and capabilities.

3. Register

Add the plugin to your server configuration or programmatic execution.

4. Audit

The XHSC core performs a deep startup audit to verify file integrity.

Next Steps

Explore our structured guides to integrate third-party plugins or build your own high-performance extensions.

Plugin System Guide

Deep dive into the modular core (Registries, Interceptors, and Restricted Proxies).