> For the complete documentation index, see [llms.txt](https://docs.espressosys.com/network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.espressosys.com/network/learn/espresso-in-the-modular-stack.md).

# How Espresso Fits

Espresso is a decentralized settlement layer. Chains and applications integrate with Espresso to get decentralized Proof of Stake settlement and finality on the blocks they produce, optional data availability, and state finalized by Espresso that other chains and applications can verify when they need to rely on that settlement.

Espresso plays the same role in every integration. What differs is the deployment shape. Espresso is also interoperable with other chains like Ethereum.

## Pattern 1: A dedicated execution environment built around Espresso

A team builds an application or chain that runs its own execution environment (defining its own rules for fees, ordering, compliance, and asset support) and settles through Espresso. That environment can use Besu or another EVM client, rather than a single prescribed execution stack. Multiple parallel instances of the same environment can run on Espresso simultaneously, scaling throughput linearly without redesigning application logic. Espresso's decentralized Proof of Stake finality on the chain's blocks is the chain's settlement guarantee; counterparties can verify state finalized by Espresso when they need to rely on that settlement.

This pattern fits institutions and application teams that need:

* Control over their operating environment (fees, ordering policy, compliance, asset support).
* Predictable performance independent of general-purpose chain congestion.
* Decentralized settlement and finality without operating their own validator set.
* Connectivity to broader onchain markets through Espresso's interoperability.

See [Configurable Execution Environments](/network/learn/rollup-architecture.md) for more detail.

## What Espresso does not do

* Espresso does not execute application transactions. Execution always happens in the application's own environment.
* Espresso does not act as a shared sequencer and does not control each application's transaction ordering rules. Each integrated chain runs its own sequencer or builders; Espresso provides decentralized settlement and finality for the blocks they propose.

## Where to go next

* For institutional readers evaluating which pattern fits: [What is Espresso?](/network/learn/what-is-espresso.md) and [Use Cases](/network/learn/use-cases.md)
* For chains and applications building a dedicated execution environment: [Configurable Execution Environments](/network/learn/rollup-architecture.md).
* For teams integrating an existing chain into Espresso, see the chain integration guides under the Developer track.
* For network contracts and endpoints: [Networks](/network/network/networks.md).