> 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 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.eclipse.xyz/architecture/eclipse-architecture/why-eclipse.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.