> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/get-started/readme/about-e6data.md).

# About e6 Query Engine

What e6data is and how the platform is organized - the starting point before you deploy and query.

This section introduces e6data: what it is, how it works, the vocabulary used throughout the docs, and the deployment models you can choose from.

## Start here

Work through these in order if you're new to e6data:

1. [Introduction](/query-engine/get-started/readme.md) - what e6data is and why it's built the way it is.
2. [How e6data works](/query-engine/get-started/readme/how-e6data-works.md) - the engine and request flow at a glance.
3. [Key concepts](/query-engine/get-started/architecture/high-level-architecture.md) - the vocabulary you'll see throughout the docs (workspace, cluster, catalog, Compute Plane, and more).
4. [Platform components](/query-engine/get-started/architecture/platform-components.md) - what makes up the Control Plane and Compute Plane.
5. [Deployment models](/query-engine/get-started/deployment-models.md) - Serverless vs. In Your VPC.

## Next

Once you understand the platform, set up your account in [Identity and access setup](/query-engine/get-started/identity-access-setup/sign-up-and-login.md), then run your first query with the [Quickstart](/query-engine/get-started/quickstart.md).


---

# 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.e6data.com/query-engine/get-started/readme/about-e6data.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.