Log — Building Cadres
The build log.
What I'm building, why, and what I got wrong along the way.
Latest entry — LOG-06 · · 4 min
Six Products and the Rule That Keeps Them Apart
Cadres kept growing after the suite post: a service desk, a network product and more. How it got to six, and the rule that stops that turning into sprawl.
Read the entry →All entries6 entries · RSS
LOG-06
Six Products and the Rule That Keeps Them Apart
Cadres kept growing after the suite post: a service desk, a network product and more. How it got to six, and the rule that stops that turning into sprawl.
LOG-05
Someone Will Ask for Evidence Sooner Than You Think
I needed compliance, access and finance tooling to run Cadres, and decided to build it. Why that cost months, and why most small companies leave this too late.
LOG-04
Everything Is a Workflow
Patching, remediation and privileged maintenance all run on the same workflow engine. What it does, and why I built it before almost anything else.
LOG-03
Nobody Should Know the Admin Password
I wanted to pick up a credential while opening a remote session. That turned into a built-in vault with automatic rotation.
LOG-02
Six Agents on Every Server
Patching on its own wasn't enough, and neither was host management without remote access. How one feature kept pulling in the next.
LOG-01
It Started With Patching
Each server patch was costing us 30 to 60 minutes of someone checking boxes. That's where Cadres came from.