hypequery

The type-safe analytics backend for ClickHouse.

hypequery is an open-source TypeScript semantic layer and type-safe query builder for ClickHouse. Define analytics once, then use the same trusted contract in backend code, multi-tenant APIs, React hooks, and MCP tools for AI agents.

It fits the stack you already have. Generate types from your live ClickHouse schema, model metrics in normal TypeScript, and catch broken tables, columns, filters, and result shapes before production—without another BI server or YAML project.

Quick start · Capabilities · Examples · MCP

One definition, every surface

import { dataset, dimension, measure } from '@hypequery/datasets';

export const Orders = dataset('orders', {
  source: 'orders',
  tenantKey: 'tenant_id',
  timeKey: 'created_at',
  dimensions: {
    region: dimension.string(),
    status: dimension.string(),
    createdAt: dimension.timestamp({ column: 'created_at' }),
  },
  measures: {
    revenue: measure.sum('amount'),
    orderCount: measure.count('id'),
    p95OrderValue: measure.percentile('amount', 0.95),
  },
});

export const revenue = Orders.metric('revenue', {
  measure: 'revenue',
});

That dataset can run in a worker, become a validated HTTP endpoint, power a typed React dashboard, or appear as a bounded MCP tool. Tenant scope and metric meaning stay in one place.

Start in minutes

npm install -D @hypequery/cli
npx hypequery init
npx hypequery dev

Or add only the ClickHouse query builder:

npm install @hypequery/clickhouse

const revenueByRegion = await db
  .table('orders')
  .select(['region'])
  .where('status', 'eq', 'completed')
  .sum('amount', 'revenue')
  .groupBy('region')
  .orderBy('revenue', 'DESC')
  .execute();

No hand-written result interface. No any[]. The result is inferred from your real schema and the query itself.

Built for product analytics

• ClickHouse-native: generated types plus FINAL, LIMIT BY, percentiles, argMax, arrays, CTEs, streaming, and window expressions.
• Governed in code: dimensions, measures, metrics, relationships, and time grains live beside your application.
• Multi-tenant by design: runtime tenant scope fails closed instead of relying on every query author to remember a filter.
• Frontend ready: typed TanStack Query hooks for named queries, metrics, and datasets.
• Agent ready: MCP tools expose approved analytics, not unrestricted SQL.
• Easy to adopt: start with one local query and add the semantic, HTTP, React, or MCP layers only when needed.

Packages

Explore

• What hypequery supports today
• ClickHouse semantic layer
• Multi-tenant analytics
• React hooks
• MooseStack EOL comparison
• MooseStack migration guide

If hypequery saves you from another copied SQL string or drifting metric, a GitHub star helps the next TypeScript team find it.

License

Apache-2.0. See LICENSE.