.svg)
Microsoft Fabric COMPATIBILITY
Making your Microsoft Fabric Platform Better:
New Capabilities. Extended Reach. Amplified ROl.
Keep what you love about Microsoft Fabric—add e6data where it matters. Save $1.5M–$10M (60% TCO), get 10x more queries, unlock real-time capabilities, extend governance to multi-region & cloud, hybrid—all SQL & Iceberg compatible.
.png)
Single compute engine handling all SQL and AI workloads
Microsoft Fabric’s all-in-one platform makes it simple to ingest, transform, and query data from a single platform. Yet when workloads surge, users demand faster turnaround times, stricter SLAs, higher concurrency, and lower costs—needs a single cluster can’t always meet without extra operational overhead.
.png)
e6data’s distributed k8s-native engine — built on atomic architecture
Keep what you love about Microsoft Fabric—add e6data’s engine into bottleneck workloads. Each workload (ingest, ETL, query, AI) —scale instantly, save $1.5M-10M (≤60 % TCO), run 10x more queries, get real-time streaming, extend catalog & governance securely to multi-cloud—no data movement or SQL rewrites.
USE CASES
Ingest, ETL, Query your most complex SQL and AI workloads
Add e6data to solve pressing pain points while staying on Microsoft Fabric, without any migration.
Dashboards that scale up to 1000 QPS
Power real-time dashboards with sub-2-second response times at high concurrency with consistent SLAs.
SQL meet AI in your Microsoft Fabric
Run semantic search on unstructured data using built-in cosine similarity in SQL. No vector DBs, no retrieval pipelines.
Deploy anywhere - cloud, on-prem, hybrid
The industry’s only Affinity and Locality-Aware Computing: 10x faster latency, 99% lower egress, 60% lower TCO.
Query on Apache Iceberg instantly
Query Iceberg on your Microsoft Fabric lakehouse using our native-Iceberg support, extended across all table formats.
Stream and query your events data in Microsoft Fabric under one minute
Materialize Kafka topics to Iceberg tables in your Azure ADLS (or S3 / GCS), and query them in under 60s at object-store cost, without any migration, and ETL.
Performance at production scale: run e6data in Microsoft Fabric
Benchmarks
Up to 10x faster querying, sub-second p99 latencies
.png)
Estimate your monthly cost
Up to 60% lower costs, granular, per vCPU scaling
.png)
Deploy across multi-cloud, multi-region, and on-prem
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
FAQs
How does e6data speed up Microsoft Fabric and cut costs?
Our query engine is kubernetes-native, disaggregated, and decentralised with stateless services. Our architecture is atomically-scalable, i.e., it scales granularly per vCPU increments. Hence, you only pay for cores consumed.
I use both Microsoft Fabric and Snowflake. Can I adopt e6data alongside both of them? Do I have to move out?
We integrate with your existing data architecture—whether you’re using Microsoft Fabric, Databricks, Snowflake, Trino, Athena, or any other engine—alongside your chosen catalog, governance framework, table format, and BI tools. You can deploy us anywhere: single or multi-cloud, multi-region, on-premises, or in a hybrid environment.
Do I have to copy or move data out of OneLake to use e6data?
No. e6data requires no data or stack migration: it reads Delta, Parquet, or Iceberg files directly in OneLake, alongside Fabric’s own engines, so your data never leaves Microsoft control and governance remains intact.
How do I deploy e6data inside Microsoft Fabric?
Spin up an e6data cluster from Azure Marketplace in the same subscription or VNet that hosts Fabric. Point it at your OneLake workspace and register the cluster’s JDBC/REST endpoint; notebooks, pipelines, and Power BI semantics can then route queries to e6data with no code/query changes.
How is e6data licensed and how does it show up on my Microsoft Fabric bill?
e6data is priced per usage of cores and is invoiced directly by e6data, separate from your Microsoft Fabric charges.
.svg){kind=logo}
.svg)
.svg)
.svg)
Available at
.png)
.svg)