> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/architecture/eclipse-architecture/why-eclipse.md).

# Why Eclipse?

Eclipse is engineered for applications that demand more than what L1s or conventional rollups can deliver.\
\
L2s today often inherit L1 bottlenecks. Eclipse takes the opposite approach: settle on Ethereum, optimize everything else for performance.

Instead of replicating the limitations of Layer 1s, Eclipse builds a modular system designed to make full use of contemporary hardware, from CPUs and GPUs to advanced networking interfaces.

With high-performance SVM execution, application-specific scheduling, and independently scalable components, Eclipse offers the flexibility and power developers need to build the next generation of web3 applications, from high-frequency trading and real-time gaming to AI agents and decentralized infrastructure.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eclipse.xyz/architecture/eclipse-architecture/why-eclipse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.