wavehouse.dev is built with Starlight, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics and PostHog.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 7 Nov 2026 | |
| JavaScript Frameworks & Libraries2 | ||
| 7.3.8 | 7 Nov 2026 | |
| – | 7 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 7 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
smtp.google.comjeremy.ns.cloudflare.comchin.ns.cloudflare.comv=spf1 include:_spf.google.com ~allgoogle-site-verification=95a4Y43R7vwaQ_J9b-jmKazjyiNrq6cDlUadyCr7rm0# Content Signals (contentsignals.org) — WaveHouse is open source: we want # agents and models to read these docs, index them for search, answer from # them live, and train on them. So every signal is an explicit yes. User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / Sitemap: https://wavehouse.dev/sitemap-index.xml
# WaveHouse > The open-source real-time API gateway for ClickHouse — schema-aware ingest, async batching, real-time streaming, and tiered query caching in a single binary. ## Documentation sets - [Full documentation](https://wavehouse.dev/llms-full.txt): every page concatenated, source-faithful (mermaid, math, asides, components preserved as text). - [Abridged documentation](https://wavehouse.dev/llms-small.txt): only top-level pages and section overviews. ## Getting Started - [Getting Started](https://wavehouse.dev/getting-started.md): Run WaveHouse locally in five minutes — ingest, query, and subscribe to real-time events. ## Why WaveHouse? - [Why WaveHouse?](https://wavehouse.dev/why-wavehouse.md): How WaveHouse compares to direct ClickHouse, Kafka + ClickHouse, and Tinybird — with the failure modes, DIY cost, and feature matrix. ## Architecture - [Architecture](https://wavehouse.dev/architecture.md): System design, data flows, internal packages, and technology stack. ## Ingest Pipeline - [Ingest Pipeline](https://wavehouse.dev/ingest-pipeline.md): How the internal/ingest worker batches events per table into ClickHouse — goroutines, channels, timers, contexts, shutdown, the sweeper, and the path to multi-instance scale. ## Access Control - [Access Control](https://wavehouse.dev/access-control.md): Roles, policies, and row/column permissions — how WaveHouse decides what each caller can read and write. ## Named Pipes - [Named Pipes](https://wavehouse.dev/pipes.md): Pre-defined, parameterized SQL queries with role-based access and built-in caching. ## API Reference - [API Reference](https://wavehouse.dev/api.md): All endpoints, authentication, request/response formats for the WaveHouse API. ## TypeScript SDK - [TypeScript SDK](https://wavehouse.dev/sdk.md): Client SDK — query builder, real-time streaming, codegen. - [SDK Queries](https://wavehouse.dev/sdk/queries.md): Tables, the chainable query builder, pagination, and raw SQL in @wavehouse/sdk. - [SDK Streaming & Live Queries](https://wavehouse.dev/sdk/streaming.md): Real-time SSE streams, client-side filtering, and backfill-then-live queries in @wavehouse/sdk. - [SDK Pipes](https://wavehouse.dev/sdk/pipes.md): Execute and inspect named query pipes with @wavehouse/sdk. - [SDK Admin & System](https://wavehouse.dev/sdk/admin.md): Schema introspection, settings reload, DLQ stats, and health checks in @wavehouse/sdk. - [SDK Reference & CLI](https://wavehouse.dev/sdk/reference.md): Error codes, AbortController, the full API tree, the codegen CLI, and E2E testing with @wavehouse/sdk. ## Configuration - [Configuration](https://wavehouse.dev/configuration.md): Full configuration reference — YAML settings and environment variables. ## Settings Directory - [Settings Directory](https://wavehouse.dev/settings-directory.md): The hot-reloadable half of configuration — roles, policy, pipes, and the config.json keys; reload triggers; and the validate / bootstrap CLI. ## Deployment - [Deployment](https://wavehouse.dev/deployment.md): Running WaveHouse in production: Docker images, releases, environment variables, health checks, and schema setup. ## Upgrading - [Upgrading](https://wavehouse.dev/upgrading.md): Upgrading a WaveHouse deployment between releases: what to export, convert and drain, and what changes for clients. ## Durability & Storage - [Durability & Storage](https://wavehouse.dev/durability.md): What a WaveHouse ingest ack guarantees, why embedded JetStream fsyncs every publish while an external NATS cluster relies on replicas, and how to tell whether your storage substrate can sustain it. ## Behind a reverse proxy - [Behind a reverse proxy](https://wavehouse.dev/reverse-proxy.md): Running WaveHouse behind nginx, Caddy, or a Cloudflare Tunnel: TLS, request-body limits, SSE buffering and timeouts, header/auth forwarding, the client address and trace context, and health probes. ## Development - [Development](https://wavehouse.dev/development.md): Building, testing, linting, project structure, and contribution workflow. ## Claude Code & AI agents - [Claude Code & AI agents](https://wavehouse.dev/claude-code.md): Working with Claude Code in the WaveHouse repo — what ships in .claude/ and .githooks/, how enforcement is layered, and recommended user-level setup.
| – |
| 7 Nov 2026 |