Acquisitions
EDB Buys Altinity to Combine Postgres and ClickHouse for Sovereign AI

EDB announced its acquisition of Altinity on November 5, 2026, combining Postgres transactional technology with ClickHouse real-time analytics in its sovereign AI data system. The transaction is complete, and Altinity’s engineers are joining EDB’s Postgres contributors and maintainers.
Altinity, founded in 2017, provides enterprise software, managed services and support for organizations running open-source ClickHouse in production. Its customers include The Trade Desk, Tubi, Kong, AppsFlyer, ZoomInfo and PostHog. In its acquisition briefing, EDB puts the combined customer base at more than 1,860 enterprises.
The acquired portfolio includes Altinity Stable Builds, with long-term support and FIPS-compatible builds for regulated environments; Antalya Builds for storage, authorization and data-lake integration; Altinity.Cloud for deployments in customers’ own cloud accounts; and the Altinity Kubernetes Operator. EDB reports more than 108 million Docker Hub pulls for the operator.
A Combined Architecture for Agentic AI
The acquisition targets a specific architectural problem: enterprise systems that run transactions are commonly separated from those that analyze the resulting activity. EDB argues that this fragmentation creates latency, cost and vendor lock-in, while a single agentic workflow may need to transact, analyze and act on the same business context.
Within EDB Postgres AI, Postgres supplies the operational record and ClickHouse analyzes large volumes of events and business activity. Closer integration is intended to reduce data movement and integration effort, helping applications and agents understand activity and act on it. The wider architecture combines a multi-model data layer, data-layer governance, an agentic runtime and a sovereign control plane, with permissions enforced where the data resides.
The integration roadmap includes a shared Apache Iceberg catalog and consistent access controls across Postgres and ClickHouse, connecting transactional workloads, real-time analytics and open lakehouse architectures. Governance is designed to determine what agents can access and do at the data layer, provide an audit trail and leave an off switch under customer control.
Jump Trading chief technology officer Alex Davies said the firm uses ClickHouse with Altinity for real-time analytics across cloud and on-premises environments. He sees the combined Postgres and ClickHouse stack as a way to run analytical and transactional workloads under customer control.
Deployment Plans and Customer Continuity
EDB plans to introduce integrated enterprise ClickHouse capabilities in the fourth quarter of 2026 and will detail availability as individual offerings arrive. The deployment roadmap spans bring-your-own-cloud, a developer cloud, self-hosted or on-premises installations on customer-managed Kubernetes or OpenShift, and physical far-edge systems for air-gapped, fully disconnected execution on local hardware.
Altinity said in its own announcement that it has become the EDB Real-Time Analytics group, reporting directly to EDB CEO Kevin Dallas. The full management team remains in place, while customer contracts, service-level agreements, products and services are unchanged. Customers can continue using the same support channels and engineering teams.
EDB committed to ClickHouse remaining under Apache 2.0 and to Altinity Stable Builds, the Kubernetes Operator and Project Antalya staying open source under that license. The contributor license agreement and request-for-comments process are to remain unchanged, upstream contributions will continue, and Altinity.Cloud customers will retain their services, service-level agreements and deployments.
ClickHouse, Inc. and the open-source project remain independent of EDB, and the acquisition does not imply ClickHouse, Inc.’s sponsorship or endorsement. EDB describes itself as the No. 1 Postgres contributor for more than 20 years and Altinity as the No. 2 company contributor to ClickHouse for more than a decade, with 888 merged pull requests.
IDC research director Devin Pratt said the practical test is whether the combined platform can coordinate its specialized engines, preserve their individual strengths and reduce customers’ integration burden and costs. For EDB, that makes the shared catalog, common controls and deployment roadmap the substance of the integration challenge: they must turn two distinct database engines into a coherent system without undermining the continuity promised to Altinity’s customers and open-source users.












