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).
Flurry
Git-compatible source control with immutable changes
Flurry is an open-source, self-hosted source control system that keeps Git compatibility at the edge and immutable changes at the center. Clone, fetch, and push with ordinary Git; review and land explicit changesets in the browser; work offline with the native fsc client; and connect bounded automation through signed webhooks, statuses, evaluations, and a local MCP server.
Hey Product Hunt — I’m Wess, the solo maker behind Flurry.
I built Flurry because source control has accumulated two kinds of complexity: infrastructure that is hard to own, and collaboration state that is too easy to mutate.
Flurry takes a different path. Git remains the compatibility layer for clone, fetch, and push. Inside Flurry, changes are immutable records, reviews are explicit, landing is atomic, and automation reports evidence without turning the source host into a general-purpose runner.
What’s ready today:
- unlimited public and private repositories on your own instance - browser, Git, and native `fsc` workflows over the same history - immutable changesets, review, approvals, protected landing, issues, wikis, releases, and snippets - signed webhooks, revision statuses, structured automated review, and a local MCP server - Docker-based self-hosting with documented backup and recovery
I’d especially value feedback on one question: does the immutable-changeset model make review and automation easier to reason about, or does it ask you to rethink too much of the Git workflow you already know?
No comment highlights available yet. Please check back later!
About Flurry on Product Hunt
“Git-compatible source control with immutable changes”
Flurry was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #127 on the daily leaderboard. Flurry is an open-source, self-hosted source control system that keeps Git compatibility at the edge and immutable changes at the center. Clone, fetch, and push with ordinary Git; review and land explicit changesets in the browser; work offline with the native fsc client; and connect bounded automation through signed webhooks, statuses, evaluations, and a local MCP server.
Flurry was featured in Open Source (69.1k followers), Software Engineering (43.3k followers), Developer Tools (523.3k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 156.2k products, making this a competitive space to launch in.
Who hunted Flurry?
Flurry was hunted by Wess Cope. 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 Flurry stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt — I’m Wess, the solo maker behind Flurry.
I built Flurry because source control has accumulated two kinds of complexity: infrastructure that is hard to own, and collaboration state that is too easy to mutate.
Flurry takes a different path. Git remains the compatibility layer for clone, fetch, and push. Inside Flurry, changes are immutable records, reviews are explicit, landing is atomic, and automation reports evidence without turning the source host into a general-purpose runner.
What’s ready today:
- unlimited public and private repositories on your own instance
- browser, Git, and native `fsc` workflows over the same history
- immutable changesets, review, approvals, protected landing, issues, wikis, releases, and snippets
- signed webhooks, revision statuses, structured automated review, and a local MCP server
- Docker-based self-hosting with documented backup and recovery
Flurry is Apache-2.0 licensed and live at https://flurry.codes.
I’d especially value feedback on one question: does the immutable-changeset model make review and automation easier to reason about, or does it ask you to rethink too much of the Git workflow you already know?