Skip to content

LetPeopleWork/Lighthouse

Repository files navigation

Lighthouse — Flow metrics, predictability & Monte Carlo forecasting

Latest Release

Lighthouse is a free, open-source forecasting and Flow metrics platform designed for Agile and Kanban teams. By applying Monte Carlo simulations to your historical throughput, Lighthouse helps teams predict delivery dates, understand predictability, and keep systems stable with actionable Flow Metrics.

Try the Community version — no account or credit card required; runs on your infrastructure and ships with a demo mode for exploration.

Team Metrics Overview

Why Lighthouse?

  • Monte Carlo simulation-based forecasts (How Many, When) — probability-driven delivery estimates
  • Built for Kanban: in-depth flow metrics (WIP, Cycle Time, Throughput, Work Item Age) and widgets for teams and projects
  • Integrations with Jira, Azure DevOps, CSV import and Linear (preview) to keep your existing toolchain
  • Dashboards and Predictability Score to turn data into decisions and keep systems stable
  • Free & open-source (MIT); runs on your infrastructure

Built for Kanban & Stability

Lighthouse is optimized for teams that want to keep a stable delivery system. It focuses on indicators teams use to maintain flow and reduce variability — key Kanban principles.

Key capabilities to keep systems stable:

  • WIP monitoring and historical WIP charts — detect overload and make pull-based decisions
  • Throughput and run charts — measure team capacity and detect trends
  • Cycle Time (percentiles & scatterplots) — identify outliers and flow breakdowns
  • Work Item Age and Work Item Aging charts — find stuck work early and reduce rework
  • Simplified CFD and Work Distribution — visualize state changes and where effort is spent
  • Predictability Score — a single-number indicator measuring how stable your throughput is

How teams use Lighthouse

  • Keep WIP within limits and watch aging items so flow remains predictable
  • Use Monte Carlo forecasts to discuss trade-offs (e.g., delivery vs. scope) and make probability-driven decisions
  • Establish SLEs and targets using Cycle Time & Predictability metrics
  • Run experiments — e.g., reduce batch size or enforce pull policies — and measure the impact

Quick links

Quick Start

Docker (recommended):

docker pull ghcr.io/letpeoplework/lighthouse:latest
docker run -d -p 8081:443 -p 8080:80 -v ".:/app/Data" -v "./logs:/app/logs" -e "Database__ConnectionString=Data Source=/app/Data/LighthouseAppContext.db" ghcr.io/letpeoplework/lighthouse:latest

Standard Installation (binary packages)

  1. Download the platform-specific package from: https://github.com/LetPeopleWork/Lighthouse/releases/latest
  2. Extract and run; Lighthouse.exe on Windows, ./Lighthouse on Linux/macOS.

Developer: Build & run from source

  1. Clone the repo and build the backend and frontend locally
git clone https://github.com/LetPeopleWork/Lighthouse.git
cd Lighthouse
# Back-end: build and run
dotnet build Lighthouse.sln
dotnet run --project Lighthouse.Backend/Lighthouse.Backend/Lighthouse.Backend.csproj

# Front-end: inside Lighthouse.Frontend
cd Lighthouse.Frontend
pnpm install
pnpm run dev      # connect to the local backend or set VITE_API_BASE_URL
pnpm run dev-demo # run UI with demo/mock data

Core features

  • Monte Carlo forecasting (How Many / When)
  • Flow metrics dashboards and widgets: WIP, Throughput, Cycle Time, Work Item Age, Feature Size
  • Predictability Score (throughput percentiles) and SLEs
  • Project & Team forecasts that respect backlog ordering and Feature WIP
  • Integrations: Jira, Azure DevOps, CSV import, Linear (preview)
  • Demo UI and docker images for rapid onboarding

Screenshots & Examples

Core dashboards and widget screenshots are available in the docs:

Support, Contribution & Roadmap

License & Security

Lighthouse is MIT licensed — see the LICENSE file. The product runs fully on your infrastructure; data is not sent to third-party cloud providers by default.

Known limitations

  • Lighthouse does not model explicit dependencies between work items (backlog order and team focus determines forecasts).
  • If several teams work on the same feature, probability calculations may be conservative (current approach shows later estimates per-silo).
  • The Free Community edition imposes limits on the number of projects/teams; see docs for details.

Want more influence on your Kanban process? Use Lighthouse with Slack and let people work on improvements to WIP, SLEs, and cycle time reductions — we provide the tooling and the expertise.