> ## 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.

# Architecture and operations

> Follow the architecture, observability, and operational standards every plugin must meet to interoperate with Midaz and run in production.

Plugins in the Lerian ecosystem must be designed with interoperability, scalability, and resilience in mind. This section outlines the architectural and infrastructure standards that ensure your plugin connects to Midaz through its standard interfaces and runs reliably in production.

These are **mandatory requirements** for every partner solution published on the Lerian Marketplace.

## Programming language and architecture

***

You're free to choose the programming language that best suits your plugin, but keep in mind that Lerian's stack is primarily built in **Golang**, and your solution must interoperate with it through its standard interfaces.

**We recommend:**

* Container-first design using **Docker**.
* **Domain-Driven Design (DDD)** for clean modularity.
* **Isolation** of concerns and microservice-friendly practices.

## MSP model requirements

***

All plugins must be designed to run under the **Managed Service Provider (MSP)** model, with:

* **Infrastructure as Code (IaC)** documented, preferably in Terraform.
* **Helm Charts** for Kubernetes deployments.
* Declarative deployment with **GitOps**.

<Danger>
  GitOps is required to ensure traceable and predictable production deployments across environments.
</Danger>

## Observability

***

Plugins must be **observable by design**, including:

* Structured logs
* Domain-specific metrics
* Distributed tracing

All observability data must integrate with **OpenTelemetry (OTel)** and support **OTLP** exports.

<Tip>
  Common destinations include Datadog, Prometheus, and other APM tools.
</Tip>

## Auditability and traceability

***

If your plugin handles transactions, it must integrate with **Trillian** or an equivalent solution for:

* Immutable, verifiable audit logs
* Integrity verification (off-chain capable)

<Warning>
  Plugins impacting financial data without auditability will not pass homologation.
</Warning>

## Authentication and authorization

***

Every plugin must integrate with Lerian's Access Manager, our identity and access control plugin.

<Note>
  This ensures a unified authentication experience for clients. For more information, refer to the [Access Manager Guide](/en/platform/access-manager/access-manager) .
</Note>