Waltz reads how your software changes, and tells each level what matters.
Engineering Intelligence for teams that build with AI agents. A short Brief for each level of your organisation, with the evidence attached.
- Reads
- GitHub today; Jira, Slack and coding agents next
- Delivers
- A weekly Brief, starting with Engineering Managers
- Never
- Rates individual people
One system. A Brief for every level.
Each Brief is written for its reader and short enough to finish. Managers review theirs, and what they confirm carries up the chain.
From commit to Brief. Waltz reads how your software changes.
- 01
Watch
Waltz connects to the tools your teams already use and follows every change as it lands.
- 02
Model
It keeps a fact-only model of your system: services, vendors and the interfaces between them.
See a Baseline - 03
Brief
Each week it writes a short Brief for each reader, with the evidence for every line.
Read a Brief - 04
Review
Readers correct and confirm. Their corrections shape next week's Briefs, and the level above.
Connect once. Read every week.
An app install or a sign-in per tool. No configuration files to start.
- GitHubCommits, pull requests and how the code is built
- JiraNext: initiatives, epics and their links to code
- SlackNext: Briefs delivered where your team reads
- Coding agentsNext: which changes agents wrote, from vendor data
Recent Briefs.
- A quiet week: nothing changed in how the system is built; only routine upkeep.Engineering Manager · Full Stack FastAPI Template
- Backend can now be deployed to FastAPI Cloud, as well as Docker Compose.Engineering Manager · Full Stack FastAPI Template
- The Traefik software no longer runs as a separate service: Proxy now runs it; Proxy now deploys automatically with the rest of the system and uses Let's Encrypt.Engineering Manager · Full Stack FastAPI Template
- Frontend no longer runs as a separate service: the website is now part of Backend.Engineering Manager · Full Stack FastAPI Template
Private by design. Reports on systems, not people.
Systems, not people
Waltz never models how skilled an individual is. Briefs describe what the software became.
Names are your setting
Whether a Brief names people is a choice your org makes, per audience.
One org, one boundary
Your data never appears in, or shapes, another organisation's Brief.
Source stays put
Code is analysed in a short-lived sandbox. Only derived facts and short cited excerpts are kept.