9
11 Comments

Building Loglybase: a better way to share product updates

πŸ‘‹ Hey Indie Hackers,

I’ve been building a new project called Loglybase β€” a simple, customizable platform for creating beautiful changelog pages.

The idea came from a common problem: product updates often get buried in plain text release notes or never reach users at all. I wanted to make changelogs something more than just a list of fixes β€” a clear, engaging way to communicate progress and build trust.

With Loglybase you can:

  • Create branded changelog pages in minutes

  • Use flexible editor blocks (text, code, images, video, and more)

  • Add a custom domain for your updates

  • (Soon) get AI assistance to write posts faster

I’m currently polishing the first release and would love your feedback πŸ™Œ

πŸ‘‰ What do you usually use for sharing updates with your users?
πŸ‘‰ Do you think changelogs can actually improve user engagement?

Excited to hear your thoughts!

posted toAvatar for product Loglybase
Loglybase
  1. 1

    Looks interesting

  2. 1

    Pretty cool, updates usually get ignored but making them look nice could actually make people read them πŸ‘Œ.

    1. 1

      Thank you very much for your feedback.

      I agree with you and I will try to make Loglybase help achieve this.

  3. 1

    I like the focus on making changelogs more engaging - most updates do get buried or ignored. I’m building a finance dashboard right now and one thing I keep thinking about is how to show progress in a way users actually notice.

    Curious, how do you plan to keep people coming back to check these changelogs regularly?

    1. 1

      Thank you very much for your interest.

      In the next few days I will be adding a widget that can be integrated into a website or app, and I also plan to spend some time on discussions and update notifications.

      I believe that if we manage the changelog properly, and also have discussions about updates, users will be more interested in following the changelog and the product itself.

  4. 1

    Thanks so much for sharing your thoughts! Totally agree β€” many teams either skip changelogs or keep them buried in docs nobody reads. My hope with Loglybase is to make updates more visible and engaging, so users actually feel connected to the product’s progress.

    1. 1

      Thank you very much for your feedback. I will try to make Loglybase a worthy product for developers.

  5. 1

    Great job man! Loving the design of what I've seen so far.

    I'm currently getting into entrepreneurship and I'm curious about the effect of change logs is on the usual success metrics eg. revenue, customer experience/satisfaction, etc.? Also does the size of the product or user base matter for this?

    1. 1

      First, thank you for your feedback.

      Changelogs can have a surprisingly strong impact on success metrics, even though the effect is often indirect.

      Changelogs help engage your users in your product, help them understand it, and learn about the functionality they might need. In addition, keeping a product changelog makes your product look more serious, and users can see how your product is evolving and whether it is evolving at all.

      Finally, changelogs can be used to collect feedback from your users, thereby improving the product.

      Speaking of feedback, I plan to add tools for collecting user feedback in the near future.

  6. 1

    I think this is a pretty neat idea. Especially the upcoming widget mentioned in your FAQ on your site! We may consider using the widget once it's released!

    1. 1

      Thank you very much for your feedback. I am glad to hear that you are interested in the product and that you are interested in using it in the future. I will try to add the widget and many other things as soon as possible.