// the find
514-labs/moosestack
The agent harness for building analytics into your app on top of ClickHouse, Redpanda and other high-performance analytical infrastructure
MooseStack was a developer framework for building analytics applications on top of ClickHouse, Redpanda, and Temporal — letting you declare tables, streams, and APIs in TypeScript or Python while the CLI wired up the infrastructure. It's now officially end-of-life, killed by its own benchmark data showing that coding agents perform worse with the abstraction layer than without it.
The honest self-deprecation in the README is genuinely admirable — they published the benchmark table showing agents did worse with Moose on complex tasks and shut it down rather than spinning a narrative. The underlying Rust CLI includes a custom Kafka broker (devkafka) and Redis implementation (devredis) for local dev, which is a serious engineering investment for developer experience. The schema migration system for ClickHouse filled a real gap, since ClickHouse ALTER TABLE semantics are painful to manage by hand. The e2e test suite is thorough — backward-compatibility tests, incremental compilation tests, agent integration tests — more coverage than most framework projects bother with.
It's dead — the README says so in the first paragraph, so adopting it is building on a foundation that won't get fixes or security patches. The abstraction layer was the whole value proposition and it demonstrably made agent-driven workflows slower and more expensive on the benchmarks they ran themselves. Self-hosting the full stack (ClickHouse + Redpanda + Temporal + Redis + the Moose runtime) is a lot of operational surface area for what is essentially a developer convenience layer. At 585 stars and 31 forks, the community was always thin, which means limited third-party resources when you hit edge cases.