PhoenixAI Database

PhoenixAI Anywhere — the same engine, inside your own infrastructure.

Self-managed on Kubernetes, in your cloud or on-premises, with full control of your environment.

PhoenixAI Cloud dashboard showing a running cluster with connection details, usage metrics, and activity feed

What it is

The full engine. Not a stripped-down edition.

PhoenixAI is a real-time analytical database for AI agents and customer-facing analytics. It serves sub-second SQL across streaming data and your Apache Iceberg lakehouse, with minimal data movement.

It handles workloads that break other databases: agent queries needing sub-second answers, complex multi-table joins on fresh data, and customer-facing analytics at tens of thousands of QPS. Standard SQL throughout, so existing tools connect without rewrites.

<1s

Query latency

on multi-table analytical queries

<5s

Ingest to queryable

on streaming mutable data

10K+

QPS

Sustained load

90%

Lower infrastructure footprint

than other real-time analytics solutions

Core capabilities

Runs where your data has to stay.

Four things PhoenixAI is built to do, at the scale AI workloads demand.

Sub-second SQL on real-time and historical data

PhoenixAI keeps query latency under a second across both freshly streamed data and historical lakehouse data, under the high concurrency AI agents and customer-facing analytics demand. Latency stays stable whether traffic is hundreds of QPS or tens of thousands.

  • Stable p99 latency at high QPS
  • Second-level freshness on mutable streaming data
  • One SQL interface across real-time and historical data

Complex multi-table queries without precomputation

AI agents and dashboards issue queries you can’t always plan for. PhoenixAI runs multi-table joins on the fly against normalized schemas, with no need to pre-flatten or pre-aggregate. Materialized views stay available as optional accelerators for the heaviest repeat patterns, not as a mandatory starting point.

  • Multi-table joins on the fly, on the data as it lives
  • No mandatory denormalization or pre-aggregation
  • Materialized views as optional accelerators

Fits into your existing data stack

PhoenixAI sits alongside the infrastructure you already have. Query your lakehouse in place, ingest streams as they arrive, and connect through standard SQL, without rewriting queries, replacing tools, or copying data into a separate warehouse.

  • Query your Apache Iceberg lakehouse in place
  • Native streaming ingestion from Kafka, Flink, and Spark
  • Standard ANSI SQL that works with existing BI tools, drivers, and applications

Full control with Anywhere

The full PhoenixAI engine, not a stripped-down edition. Kubernetes-native automation and self-healing operations let your platform team run it entirely inside your own environment — without taking on manual ops.

  • Full control over your deployment environment
  • Runs in your cloud VPC or on-prem, air-gapped included
  • Automated at scale on Kubernetes

How it works

Kubernetes-native, so your platform team can run it.

Cost-Based Query Optimizer

The optimizer picks join strategies, predicate push-downs, and execution paths based on actual data statistics at runtime. Multi-table joins that time out elsewhere complete in well under a second, without manual hints or query rewrites.

SIMD-Optimized Vectorized Execution

PhoenixAI’s query engine processes data in column-oriented batches using SIMD CPU instructions. On complex aggregations and scans across billions of rows, this translates directly into sub-second response times.

Massively Parallel Processing Architecture

Massively parallel processing compute architecture distributes joins and aggregations across every node in the cluster. Complex multi-table joins on large fact and dimension tables scale out as the dataset grows, with no need to pre-aggregate or denormalize by default.

Works with

Apache KafkaApache FlinkApache SparkAWS KinesisApache IcebergDelta LakeApache HudiConfluentDatabricksdbtTableauLookerSupersetJDBC / ODBCREST APIAWSAzureGoogle Cloud

In production

What platform teams say.

Coinbase's blockchain dataset spans hundreds of billions of rows across more than 300 normalized tables. Our fraud and compliance workloads require complex joins, and blockchain network analytics demand low-latency query performance that our previous query engines could not provide. PhoenixAI changed the equation: streaming updates from Kafka become queryable within seconds, analysts get sub-second responses on live normalized data, and our AI agents operate on the same real-time dataset. This level of performance at scale fundamentally changes what data teams can do.

Coinbase

PhoenixAI customer

>300

Normalized tables

PhoenixAI is at the center of our real-time data analytics. We strive for quicker and easier insights into day to day operations. We chose PhoenixAI for its ability to upsert data in real-time, support for joins across large fact tables with very low latency, and the ability to serve and join native and external tables from the same cluster.

Fanatics

PhoenixAI customer

<1s

join latency

Demandbase AI introduced unpredictable LLM-generated SQL that our previous ClickHouse-based architecture wasn’t built to handle. PhoenixAI gives us a fast, isolated warehouse for agent workloads directly on our Apache Iceberg tables, with the optimizer handling novel joins automatically. Our agents now query petabytes of normalized data across thousands of tenants while customer-facing dashboards keep their second-level SLAs.

Ryan Nowacoski

Senior Engineering Manager, Data Platform, Demandbase

Petabytes

agent workloads

Try it in your own environment.

Book a 30-minute session with our team. Bring your workload; we’ll walk through it live and show you how PhoenixAI would handle it.