Compare
Compare hypequery against the main ClickHouse TypeScript options
These pages are for teams deciding how to structure ClickHouse access in TypeScript. Start with the comparison closest to your current stack, then move into the implementation guides.
Decision focus
ClickHouse-first TypeScript teams
What you get
Tradeoffs, not feature checklists
Best next step
Pick a path, then quick start
Built for real evaluations
Each comparison focuses on what changes when ClickHouse is part of the architecture, not generic query-builder advice.
Linked to implementation
Every comparison page leads directly into the docs and pillar pages so the evaluation can turn into implementation quickly.
Opinionated about fit
The goal is to clarify where hypequery fits well and where a lower-level or more general tool may still be the right choice.
Quick comparison: hypequery vs @clickhouse/client
@clickhouse/client is the right low-level client. hypequery is the better fit when you need generated schema types, reusable query definitions, typed APIs, and frontend consumption on top of ClickHouse.
Open comparison
Quick comparison: hypequery vs Kysely
Kysely is an excellent general TypeScript query builder. hypequery is narrower: it is built for ClickHouse runtime type mapping, schema generation, and reusable analytics APIs.
Open comparison
Next step
Start with the quick start once you know the shape you want
Move from evaluation into implementation with generated schema types and your first reusable query.