This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Git tracks code. eve tracks product. eve is an open source product history layer built on top of Git. Instead of navigating commits and diffs, it organizes completed work into Snapshots that capture what changed, why it changed, how it was validated, screenshots, documentation, and the Git history behind every product change. Snapshots help everyone involved in building the product understand its evolution, while giving future coding agents structured context for continuing the work.
Over the past few years my workflow has changed a lot. I spend much less time writing code myself and much more time reviewing what AI coding agents produce. I realized I cared less about individual commits and more about understanding how the product was actually evolving.
That led me to build eve.
The idea is simple: Git remains the source of truth for code, while eve becomes the source of truth for product history. Every completed feature, bug fix, experiment, or release becomes a Snapshot that records not only the underlying commits, but also the reasoning, validation, screenshots, and other context behind the change.
My hope is that these Snapshots make product evolution easier to understand for everyone involved in building the product, while also becoming a reusable context layer for future coding agents.
It’s completely local, open source, and stores everything alongside your repository.
This is the first public release, so I’d genuinely love feedback, whether it’s on the idea itself, the UI, the data model, or the MCP integration. Thanks for taking a look!
No comment highlights available yet. Please check back later!
About eve on Product Hunt
“Git tracks code. eve tracks product”
eve was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #142 on the daily leaderboard. Git tracks code. eve tracks product. eve is an open source product history layer built on top of Git. Instead of navigating commits and diffs, it organizes completed work into Snapshots that capture what changed, why it changed, how it was validated, screenshots, documentation, and the Git history behind every product change. Snapshots help everyone involved in building the product understand its evolution, while giving future coding agents structured context for continuing the work.
eve was featured in Productivity (655.7k followers), Developer Tools (515.4k followers), Artificial Intelligence (473.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 349.4k products, making this a competitive space to launch in.
Who hunted eve?
eve was hunted by Umut. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how eve stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Umut
Hi everyone! I’m Umut, the creator of eve.
Over the past few years my workflow has changed a lot. I spend much less time writing code myself and much more time reviewing what AI coding agents produce. I realized I cared less about individual commits and more about understanding how the product was actually evolving.
That led me to build eve.
The idea is simple: Git remains the source of truth for code, while eve becomes the source of truth for product history. Every completed feature, bug fix, experiment, or release becomes a Snapshot that records not only the underlying commits, but also the reasoning, validation, screenshots, and other context behind the change.
My hope is that these Snapshots make product evolution easier to understand for everyone involved in building the product, while also becoming a reusable context layer for future coding agents.
It’s completely local, open source, and stores everything alongside your repository.
This is the first public release, so I’d genuinely love feedback, whether it’s on the idea itself, the UI, the data model, or the MCP integration. Thanks for taking a look!