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).

Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Lictory

Approve a revision, not a ticket. Open-source, self-hosted

Specs get branches, reviews by Product, Eng and QA, and approvals tied to a revision. Edit after sign-off and they go stale. Readiness is computed like CI. Optional AI and MCP agents only propose. Deliver in Lictory or hand off to Jira Cloud. MIT.

Top comment

Hey Product Hunt πŸ‘‹ I'm Christian, a software engineer and student in Rome.

Lictory came from one pattern I kept seeing: rework rarely starts in the code. It starts with a spec everyone read differently.

So Lictory treats requirements like code. You propose changes on branches, each discipline reviews the parts it owns, and approvals belong to the exact revision they saw. Change the text after QA signs off, and that approval is marked outdated and QA gets asked again. "Ready" isn't a dropdown. It's computed from checks, like CI.

Docs live next to the work too: Spaces hold runbooks and decision records that cite work items with their live status. Pages others rely on can go through the same branch and review flow as specs.

AI is optional. Lictory Intelligence and agents connected over MCP can suggest changes, but people approve.


It's MIT licensed and runs on your own server with a guided install CLI.
I built it with T3 Code, Claude and Grok Bot.


I'd love to hear where your team's spec process breaks today.

About Lictory on Product Hunt

β€œApprove a revision, not a ticket. Open-source, self-hosted”

Lictory was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #423 on the daily leaderboard. Specs get branches, reviews by Product, Eng and QA, and approvals tied to a revision. Edit after sign-off and they go stale. Readiness is computed like CI. Optional AI and MCP agents only propose. Deliver in Lictory or hand off to Jira Cloud. MIT.

On the analytics side, Lictory competes within Open Source, Developer Tools and GitHub β€” topics that collectively have 633.9k followers on Product Hunt. The dashboard above tracks how Lictory performed against the three products that launched closest to it on the same day.

Who hunted Lictory?

Lictory was hunted by Christian Carpinelli πŸ‡ͺπŸ‡Ί. 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.

For a complete overview of Lictory including community comment highlights and product details, visit the product overview.