Meridian is currently the #1 product launching today on Product Hunt. We have reached 376 points, and Product of the Day is now within reach.

We spent the past three months building Meridian, an open-source, local-first AI work journal that captures the work behind your work and turns it into clear timelines, worklogs, and daily updates.

The response so far has meant a great deal to our team, but the launch is not over yet. If you believe in what we are building, please upvote Meridian, leave a comment, or share the launch with someone who might find it useful. Every contribution helps us protect the top position and reach this milestone.

Support Meridian: https://www.producthunt.com/prod...

A useful worklog should not just sound polished. It should be grounded in evidence from the actual workday.

Meridian runs locally, builds a timeline from your development activity, matches that context to open Jira and GitHub tickets, and drafts updates for you to review before anything is shared.

We re launching today and would especially value feedback on:

We used to end the day by asking Claude Code something like:

Can you write my daily update based on what I worked on today?

The problem was that Claude Code only knew about the context it had seen.

Meridian is currently #1 on Product Hunt, and we are just 20 points away from becoming Product of the Day.

We have spent the past three months building an open-source, local-first AI work journal that helps developers capture the work behind their work, including investigations, technical decisions, unexpected problems, and everything that often disappears from daily updates.

Thank you to everyone who has taken the time to try Meridian, support our launch, and share Meridian. We are incredibly close to this milestone, and every bit of continued support matters.

Please help us cross the final 20 points and try Meridian.

Thank you to everyone who has taken the time to try and support Meridian. We re building it fully open source, and we need your continued support to stay at the top. Please be honest with us so we can keep improving.

Product Hunt: https://www.producthunt.com/prod...

As developers, we d often reach the end of the day and try to write our daily updates.

The problem was that we could remember the big things we worked on, but not all the context around them.

We d forget:

1. what we spent time debugging

2. why we made certain decisions

3. which issues came up unexpectedly

4. how much time went into code reviews

5. the small fixes and investigations that never made it into Jira

6. all the context behind a commit or PR

We built Meridian in public because software that captures your work should never operate as a black box. Developers deserve to see how their activity is processed, decide what gets included, and review every update before sharing it.

Meridian runs locally, organizes development activity into a timeline, connects work to Jira and GitHub tickets, and drafts clear worklogs for your approval. It is MIT-licensed and free for individual developers.

As one of Meridian s makers, I want open, private, user-controlled software to become the standard, not the alternative.

GitHub: https://github.com/Meridiona/mer...

Three months ago, my co-founder and I quit our jobs to build Meridian full-time. We believe developers should be able to inspect the software that captures their work, control what it includes, and approve every update before it is shared.

Meridian is an open-source, local-first AI work journal. It runs on your device, captures development activity, and drafts clear worklogs and updates for tools like Jira. Nothing leaves your device until you approve it.

As one of Meridian s makers, this is the standard we re building toward: transparent, user-controlled software that developers can trust. Meridian is MIT-licensed and free for individual developers.

We re at the top of the table today, and your support could help us stay there. I d also love to hear from other makers: what would make you trust an AI work journal?

We noticed this happening constantly while building Meridian.

Someone would ask for an update and we d have to think:

Wait what did I actually do today?

We could remember the main task.

Honestly, the ranking was exciting, but the interesting part was everything that happened behind it.

We ve spent the last few months building Meridian, and today was the first time we put it in front of a much larger audience.

A few things surprised me:

People cared about the problem more than we expected
The best feedback came from people who had never heard of us
Getting attention is much easier than keeping it
A launch gives you a very different kind of product feedback
We built it quickly turns into now we have to prove it