Launching today

Lictory
Approve a revision, not a ticket. Open-source, self-hosted
2 followers
Approve a revision, not a ticket. Open-source, self-hosted
2 followers
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.





Free
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted



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.