Skip to main content

​
What is the e6data Query Engine?

The e6data Query Engine is a lakehouse compute engine for data teams who need fast, cost-efficient analytics directly on their data lake. It runs SQL and AI workloads against your existing storage - S3, ADLS Gen2, or Iceberg-managed data - without copying data into a separate warehouse. It is designed for the three things that make modern analytics hard:
  • High concurrency - many users running many queries at the same time.
  • Complex SQL - joins, window functions, and aggregations over large fact tables.
  • Cost discipline - paying for what you actually use, not for idle infrastructure.

​
How customers use Query Engine

  • BI dashboards at the scale of thousands of concurrent users, with sub-second query times.
  • Operational analytics for product, ops, and revenue teams that need fresh answers, not warehouse refresh cycles.
  • Ad-hoc exploration on data lakes too large to load into a traditional warehouse.
  • AI/ML feature pipelines running close to the data.

​
Start here

The rest of this section covers how Query Engine works, the vocabulary used throughout the docs, and the deployment models you can choose from. Work through these in order if you’re new to e6data:
  1. Introduction - what e6data is and why it’s built the way it is.
  2. How e6data works - the engine and request flow at a glance.
  3. Key concepts - the vocabulary you’ll see throughout the docs (workspace, cluster, catalog, Compute Plane, and more).
  4. Platform components - what makes up the Control Plane and Compute Plane.
  5. Deployment models - Serverless vs. In Your VPC.

​
Next

Once you understand the platform, set up your account in Identity and access setup, then run your first query with the Quickstart.
Last modified on October 21, 2026