StarTree Cloud
A managed Apache Pinot platform that serves sub-second, high-concurrency analytics directly on Apache Iceberg and Parquet tables in object storage, with no ETL into a separate store.
Summary
A managed Apache Pinot platform that serves sub-second, high-concurrency analytics directly on Apache Iceberg and Parquet tables in object storage, with no ETL into a separate store.
It sits at the serving layer of a lakehouse, competing with batch lakehouse engines (Trino, ClickHouse) on latency and cost-per-query rather than on ad-hoc SQL breadth. For S3-native data infra, it turns Iceberg-on-S3 into a directly servable, user-facing analytics substrate.
- Native Iceberg querying shipped July 2025; the eye-catching 9-39x numbers come from a separate May 2026 benchmark, not the launch post.
- Headline QPS (up to 498) depends on index pinning; cold first-touch queries against object storage are slower.
reads_fromApache Iceberg — queries Iceberg/Parquet directly without conversion to Pinot segments.competes_withTrino — same Iceberg-on-S3 data, but optimized for low-latency high-QPS serving.enablesLakehouse — adds an interactive serving tier on top of lakehouse storage.
Definition
StarTree Cloud is a fully managed real-time analytics platform built on Apache Pinot, the open-source OLAP database for low-latency, high-concurrency queries. It extends Pinot with enterprise features and added native querying of Apache Iceberg and Parquet tables directly on object storage. The goal is interactive, external-facing analytics served straight from a lakehouse.
Iceberg tables on S3 are normally queried by batch engines (Trino, ClickHouse) with seconds-to-minutes latency. StarTree lets you serve sub-second, high-QPS queries directly off Iceberg/Parquet on object storage without ETL into a separate serving store, collapsing the lakehouse-to-serving-layer copy. That makes object storage itself the serving substrate for user-facing analytics.
User-facing/external analytics, real-time dashboards on lakehouse data, high-QPS aggregations over Iceberg, anomaly and metrics serving, lakehouse query acceleration without data duplication.
Connections7
Outbound7
scoped_to1reads_from2competes_with1alternative_to1optimizes_for1enables1Resources3
Official announcement of native Iceberg/Parquet querying with no transformation or duplication (July 23, 2025).
May 2026 benchmark with concrete latency, QPS, cost-per-query, and CPU numbers vs Trino and ClickHouse.
Explains the Parquet forward-index reader and pruning that enable direct sub-second Iceberg serving.