Self-hosted project trackerOct – Nov 2026

Kloister

Self-hosted project tracking: boards, backlog, sprints and a dependency-aware timeline.

My partWrote the spec and the release rules, set each milestone, and reviewed every one before it shipped.

Agent-assistedAgents wrote much of the code under review.

GitHub

Kloister's project board with Backlog, To Do, In Progress and Done columns of example cards — The board. All data is example data.

2 teamsat my day job plan their work in it

What it does

Boards, backlog, sprints, epics down to bugs, and a timeline where moving one item moves its dependants, with working days and holidays.
Role-based change rules: by default only PMs and Leads change dates and scope; Members can suggest a change.
Live updates: boards, timelines and items follow other people's changes without a reload, with a name tag on the field someone is editing.
Runs fully on your own server, with no SSO, email or outside service at runtime, and one install script for RHEL 8.10.
8 releases in 18 days, each through CI that builds, lints, tests, checks migrations against the schema and runs 80 browser stories.

How I checked the agents' work

Every milestone gets a second reader

The agent rules require an independent review at the end of each milestone, by an agent with fresh context. It checks the diff against the spec for missing permission checks, tests and security issues, and every valid finding is fixed before the commit.

Example: the review of the Azure Boards transfer milestone used two reviewers and found 12 issues, including a missing rollback when a late row fails and updates that could wipe remote values nobody had seen. All were fixed, with tests.

Not done yet: the acceptance run on a real RHEL 8.10 virtual machine.

Source: AGENTS.md (milestone workflow) and 13 review notes in the repo's local review folder