ClickHouse
1.0 open-sourceThe section your link pointed to isn't on ClickHouse's page any more, so we've brought you to the top.
ClickHouse® is a real-time analytics database management system
CREATE USER 'newuser' IDENTIFIED WITH plaintext_password BY 'pass' VALID FOR 1 YEAR;
INSERT INTO table FORMAT JSONEachRow [{"ts": 1703363853.035}]
EXPLAIN ANALYZE SELECT user_id, COUNT(*) FROM events GROUP BY user_id;
SELECT * FROM filesystem('/var/log', '*.log')
SET kafka_autodetect_client_rack = 1
SELECT arrayMap(negate, [1, 2, 3])
ALTER TABLE my_table ADD INDEX idx_json_all_paths (json_column) TYPE json_all_paths GRANULARITY 1;
CREATE QUOTA q KEYED BY normalized_query_hash LIMITS 100 queries_per_normalized_hash FOR INTERVAL 1 HOUR;
clickhouse-keeper-client --host localhost --port 9181 lsr /my/path
CREATE TABLE t_map (m Map(String, UInt64)) ENGINE = MergeTree() SETTINGS map_serialization_version = 'with_buckets', max_buckets_in_map = 1024;
SELECT * FROM mergeTreeTextIndex('default', 'my_table', 'text_idx') WHERE match(column, 'pattern');
Summary
ClickHouse is an open-source (Apache 2.0), column-oriented database management system that generates analytical data reports in real time, storing and querying data organized by column rather than row to make large-scale aggregation fast. Teams install it as a single binary on Linux, macOS, or FreeBSD, or run it as a managed service through ClickHouse Cloud, built by the same team that maintains the open-source project. In the siem space it functions as a security data lake, giving SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. teams and platform engineers a backend to store and run OLAP-style queries over large volumes of log data rather than a packaged detection or alerting layer. Launched in 2016, it remains actively developed, with 55 tracked releases and a last release 12 days ago.
ClickHouse® is a real-time analytics database management system
How ClickHouse helps
Which servers or services are showing unusual spikes in traffic right now?
ingests and aggregates high-volume log and event data with column-oriented storage, letting a query across millions of rows return in real time instead of after a batch job finishes
Where did a suspicious user session go across our infrastructure over the last month?
stores raw log and event history in a queryable table rather than a rolling window, so a single query can trace one identity or IP across weeks of records
Which piece of our stack is producing the most log volume and driving up our storage bill?
groups and counts events by source, host, or service across the full retention window in one aggregation pass
Are last week's alerting rules still catching what they used to?
keeps the full history of raw events, so a changed detection query can be re-run against the same past data to compare what it flags now versus before
Who has access to which piece of our deployment, and did that access just change?
records for organizations, members, roles, and keys are held as queryable data, so a query can show current grants or when a role or key was added or removed
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for ClickHouse, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail ClickHouse puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · ClickHouse vendor page41 readings of ClickHouse's pricing page since Oct 2022, with 3 relaunches of its plan lineup and 16 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
runreveal.com, every changeClickHouse's home and pricing pages and 8 more pages as they looked each month from January 2023 to October 2026: 17 renders, 5 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What ClickHouse connects to, runs on and detects, read from its release notes and docs. So far: 1 new integration.
1 change, tracked since Sep 29, 2026.
-
Sep 292026
new Integrations documentation index
With connectors
Integrations (245 pages): Documentation for Integrations. - English / Integrations (245 pages): Documentation for English / Integrations. - English / Integrations / Connectors (120 pages): Documentation for English / Integrations / Connectors.
Other 2
Nothing first seen in this window. That doesn't mean ClickHouse shipped nothing, only that we found no record of it.
How we count
Read from 1 of 22 release notes and docs updates we hold for ClickHouse. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through ClickHouse's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
22 entries
No entries match these filters.
- November 20261
- October 20264
- September 20266
- August 20261
- July 20261
- June 20261
- May 20261
- April 20261
- March 20261
- February 20261
- January 20261
- March 20251
- August 20241
- December 20231
Project health
Issue, contributor and maintainer activity in ClickHouse/ClickHouse, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 725 +209 vs prior 12 months
- Maintainers 47 +18 joined · −20 left, last 12 months
- Bus factor 10 committers behind half the commits
- Community-filed 48% of issues opened, last 12 months
- Median time to close 29 days first maintainer reply 7.5 days
- Open backlog 5,164 of 13,133 issues ever filed
- Issues opened / month 186 · 271 communitymaintainers
- Open backlog 5,164
- Contributors / month 197
- Commits / month 5,713
- Stars not measured
- bugs 37%
- features 10%
- questions 4%
- docs 1%
- other 48%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →