Project Antalya

Bringing real-time analytics to the next level

Project Antalya adds new capabilities to ClickHouse®. It is not a fork of ClickHouse; we are submitting PRs to upstream ClickHouse as our functionality matures.

What Project Antalya delivers

The project’s goals are:

  • A 90% reduction in storage costs by replacing ReplicatedMergeTree tables with Iceberg / Parquet
  • 10x to 100x faster queries through swarm clusters
  • No application changes necessary - the functionality of Antalya is a drop-in upgrade for existing open-source ClickHouse deployments
  • Universal data access - real-time, AI, and batch workloads should use a single source for data

Problems Project Antalya solves

The project was designed to solve crucial problems facing analytics workloads today:

  • Compute and storage are coupled - Compute and storage should be separate, so that scaling one up doesn’t require scaling up the other.
  • Multiple workloads (real-time, AI, batch) have their own copies of the same data - There should be a single data lake containing a single copy of all data.
  • SQL queries aren’t able to access all data - An SQL query should be possible to access all data, no matter where it lives or how it’s stored. And of course that should be possible with ClickHouse.

Status - Roadmap and Release Notes

👉 As of July, 2025, Project Antalya is not for production use.

You can find the project roadmap in the Antalya branch of Altinity's ClickHouse repo.

The latest release is version 25.3.3.20143. See the release notes page for the details of the release, including differences between the latest Project Antalya release and upstream ClickHouse.

The details

The following pages explain the concepts behind Project Antalya, as well as the configuration settings to enable them and the SQL syntax to access them:

Project Antalya Concepts Guide

What is Project Antalya, and why did we build it?

Command and Configuration Reference

The technical details you’ll need to make the most of Antalya