Introducing ClickStack Cloud: Serverless observability powered by ClickHouse<br>Open searchOpen region selectorEnglish<br>Japanese

47.6kSign inGet started

->Scroll to top

BackBlog<br>Product<br>Copy pageCopied!More actionsView as Markdown Open this page in Markdown<br>Open in ChatGPT Ask questions about this page<br>Open in Claude Ask questions about this page<br>Open in v0 Ask questions about this page

Introducing ClickStack Cloud: Serverless observability powered by ClickHouse

Mike Shi<br>May 27, 2026 · 9 minutes read

Summary

ClickStack Cloud is a fully managed observability service built on ClickHouse, designed for teams that want ClickHouse-powered observability without operating the underlying infrastructure.

Teams point their OpenTelemetry Collector at a managed OTLP endpoint and can immediately explore logs, metrics, and traces in the ClickStack UI, with ingestion, buffering, scaling, and storage handled automatically.

During private preview, we are building automatic schema tuning based on query patterns, with dedicated query compute for agentic workloads planned after preview completes.

Today, we’re announcing the private preview of ClickStack Cloud , a turn-key observability offering built on ClickHouse.

ClickStack Cloud is designed for teams that want the performance, scale, and cost efficiency of ClickHouse for observability, without having to operate their own observability infrastructure.

Send OpenTelemetry data to a managed OTLP endpoint, then explore logs, metrics, and traces in the ClickStack UI. Teams can start investigating telemetry without managing collectors, sizing infrastructure, making scaling decisions, designing schemas, or becoming ClickHouse experts first.

If you want to use ClickHouse for observability, ClickStack Cloud is intended to be the default path: send telemetry data, start investigating, and let the platform handle the operational complexity underneath.

What to try out ClickStack Cloud?<br>If you’re interested in trying ClickStack Cloud, please sign up for the preview program.<br>Sign up<br>Why ClickStack Cloud #

Observability data are a natural fit for ClickHouse.

Logs, metrics, and traces are high-volume, high-cardinality, time-series-heavy datasets. Teams need to search across raw events, aggregate quickly, retain more data for longer, and correlate incidents with what is happening across their systems and business.

ClickHouse has already become a foundation for many modern observability architectures because it can deliver fast queries over large volumes of telemetry at a fraction of the cost of traditional approaches. ClickStack brought that power into a complete observability experience with OpenTelemetry-native ingest and a purpose-built UI.

ClickStack Cloud gives teams a fully turn-key way to use ClickStack, backed by ClickHouse Cloud, without having to operate the underlying ingestion, storage, or query infrastructure themselves.

Send OpenTelemetry data. Start observing. #

With ClickStack Cloud, users send OpenTelemetry data to a managed endpoint. From there, ClickStack Cloud handles ingestion, buffering, scaling, storage, and query serving behind the scenes.

In practice, setup can be as simple as pointing your OpenTelemetry Collector at a ClickStack Cloud ingestion endpoint once you start your new ClickStack Cloud service:

1exporters:<br>2 otlphttp:<br>3 endpoint: https://your_service.otel.us-east-2.aws.clickhouse.cloud:4318<br>4 headers:<br>5 authorization: Bearer ${CLICKSTACK_CLOUD_TOKEN}

Once data is flowing, users can explore their logs, metrics, and traces all from the ClickStack UI, with integrated authentication and RBAC.

Teams can just focus on understanding and operating their production systems, not operating the systems that store and query their telemetry.

A fully managed ingestion layer for OpenTelemetry #

The goal is a simple user experience. The hard part is making it scale seamlessly behind the scenes.

Observability traffic is bursty by nature. Incidents, deployments, cron jobs, customer behavior, and new instrumentation can all quickly change telemetry volume. A managed observability service needs to absorb those changes without asking users to resize infrastructure or debug ingest bottlenecks.

That is where ClickStack Cloud’s managed ingestion layer comes in. Users send telemetry to a managed endpoint, and ClickStack Cloud handles the ingestion path behind the service: buffering, scaling, storage, and delivery into ClickHouse.

Under the hood, telemetry is buffered through a durable event queue backed by object storage. A scalable ingestion layer then allocates resources based on incoming traffic patterns and ingestion pressure.

For users, the experience stays simple: send OpenTelemetry data to ClickStack Cloud and let the platform manage the path from ingestion to queryable telemetry.

What we are building during private preview #

ClickStack Cloud is entering private preview with managed ingestion, a serverless query experience, and the ClickStack UI...