OpenLog

Turn product signals into clear decisions

Visit Website
January 2, 2026 Why I started building OpenLog (early feedback welcome)

Hey Indie Hackers,

I recently started working on OpenLog after running into the same problem over and over while building products.

Feedback, logs, user messages, issues, signals are everywhere.

But deciding what actually deserves attention is surprisingly hard.

Most tools help you collect more data.

I wanted something that helps with clarity.

OpenLog is my attempt to bring product signals (feedback, logs, sessions) into one place so decisions feel calmer and more intentional, not reactive.

This is very early.

I’m onboarding a small group of beta users and prioritizing feedback over growth right now.

If you’ve built or worked on a product:

– How do you currently decide what to fix or build next?

– What signals do you trust the most?

– Where does it usually break down?

Would genuinely love to learn from this community.

Happy to share more details if useful.

Comment

About

OpenLog exists because most teams struggle with deciding what actually deserves attention. Feedback, logs, and signals are everywhere, but clarity is rare. I wanted a way to see real product signals in one place and act