Show HN: WaveHouse – Supabase for ClickHouse
WaveHouse is an open-source Go binary that bundles fast durable ingest, row/column-level security, and realtime streaming for ClickHouse.
WaveHouse, a self-described "Supabase for ClickHouse," launched on Hacker News on August 20, 2026, as an open-source project built to reduce the infrastructure overhead of using ClickHouse in production applications.
The project was posted by HN user ericandr as a Show HN submission. WaveHouse ships as a single Go binary designed to be deployed alongside an existing ClickHouse instance. According to the Show HN post, it bundles three capabilities that developers typically have to wire together separately: fast, durable data ingestion; row-level and column-level security with role management; and realtime data streaming.
The team says the project grew directly out of their own experience building an IoT telemetry solution. As described in the Show HN post, inserting data quickly and durably into ClickHouse without standing up a message queue like Kafka was a recurring pain point, adding significant complexity for teams that want to use ClickHouse's analytical query capabilities on smaller or faster-moving projects. Exposing ClickHouse query results in a UI compounded the problem, requiring a dedicated backend API layer to manage authentication and permissions.
The Supabase comparison is deliberate in framing. Supabase positions itself as a backend-as-a-service layer on top of PostgreSQL, abstracting away auth, storage, and realtime subscriptions. WaveHouse applies the same pattern to ClickHouse — a column-oriented database commonly used for analytics, observability, and high-throughput event data — packaging the surrounding scaffolding into one deployable unit rather than requiring teams to compose and maintain it themselves.
The project is listed as open-source, and the team is actively soliciting feedback on features and improvements, per the Show HN post. No funding, team size, or company details were disclosed in the submission. The roadmap beyond current capabilities was not specified, though the post notes the team plans to continue adding features to the project.
No comments yet — start the thread.