GitHub Repository

Release orchestration and environment visibility for modern microfrontend architectures.

6 starsPython

WatchTurm – an open-source release visibility layer I use in my work

Name: WatchTurm – an open-source release visibility layer I use in my work
Availability: InStock
Author: WatchTurm

by WatchTurm·Feb 21, 2026·3 points·0 comments

Visit Project View on HN

AI Analysis

●●●BangerSolve My ProblemSlickDark Horse

Multi-environment release dashboard aggregates GitHub+TeamCity+Jira in one control room, no agents.

Strengths

•Solves real pain: 'what's running where' across repos and environments without hitting five dashboards.
•Serverless architecture (snapshot generator + static frontend) means zero operational overhead and easy SSO integration.
•Calendar view and drift checker provide actionable visibility that raw CI logs don't give.

Weaknesses

•Requires manual YAML config per repo; no auto-discovery diminishes appeal for large monorepos with hundreds of services.
•15-30min snapshot refresh interval means stale data during active deployments; real-time sync pattern unexplored.

Post Description

I built this to solve a recurring problem in multi-repo, multi-environment setups: it’s surprisingly hard to answer “what is actually running where?” without checking several systems. WatchTurm is an open-source release visibility layer. It aggregates metadata from sources like GitHub, Jira and CI (e.g. TeamCity), generates a structured snapshot of environment state, and surfaces it in a single control view.

It doesn’t replace CI/CD or manage deployments. It sits above automation and focuses purely on visibility: - what version runs in each environment - how environments differ - what changed between releases

I’m currently using it in my own daily work and would really appreciate technical feedback, especially from teams with multi-environment pipelines.

repo: https://github.com/WatchTurm/WatchTurm-control-room