3
26 Comments

Building Kelops β€” simple log monitoring for solo devs and small teams ($10/mo)

Hey! πŸ‘‹

I'm building Kelops β€” a log monitoring and analysis service for developers who don't need (or can't afford) the complexity of Datadog, New Relic, and similar observability platforms.

The problem: if you're a solo dev or a small team, you don't need 50 dashboards and a $500/mo bill. You just need to know when something breaks β€” without drowning in noise.

Important: this isn't meant to compete with giants like Datadog β€” I'm not trying to match them feature-for-feature. Kelops is for people who want a simple tool with no complex setup, not a full-blown observability platform.

What's already built:
Ingest API β€” send logs from your apps
Log explorer UI β€” search and filter logs

What's in progress:
Traces β€” follow a request's path through the system
Log stream analysis, to surface only what actually matters
AI-based error grouping β€” recurring bugs get clustered automatically
Notifications in Telegram and Slack: error spikes, new error types, service downtime, periodic summaries
Authentication (not there yet)

Focus: fast setup β€” minimal configuration so you're getting logs in within a couple of minutes, not half a day of config wrangling.

Stack: Go + Kafka + ClickHouse on the backend, Next.js on the frontend β€” built for scale, priced for solo devs.

Pricing: ~$10/month. That's it. No enterprise tiers, no "contact sales."

There's already a live site, but it's still under active development β€” it may go down, and there's no auth yet, so think of it as a preview rather than a stable product. https://kelops.dev

Would love feedback on:
Which notification channels matter most to you β€” Telegram, Slack, email, something else?
What's the #1 thing stopping you from setting up log monitoring right now?

on September 24, 2026
  1. 2

    Have early users shown a willingness to replace their current monitoring setup with Kelops, or is the strongest signal so far agreement with the β€œsimpler and cheaper” positioning?

    1. 1

      Good question β€” honestly still early, so right now it's more the second: people nodding along to the 'simpler and cheaper' pitch rather than proven switching behavior yet. That's actually part of why I'm posting here β€” trying to find out if that agreement holds up once there's something to actually try.

      1. 1

        That gap between agreement and actual switching is the interesting part. Could be useful to compare notes on it by email sometime, if you’re open to it.

        1. 1

          That gap between alignment and switching is exactly the most intriguing part. I'd love to compare notes! Hit me up in my Twitter/X DMs (link is in my profile), or let me know yours so we can connect.

          1. 1

            I’m not on X β€” email would be easier. You can reach me at hello@beryxa.com.

  2. 2

    Love this angle. Building Xstream4K right now so this hits close to home β€” what made you look into it in the first place?

    1. 1

      Thanks! Mostly just came from my own experience β€” wanted something simple.

  3. 1

    How did you decide this was worth building in the first place?

  4. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  5. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  6. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  7. 1

    Appreciate the honesty here, most people only share the wins.

  8. 1

    Really relatable. How much time do you put into this each week?

  9. 1

    Curious how long it took before you saw the first real results?

  10. 1

    Curious how long it took before you saw the first real results?

  11. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  12. 1

    Good write-up. What would you do differently if you started again?

  13. 1

    Solid lesson. Which channel has worked best for you so far?

  14. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

  15. 1

    Great breakdown. What feedback have you had from early users?

  16. 1

    Really relatable. How much time do you put into this each week?

  17. 1

    Nice progress. What is the next thing you are focusing on?

  18. 1

    Curious how long it took before you saw the first real results?

  19. 1

    Thanks for writing this up. Bookmarking it for later.

  20. 1

    Thanks for writing this up. Bookmarking it for later.

  21. 1

    Thanks for writing this up. Bookmarking it for later.