Loglybase
Keep your audience informed with customizable changelog page
Hey Indie Hackers 👋
A few weeks ago, I launched Loglybase — a platform that helps makers and teams share their product updates with clarity and style.
Today, I’m excited to announce that Loglybase is now open source! 🎉
You can explore the code, use it for your own projects, or even contribute to make it better.
I decided to open source the project to make it more transparent, accessible, and community-driven. The hosted cloud version will still be available at https://loglybase.com for those who prefer a ready-to-use experience.
🔗 GitHub: https://github.com/enviallabs/loglybase
A couple of days ago I launched Loglybase, a simple way to create and share changelogs for your projects. The response has been really motivating, and I’ve kept working to make the product a bit better every day.
Today I pushed out the first update — it’s not huge, but it makes changelogs more useful and a little nicer to use.
👉 You can check out the full update here: https://changelog.loglybase.com
It’s still early days for Loglybase, but I want to keep iterating fast and sharing progress openly. Even small improvements like these move the project closer to my goal: making changelogs effortless and valuable, both for teams and their users.
What’s the smallest feature you’ve shipped that ended up making the biggest difference for your users?
👋 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!
-
1
Looks interesting
-
1
Pretty cool, updates usually get ignored but making them look nice could actually make people read them 👌.
-
1
Thank you very much for your feedback.
I agree with you and I will try to make Loglybase help achieve this.
-
-
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
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.
-
-
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
Thank you very much for your feedback. I will try to make Loglybase a worthy product for developers.
-
-
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
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.
-
-
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
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.
-
Comment