Skip to content
In this postPostgreSQLClickHouse

EDB buys Altinity: Postgres and ClickHouse keep moving in together

EDB bought Altinity on November 5. Four days later ClickHouse said it was buying Xata. Two deals from opposite directions, one conclusion: vendors want to own both your transactional and your analytical database.

By Bob Bass4 min read
PostgreSQLClickHouseDatabases

On November 5, EnterpriseDB (EDB) announced that it had acquired Altinity, the ClickHouse support and hosting company. Four days later, ClickHouse Inc. announced that its Managed Postgres service was generally available and that it was acquiring Xata, a Postgres company.

So in one week, a Postgres company bought a ClickHouse company, and a ClickHouse company bought a Postgres company. That is not a coincidence. It is two vendors racing to sell the same bundle.

What EDB announced

The facts from EDB's press release and Altinity's own post:

  • Financial terms were not disclosed.
  • Altinity becomes the "EDB Real-Time Analytics group", reporting to EDB CEO Kevin Dallas. Altinity's CEO Robert Hodges wrote that "the entire management team remains in place."
  • Existing customers keep what they have. In Hodges's words: "Customer contracts remain the same, the SLAs are the same, the products and services are the same."
  • Integration comes next. EDB says it "plans to introduce integrated enterprise ClickHouse capabilities in Q4 2026," and its road map includes "a shared Apache Iceberg catalog and consistent access controls across Postgres and ClickHouse software."
  • The target is EDB Postgres AI, the company's enterprise platform, which the release pitches for bring-your-own-cloud, self-hosted Kubernetes and OpenShift, and edge deployments.

One detail worth knowing if you are new to this corner of the market: Altinity has never been part of ClickHouse Inc. It is an independent company that builds, supports and hosts the open source ClickHouse server, and the release says so in its trademark notice. EDB now owns the largest independent ClickHouse vendor, not the company behind ClickHouse.

Why both sides want both engines

Most products that grow past a certain size end up with two databases. Postgres holds the operational record: users, orders, subscriptions, anything that needs transactions and constraints. ClickHouse holds the firehose: events, logs, metrics, clickstreams, anything you aggregate over hundreds of millions of rows. EDB's release puts it the same way: "Postgres provides a reliable operational record; ClickHouse software enables fast analysis of large volumes of events and business activity."

The painful part was never either database. It is the seam between them: the change data capture pipeline, the nightly export, the duplicated access rules, and the second vendor relationship. Whoever owns that seam owns the customer. ClickHouse went after it by launching a managed Postgres earlier this year and then buying Xata for branching and scale-to-zero. EDB, which already sold a ClickHouse offering before the deal, went after it by buying the team that knows ClickHouse operations best.

Expect more of this. Supabase bought Turso in October, Databricks bought Neon last year and Electric in August. Database companies are buying their way into owning more of your stack.

If you are an Altinity customer

Nothing changes today, and both companies were explicit about that. The things worth watching over the next few renewals:

  • Pricing at renewal. Contracts stay the same until they come up for renewal. After that, they will be written by a company with an enterprise platform to sell.
  • Where the road map points. Integrated ClickHouse inside EDB Postgres AI is the stated priority for Q4. If you run ClickHouse without Postgres, or with Postgres from someone else, check whether new features still reach you.
  • The open source builds. Altinity Stable Builds, the Antalya builds and the Altinity Kubernetes Operator (which the release says has more than 108 million Docker Hub pulls) were all named in the announcement. Neither company has published a product-by-product plan for them yet.

None of this is a reason to panic. ClickHouse is open source and your data is in a standard format. That means the cheapest insurance is knowing your exit before you need it. Moving a table between two ClickHouse servers can be a single statement, run on the new server:

sql
INSERT INTO events
SELECT * FROM remoteSecure('old-host:9440', 'analytics', 'events', 'reader', 'password');

Create the table with the same schema on the new server first, copy the largest tables in batches by date range, and compare row counts before you switch reads.

The bundle without the enterprise contract

EDB's and ClickHouse's versions of this bundle are built for companies with procurement teams. They come with BYOC deployments, OpenShift support, sales calls and annual contracts. If you are a smaller team, what you probably want is simpler: a Postgres and a ClickHouse that you can create in a minute and pay for together.

Layerbase Cloud runs both, along with 19 engines in total, under one plan and one dashboard. Postgres runs on every plan, including Free, and ClickHouse needs a paid plan. Each database gets a standard connection string, so your existing drivers and tools work unchanged. You can start with a PostgreSQL database for the app and a ClickHouse database for events, and see whether one bill is all you were after.

More on the other side of this week's news: Xata is joining ClickHouse: what to do. If you are comparing managed ClickHouse options in general, start with ClickHouse Cloud alternatives.

Support chat