> 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/quickstart.md).

# Get Started

Espresso is a real-time settlement layer for organizations building stablecoins, payment networks, tokenized assets, and other institution-grade financial applications. It enables dedicated execution environments with configurable compliance, privacy, and operational controls while providing decentralized settlement and interoperability with the broader digital asset ecosystem.

Whether you're modernizing existing financial infrastructure or launching a new digital asset platform, Espresso gives you the flexibility to build on your own terms without sacrificing security, performance, or connectivity.

***

## Is Espresso Right for You?

Espresso is a strong fit if you're building:

* Stablecoin platforms
* Payment infrastructure
* Tokenized asset platforms
* Private financial networks
* Regulated digital asset infrastructure

***

## Evaluating Espresso for Your Business

**What You Get**

* Dedicated execution environments tailored to your business and regulatory requirements
* Real-time settlement through decentralized Proof of Stake consensus
* Configurable compliance and privacy controls without sacrificing interoperability
* Secure crosschain connectivity through cryptographic proofs rather than trusted intermediaries

**Next Steps**

1. [Schedule an architecture review](https://form.typeform.com/to/KgayxNsX?typeform-source=www.espressosys.com) with the Espresso team.
2. [Explore example financial use cases.](/network/learn/use-cases.md)
3. [Review configurable execution environments.](/network/learn/rollup-architecture.md)
4. Discuss your deployment and integration strategy.

***

## Integrating an Existing Chain

If you already operate a chain or application environment, Espresso can add decentralized settlement and fast finality without requiring a new execution stack.

**What You Get**

* Fast settlement on Mainnet, backed by a decentralized validator set, with the ability to scale to millions of transactions per second
* EVM compatibility: Espresso integrates with EVM execution clients including Besu, so existing teams can integrate without adopting a new execution stack
* Horizontal scaling: teams running Besu can deploy multiple parallel instances on Espresso, scaling throughput linearly while finality latency stays bounded
* Full integration support: kick-off call, devops assistance, async support, and 24/7 monitoring through each stage of the integration

**Next Steps**

1. [Review integration paths, prerequisites, and timelines.](/network/developer/rollup-developers.md)
2. [Schedule a kick-off call](https://form.typeform.com/to/KgayxNsX?typeform-source=www.espressosys.com) with the Espresso team.
3. Discuss your deployment architecture and go-live timeline.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.espressosys.com/network/learn/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
