Back to News
Advertisement
llureilly1 about 9 hours ago 3 commentsRead Article on github.com

FR version is available. Content is displayed in original English for accuracy.

I've built a type-safe semantic layer in code, for ClickHouse. If you're building analytics off ClickHouse in TypeScript, I would love your feedback.

With hypequery there is no platform to adopt, no YAML sprawl. It runs where your app runs.

Key features:

- Define metrics once, reuse them everywhere: Declare dimensions and measures in one place and then pull from the same source of truth.

- Compiles to ClickHouse SQL: No service, no proxy, no extra runtime to deploy. It's a library that generates SQL and runs where your app runs.

- Multi-tenancy & Authentication ready: Cross-tenant queries are blocked at the query layer, helpers to plug into your existing auth.

- Agent-native: A dataset is a declared set of dimensions and measures, so it doubles as an allowlist. Includes an MCP server to hand an LLM a typed catalog to query.

- Runtime HTTP entry point: serve() exposes any dataset as an endpoint, so the same type-safe definitions back your dashboards and your API.

Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 75 words in the discussion.

Trending Topics

#production#biggest#hurdle#early#tried#epic#hardest#part#getting#teams

Discussion (3 Comments)Read Original on HackerNews

hypercain•41 minutes ago
just tried it out, it's epic!
Abushan•about 7 hours ago
hardest part getting teams to trust it in production. What is the biggest adoption hurdle for early users?
lureilly1•about 6 hours ago
The biggest hurdle is that it’s still a young library sitting in the core read path for production analytics. That naturally requires early adopters who believe in the direction, are willing to use in real systems, and can be patient whilst gaps are closed.

The base is solid though: the underlying query builder has 10k+ weekly downloads and production usage. The newer surface is the semantic layer itself.