Data platforms

ClickHouse

Fast columnar database for analytics

Overview Context types Tools Use cases Connection Security

Overview

ClickHouse rewards queries that respect the sort key and punishes the ones that do not. Modus mines databases, tables, views, and materialized views so agents write queries shaped for the engine.

What Modus reads

1Database
2Table / View / Materialized View
3Column

You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.

5context types mined

1agent tool groups

1connection method

7security controls

Context types

Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.

Schema metadata
The container Modus is scoped to: what lives inside it, how it is organised, and how much of it is actually used.
Table / view metadata
Names, descriptions, column lists, types, keys, and the join paths Modus observes between objects.
Table / view samples
A small, classified sample of representative rows so agents can tell an ISO date from an epoch, and a status enum from free text.
Column statistics
Distinct counts, null ratios, ranges, and top values per column, so an agent knows which column is the real grain.
Column samples
Representative values per column, redacted whenever classification flags them as sensitive.

Example context item

clickhouse_materialized_view_metadata

analyticsmv_events_hourly

Object: Materialized view · 12 columns
Source: analytics.events_raw
Order by: (tenant_id, event_hour)
Grain: One row per tenant per event per hour

Tools

Tools are granted per skill, never globally. Anything that changes state in ClickHouse is marked as a write and stops for human approval.

SQL Runner
Run governed read queries against the schemas a skill is scoped to. Statement categories (SELECT, INSERT, UPDATE, DELETE, CREATE) are granted per skill, so most agents get SELECT and nothing else.

Common use cases

Teach agents which materialized view already answers the question, instead of scanning the raw table.
Surface the sort key so filters land where the engine can use them.

Connection method

Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.

Username & password

A read-only user, optionally over TLS, against the ClickHouse endpoint you nominate.

Security & governance

Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.

Metadata-first mining

Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.

Scoped selection

You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.

Data classification

Sampled values are scanned for PII, financial, health, credential, and government-ID patterns, then classified as Sensitive, Flagged, or Non-sensitive. Your own overrides win over the defaults.

Group access by sensitivity

Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.

Read-only by default

Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.

Query cache

Repeat read queries can be served from a governed cache with a configurable TTL, cutting warehouse cost and latency without bypassing access controls.

IP allow list

Modus connects from fixed egress IPs you allowlist in your network or cloud firewall, so the warehouse never has to accept traffic from the open internet.

Put ClickHouse to work.

Connect it in minutes and give every agent a governed understanding of what is inside, without moving a single row of data.

Book a demo