Know what is deployed.
Trust what you see.
A read-only control room for deployments, releases, and traceability. Derived from infrastructure, not assumptions.
The Problem
What is actually running in production?
Versions live in GitHub, CI, and CD tools, but which one is real? Teams scroll tabs and ask in Slack instead of having a single, trusted answer.
When did this change happen, and who deployed it?
No shared audit trail. Incidents and compliance checks mean manual digging through commits, builds, and deployment logs.
Are these tickets really included, or do we just think they are?
“Is NEXUS-412 in QA?” Nobody knows for sure. Traceability is guesswork unless you have a deterministic way to link tickets to deployments.
The data exists, but it's scattered, inconsistent, and often misleading.
Infrastructure defines reality.
Product
Overview: envs, tags, health
One place to see what is deployed in each environment. Tags and deployers come from infra (e.g. kustomization). Health pills appear when Datadog is connected; otherwise we show "Unknown". Never fake data.
Release History
Tag-change events from infra commits, shown as a linear list and as a deployment calendar. Here we show the list; in the app you can switch to calendar view to see activity per day and click a date to inspect events.
Ticket Tracker: "unknown" when we can't prove it
Tickets from PRs; env presence when we have a documented basis (branch, tag, timing). When we don’t, we show “Unknown” and explain why. No guessing.
Runbooks: Scope, Drift, Release Diff
On-demand checks against GitHub: Scope - baseline vs default branch (commits, tickets). Drift - what's in release but not yet in main. Release Diff - compare two releases (older to newer). We're actively adding more runbooks.
Product updates
Deployment history & calendar
Release History has both a linear list of events and a calendar view with deployment intensity per day. You scan “when it was busy” on the calendar and click a day to drop into exact events.
Ticket Tracker: deterministic env presence
Tickets are linked to builds and deployments only when timing and reachability line up. Env presence is carried forward instead of disappearing; when we can't prove it, we show “Unknown”.
Environment details from infra
Env cards pull tags, deployers and links from infra (e.g. kustomization) rather than CI logs. Integrations enrich the view, but the primary truth stays in the repo.
Runbooks: Scope, Drift, Release Diff
Scope Checker - compare a baseline branch vs default: tickets, commits, PRs. Drift Checker - see what’s in a release branch but not yet in default. Release Diff - compare two releases (e.g. 0.20.0 vs 0.21.0): added tickets and commits per repo, strikethrough for missing branches. We’re actively adding more runbooks (readiness checks, promotion validators).
Statistics & Reminders
Statistics dashboard: deployment frequency, lead time, top deployers per project and environment, with 7d / 30d / 90d windows. Reminders & Signals surface deployment-focused hints: stale deploys (no deploy for X days) and QA vs UAT diff (single-repo differences worth checking).
Snapshot, integrations, Configuration
Automated snapshot scheduler with ETA tracking. GitHub, TeamCity, ArgoCD, Jira, Datadog wired in; GitHub required, rest optional. Configuration wizard for tenant setup and API tokens. Dark & light theme, unified UI.
Integrations
GitHub
TeamCity
ArgoCD
Jira
Datadog
GitHub is required. Everything else is optional.
What this product deliberately does not do
- Does not trigger deployments
- Does not enforce workflows
- Does not guess ticket deployments
- Does not write to your systems
Who it's for
Built for
- Release Managers and Platform / DevOps teams
- Multi-service platforms with infra-as-code as the gate to prod
- Teams deploying via PR + CI/CD, not click-to-deploy buttons
- Projects with named environments (dev / qa / uat / prod or equivalent)
- Stacks where observability can be tagged by env and service (e.g. Datadog)
Not for
- Click-to-deploy tools
- Auto-magic pipelines
- Teams without versioned deployments
Talk to us about your setup
We'll tell you exactly what the product can and cannot show in your environment.
Talk to us about your setupPrefer web mail or want to copy the address?
hello@watchturm.comIf the email button does nothing, your browser or OS may not have a default mail app configured. Use the links above or copy the address instead.