ClickHouse. Cloud services, state, and connection endpoints.
Connect your ClickHouse Cloud organization to map its services into the context graph, including state, tier, region, version, and replica sizing. Agents can monitor service health, catch stopped or degraded services, and correlate your analytical database with the rest of your infrastructure.
Join the waitlistIn the graph.
The ClickHouse resource types Polylane syncs, with their edges, config, and history.
Service The tools agents get.
What an agent can do with ClickHouse mid-investigation. Every call lands in the thread transcript, cited.
clickhouseApi Call any ClickHouse Cloud API endpoint that lacks a dedicated tool
clickhouseListServices List ClickHouse Cloud services with state, sizing, version, and endpoints
clickhouseGetMetrics Read live ClickHouse Cloud service metrics (CPU, memory, connections, queries) from the Prometheus endpoint
Questions.
Is Polylane an AI SRE for ClickHouse?
It's what most people mean by the term: agents that keep your ClickHouse resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in ClickHouse?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.