ClickHouse’s cover photo
ClickHouse

ClickHouse

Software Development

Palo Alto, California 150,992 followers

ClickHouse is a fast, open-source columnar database built for real-time data processing and analytics at scale.

About us

ClickHouse is a fast, open-source columnar database built for real-time data processing and analytics at scale. ClickHouse Cloud delivers the query speed and concurrency that applications demanding instant insight from large volumes of data require. As AI agents become more embedded in software, generating higher query volumes at tighter latency, ClickHouse provides a high-throughput, low-latency engine purpose-built for that workload.

Website
https://www.clickhouse.com
Industry
Software Development
Company size
501-1,000 employees
Headquarters
Palo Alto, California
Type
Privately Held
Founded
2021

Locations

Employees at ClickHouse

Updates

  • Your favorite Postgres database now comes with a quest log 🎮 We redesigned ClickHouse Managed Postgres onboarding around the fastest path from an empty service to doing something useful with your data. Your objectives, should you choose to accept them: 1️⃣ Spin up a Postgres service 2️⃣ Migrate or ingest data 3️⃣ Run your first query 4️⃣ Run analytics with ClickHouse 🔓 Bonus level: use pg_clickhouse as one SQL layer across both engines. https://lnkd.in/eEG3dNUJ

  • QuintoAndar is the largest housing platform in Latin America, closing 15,000 new rental contracts every month across 60,000 active listings. Their customer data platform (CDP) collects over 1 billion events a month from 14 million users. When the two-pipeline setup behind it became too slow and expensive, they turned to ClickHouse Cloud. Then they hit a wall. Marketing wanted to use Hightouch’s Customer Studio feature to build audiences and journeys, but it doesn’t support ClickHouse as a source. They needed a way to put a supported source in front of ClickHouse… and found their answer in managed Postgres. Tech lead manager Bruno Brito joined us on a recent webinar, where he walked through the rebuild, the roadblock, and why Postgres managed by ClickHouse turned out to be the missing piece of their architecture. Read the full story 👇 clickhou.se/4zBrdyd

  • Last chance to register! Next week (Tue, Sept 1), our Open House Roadshow in EMEA kicks off in Amsterdam, and seats are almost gone. You'll get: keynotes, hands-on training, and customer stories from Picsart, Trade Republic, and Infinitas Learning, all straight from the engineers building ClickHouse. We have 20 more seats left, make sure to secure your spot! 👉 Register now: https://lnkd.in/e58gHxUU #ClickHouse #OpenHouse #Amsterdam

  • High cardinality is where Prometheus starts to hurt, and it comes down to how it stores data: every unique combination of labels becomes its own time series, with its own memory, index, and lifecycle. That adds up fast. A thousand hosts times a hundred apps times five status codes times fifty endpoints is 25 million series, and each one carries around 200 bytes just for its in-memory struct, before any samples. Add one more label like container_id and the count multiplies again, which is how teams end up with Prometheus using tens or hundreds of gigabytes of RAM. https://lnkd.in/etaqmVrq

  • ClickHouse is very proud to have our own Data Scientist Ally (McNulty) Godine speaking in New York about our AI-first internal data warehouse that she uses on a daily basis. This will be a great session to learn about how you can leverage AI in your own workflows. To join us in person RSVP here: https://luma.com/xf3wghdh

    View profile for Ophelia S.

    On Thursday, September 17th, we're bringing together 100+ NYC data engineers building production systems in the age of AI. Data Engineer Things NYC Meetup at Capital One is officially happening, and we put together an incredible lineup: Talk 1: Building Data Products for the Age of AI Tajbik Sheikh & Roberto Sánchez Ávalos (Capital One) on how their engineering teams architect production data products when upstream AI requirements shift every week. Talk 2: Agentic Data Science in Practice: Owning a Product-Led Growth model, and the AI layer that runs it Ally (McNulty) Godine (ClickHouse) on operationalizing agentic workflows and managing the underlying data infrastructure powering modern PLG. Huge thanks to Capital One, ClickHouse, and TRM Labs for backing this community and sponsoring us. Grab your spot here: https://luma.com/xf3wghdh P.S. Room capacity is strictly capped so we don't pack the venue past the fire code. Grab your ticket before the RSVP list closes.

    • No alternative text description for this image
  • Engineers across ClickHouse use Claude Code to ship faster. "We built our own AI agents in ClickHouse that teams interact with directly, including an agent in the SQL console and an AI SRE. We use Claude Code to build and iterate on these agents themselves. The tooling that powers our customers' AI experiences is, in part, built with AI" - Alexey Milovidov "The prototype for clickhousectl was built in a few hours using Claude Code. Four months later, we've shipped 26 versions of clickhousectl, where 99% of the code is written by Claude Code." - Alasdair Brown

    View organization page for Claude for Business

    153,127 followers

    We talked to more than a dozen fast-growing startups about how they build with Claude Code, and found five core practices they've adopted. As a result, ClickHouse now ships 30% more features than before, Omni increased engineering productivity 2-3x, and Clay automated its entire bug triage process. Read the full guide: https://lnkd.in/gA9UQf5M

  • ClickHouse reposted this

    I wanted to make ClickHouse & ClickHouse Cloud more approachable for agents, and a CLI is the best tool for coding agents. Typically, you'd discuss it, make a case for the effort, design it, and schedule the build. Instead, I worked with Claude Code in a few spare hours across 3 days to build a prototype. When it was ready, I recorded a video walk through and shared it with the team. Showing a real thing makes the case better than I could ever argue, and with Claude Code, I could build that prototype without taking effort away from my day job. It got people excited, so I moved ahead and built the real thing; along with Claude, I put together the scope, architecture, design, and created a detailed implementation plan. By the end of the first day, I had detailed documentation, milestones and test plans ready to go. The bulk of the core work was completed using a dynamic workflow orchestrated by Claude against the plan. After the second day, I had a working CLI that covered 90% of Cloud operations and gave a great local experience for open source. Over the next 2 weeks, I worked with Claude Code to get the details right. I refitted all my workflows to use the CLI, and enlisted a small group of teammates to use it, too. Every error, point of friction, and unclear help was raised as an issue, then investigated and fixed by Claude. It took 3 weeks to go from idea -> prototype -> public release. The outcome has been fantastic; thousands of users using it every day, including some of our largest enterprise customers, and in 4 months there's been only 1 bug report. Rather than fixing bugs, we can focus on feature requests and user/agent experience. We've shipped customer-requested major features within an hour of the request. Claude monitors usage telemetry for malformed commands, or incorrect usage, and we run automated evals to optimize the user-facing details - command names, structure, help, etc. When we release those changes, Claude analyses how those changes affect success rates, and we capture that intelligence to re-use for future features. Claude Code is responsible for 99% of the code in clickhousectl. My job is to understand what needs to be done, define what good looks, and validate the outcome. 'Is this worth building?' isn't really a question anymore, everything can be built, my focus shifts to 'Is this worth shipping?'

    View organization page for Claude for Business

    153,127 followers

    We talked to more than a dozen fast-growing startups about how they build with Claude Code, and found five core practices they've adopted. As a result, ClickHouse now ships 30% more features than before, Omni increased engineering productivity 2-3x, and Clay automated its entire bug triage process. Read the full guide: https://lnkd.in/gA9UQf5M

  • We've seen a lot of conversation around the "observability wars" and the idea that ClickHouse might be winning them. We're humbled, but declaring victory would be premature. ClickHouse has become a common foundation for observability products, particularly for storing and querying telemetry at scale. We're proud of that. But a database is one layer of an observability system. Collection, workflows, visualization, alerting, and investigation matter too, and there's plenty we still need to build. For observability as a whole, the work isn't done. https://lnkd.in/e6YYrcX4

  • A 512 KiB read buffer was quietly sending every query response to .NET’s large object heap. 🧹 ClickHouse.Driver 1.3 lowers the default to 8 KiB, alongside a broader set of improvements delivered since 1.0. - Over 80% lower per-query allocation across 1,000 small SELECTs - Gen 2 collections eliminated in the same benchmark - More than 90% less total GC pause time - Type-safe POCO reads and writes - Official EF Core support, including bulk inserts and migrations https://lnkd.in/eqPsnt93

  • We’re partnering with Striim to give enterprises a continuous path from Oracle, SQL Server, Snowflake, and other operational systems into ClickHouse. Striim captures inserts, updates, and deletes as they happen, processes them in flight, and delivers them directly into ClickHouse for analytics, applications, observability, and AI. Together, we’re closing the gap between when something changes in the business and when that change becomes available for analysis.

    View organization page for Striim

    23,510 followers

    ClickHouse is fast. The data feeding it should be too. When operational data is still waiting upstream for the next batch, even a fast query can return an outdated answer. That’s why Striim and ClickHouse are partnering: to give enterprises a continuous path from Oracle, SQL Server, Snowflake, and other operational systems into ClickHouse. Striim captures inserts, updates, and deletes as they happen, processes them in flight, and delivers them directly into ClickHouse for analytics, applications, observability, and AI. The result is fast analysis grounded in what’s happening across the business now, giving customers a stronger foundation for building real-time data systems at scale. We’re proud to share what we’re building together. 🔗 Read the announcement: https://lnkd.in/giHdvQ6z

    • No alternative text description for this image

Similar pages

Browse jobs