Nicheloom visits: 58,069 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

BetterDB

OSS Valkey/Redis monitoring with historical data

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hey HN,I'm Kristiyan, former Engineering Manager for Redis' Visual Developer Tools (including Redis Insight). I built BetterDB because Valkey is growing fast but lacks proper observability tooling.BetterDB is a monitoring platform for Valkey (and Redis) that focuses on what existing tools miss:Historical persistence – Slowlog entries disappear when the buffer fills. BetterDB persists them so you can see what queries were running at 3am, which clients were connected, and what anomalies were detected — not just current state.Pattern analysis – Stop scrolling through raw slowlog entries. BetterDB aggregates them and shows you "HGETALL user:* is 80% of your slow queries" — actionable insights, not raw data.COMMANDLOG support – Valkey 8.1 introduced COMMANDLOG for tracking large requests/replies, not just slow ones. That 50MB MSET that's killing your network? Now you'll see it. BetterDB is the first monitoring tool to support it.Anomaly detection – Automatic baseline learning with Z-score analysis across 15+ metrics. Know when something's off before your users do.Prometheus-native – 99 metrics exposed at /prometheus/metrics. No new dashboards to learn — plug into your existing Grafana/Datadog setup and get Valkey-specific data you can't get elsewhere.Cluster-aware – Automatic node discovery, topology visualization, per-slot metrics, and aggregated slowlogs across all nodes.ACL audit trail – Track who accessed what, when. ACL denied events by reason and user, persisted for compliance and debugging.Memory & Latency Doctor – Built-in diagnostics that tell you what's wrong, not just that something is wrong.The core is MIT licensed. Pro features (key analytics, AI assistant) live in a separate proprietary/ directory under a source-available license. During beta, use BETA-TEST to unlock everything free.Website: https://betterdb.comGitHub: https://github.com/BetterDB-inc/monitorRelease notes: https://github.com/BetterDB-inc/monitor/releasesDocs: https://docs.betterdb.comQuick start: docker pull betterdb/monitor:latest docker run -d -p 3001:3001 -e DB_HOST=your-valkey-host -e BETTERDB_LICENSE_KEY=BETA-TEST betterdb/monitor:latest All ideas are welcome and all feedback is important — don't be shy! Star the repo if this is useful, open issues for bugs or feature requests, or just drop a comment here. What pain points do you have with your current Valkey/Redis monitoring setup?

HN · launched Jan 23, 2026 · 6 upvotes (top 75%) · 0 views

Niche: web and application performance monitoring tools · 66 launches, 6 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Observability & eval
  • Developer
  • Not AI
  • Commercial product

Source listing ↗

Could you build this?

Partial The dashboard and basic Redis INFO command polling are vibe-codeable, but non-intrusive high-frequency metrics collection and command profiling across enterprise Valkey/Redis clusters require deep database systems expertise.

What it would actually take: A production-grade Valkey/Redis monitoring tool requires a low-overhead daemon (in Go or Rust) that polls `INFO`, parses the slowlog and latency monitor, and samples keyspaces without degrading sub-millisecond Redis latency. The backend requires a dedicated time-series database (e.g., VictoriaMetrics or TimescaleDB) to store high-resolution history without exploding memory. Deep domain knowledge of Redis internals (memory fragmentation, single-threaded event loop impact of monitoring commands) is required.

Discussion

1 comment analyzed.

Concerns raised: Periodic patterns not explicitly modeled (daily batch jobs, cache warming), Cardinality explosion risk with per-key metrics, Alert noise from bursty workloads

Feature requests: Configurable expected variance windows for scheduled events, Integration with deployment events for pattern detection, Better handling of periodic/scheduled workload patterns

Competitors

Other products that read as similar to this one : 184 launches clear the similarity bar, closest 8 shown.

Attention rank: #162 of 185 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 83 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.