> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# What are plugins?

> Plugins are how you extend a product without changing its core.

They're modular components that run alongside the platform, adding new logic, endpoints, or workflows to support specific business needs. Instead of reinventing the wheel or building custom features from scratch, you can plug in what you need and keep everything else **stable**, **scalable**, and **secure**.

<Warning>
  Plugins are premium features currently available only to **Enterprise customers** and are licensed separately.
</Warning>

<Info>
  **CRM** is no longer a plugin. It is now an embedded component of Midaz, available out of the box with no additional license required. See [CRM Overview](/en/midaz/crm/crm-overview) for details.
</Info>

In Midaz, we use plugins to let you:

* Handle real-time payments with [**Pix**](/en/midaz/plugins/pix/pix-overview)
* Apply dynamic fees and taxes using the [**Fees Engine**](/en/midaz/plugins/fees-engine/fees-engine-overview)
* Process electronic transfers between banks through [**Bank Transfer (TED)**](/en/midaz/plugins/ted/ted-overview)

And much more, all without touching the platform's core engine.

### Why we designed it this way

Midaz was built to be composable. That means everything runs as independent services that talk to each other, including plugins. This gives you:

* **Flexibility**: Add, update, or remove plugins without downtime
* **Separation of concerns**: Business-specific logic lives in the plugin, not the core
* **Better control**: Each plugin has its own versioning, deployment, and monitoring
* **Safe evolution**: The platform can grow without breaking your integrations

### What a plugin can do

A plugin can:

* Expose new APIs
* Persist and transform data
* Run background jobs and scheduled tasks
* React to events (like new transactions or ledger updates)
* Define its own configuration, rules, and access policies

As long as it follows Midaz's interface contract and authentication model, it can integrate just like a native feature.

<Tip>
  You can think of plugins as microservices with a clear purpose, designed to feel native to the rest of the platform, but built to evolve independently.
</Tip>

For the full catalog of available plugins and information on building your own, see [Our plugins](/en/about-plugins).