About Nimbus.
Nimbus is a small software company. We think quality comes from a team knowing what its software does. We build tools and write essays to help teams keep that knowledge as coding agents write more of their code.
What we believe
01 A person owns every change An agent can write the code, and someone on the team still answers for it. We build for that person.
02 The answer comes from the code What the code does should be worked out from the code, with no model in the loop, so two people who ask get the same answer.
03 Tools should carry the load Keeping a whole system in your head costs attention. Tools should keep track of what changed, so people can spend their attention on decisions.
04 It has to work when the agent doesn’t Agents go down, run out of credits, or aren’t allowed near the code. A team still needs to know what its code does when that happens.
Where our tools help today
suss reads TypeScript, Python and Ruby, on your machine or in CI. Its plugin runs inside Claude Code.
01 Plan What reads this table before I change it? suss ask
02 Write Did this edit break the other side of a route or table? the Claude Code plugin
03 Review What did this branch change, and what did it introduce? suss check --base and the GitHub Action
04 Release What changed between these two tags? suss inspect --diff, by hand
05 On call What does the code we deployed do on each path? suss inspect on that commit
How we got here
- 2024 We started by generating documentation from code, and then drew maps of how a system's services connect.
- 2025 We built an impact analysis service that commented on pull requests with the other services a change could break.
- 2026 We started suss in April and released it as open source in August.
People
Matt Kindy
Jen Sun