Meridian is an open-source AI work journal that runs entirely on your device. It writes your work up in plain English as the day goes, so by the end of the day you have a summary of everything you did. Meridian automatically drafts your updates for your project management tools like Jira, ready to post once you approve them. Do the work. Let the remembering take care of itself. MIT-licensed, free.
Forum Threads
We were featured three times in the Product Hunt newsletter! 🎉
We were featured three times in the Product Hunt newsletter, including once before our launch day had even ended.
Meridian finished as the #1 Product of the Day, and we are now aiming for the top of the August monthly leaderboard.
Meridian is an open-source, MIT-licensed, local-first AI work journal built to ensure meaningful work does not go unnoticed. It runs on your device, captures real work activity, organizes it into a clear timeline, connects it with GitHub and Jira, and drafts worklogs and project updates for review and approval.
We want to make work more visible without turning productivity software into surveillance. Meridian keeps the underlying context on the user s device, gives them control over what gets shared, and remains open source so anyone can inspect how it works.
We Got 400 Downloads on Day One. Can Meridian Top the Month?
https://www.producthunt.com/prod...
Meridian finished as the #1 Product of the Day on Product Hunt and crossed 400 downloads on its first day.
We built Meridian because meaningful work often disappears between debugging sessions, unexpected fixes, and updates written from memory. It is an open-source, MIT-licensed, local-first AI work journal that runs on your device, organizes your activity into a clear timeline, and drafts worklogs and project updates for you to review and approve.
Now we want to top the August monthly leaderboard, and we need your support. Please upvote Meridian on Product Hunt, download it, and star the GitHub repository.
If you want me to share Meridian s daily download numbers, comment below and I will post them.
I repeatedly watched our projects miss deadlines, cut corners in SDLC, and eventually get rebuilt
I learned that as software gets easier to build, coordination becomes the bottleneck.
At my previous work, I repeatedly watched our projects miss deadlines, cut corners in the SDLC, and eventually get rebuilt - not because engineers couldn t build them, but because teams discovered too late that reality had diverged from the plan.
I also noticed smaller teams consistently moved faster. Not necessarily because they had better engineers, but because context travelled faster: everyone knew what changed, what was blocked, what had been tried, and why.
After years building AI-native systems for enterprises and leading engineers, I ve seen the same pattern repeatedly: engineering slows down when context gets fragmented and feedback arrives late.
RunEvr
@akarsh_hegde This is a really interesting approach! I especially like the idea of taking the “remembering and reporting” part out of the workflow so people can focus on the actual work. And running entirely on-device with no account is a big plus for privacy. Great concept - wishing you a successful launch!
Meridian
@adana Thank you for the support! Really appreciate it. Privacy shaped every decision we made, which is why Meridian works on-device and keeps the user in control
Huge congrats to you and the team launch, Akarsh! I really like the problem you’re tackling, the invisible, unplanned work that happens between tickets and commits is often where the real story of a project lives.
The privacy-first and open-source approach makes the product even more compelling, especially for something that’s essentially building a memory layer around how people work.
Wishing you and the team all the best.
Meridian
@davemadeit Thank you for the thoughtful support! We built Meridian to make that invisible work visible without compromising privacy or control. Your encouragement means a lot to the team.
Meridian
@davemadeit Thank you for the thoughtful support! It means a lot to our team.
screenpipe (YC S26)
Louis here, founder of @screenpipe 👋 Fun to see Screenpipe listed under “Built With.” Looking through the repository, Meridian’s capture layer uses forked screenpipe-screen and screenpipe-a11y for screen capture, OCR, and accessibility.
One important housekeeping item: the MIT Screenpipe base requires preserving its copyright and license notice, and I couldn’t find that notice in the v1.90 app bundle or release materials. Could you add it and confirm that the private fork contains only the pre-commercial-license MIT base plus your own changes?
Congrats on the launch. Happy to resolve this privately too.
Meridian
@louis030195 Thanks for bringing this to our attention! Screenpipe has been a major inspiration, and we take the licensing requirements seriously. We are reviewing the v1.90 app bundle, release materials, and the full history of our private fork to verify it contains only the MIT-licensed base plus our own changes. We’ll add any missing copyright and license notices, publish an update once confirmed, and would be happy to coordinate privately to resolve this.
Congrats on the launch, really like the product! As a team lead this hits a real problem: the debugging and "quick help" work that never makes it into reviews. Local-first with draft-then-approve is exactly the right trust model. Trying it with my team this week, good luck! 🚀
Meridian
@abu_tareq Thank you for the support! Really appreciate it. Let me know how it goes with your team.
Great idea! End-of-day updates feel less like a task and more like something that just happens in the background. Definitely something I’d find useful in my daily workflow.
Meridian
@ananya_hegde2 Thank you! As one of Meridian’s makers, I’m glad this would fit your daily workflow. Which updates would you most want Meridian to handle automatically?
SocialBu
Congrats on the launch! Capturing unplanned work and context switching is such a pain point when drafting end-of-day updates or standup notes. Love the local-first, BYO-AI approach. Looking forward to testing it out! 🚀
Meridian
@bilal_niaz Thank you for the support! Really appreciate it. Keeping Meridian local-first and letting developers choose their AI provider were important decisions for making daily updates useful without giving up control of their data.
Nice one, congrats on #1. Local-first is the right call for a work journal most devs won't touch a cloud tracker for this. Haven't tried it yet but the concept lands. Good luck!
Meridian
@ugur_cakaroglu Thank you for the support! Really appreciate it. We’d love to hear your feedback once you’ve tried Meridian.