Learning a normal week in four days
JournalTorus
Inside the first days of a new Torus account
Written by Elsa Thorvald, Head of Reliability
Wednesday, 3 September 2026
The first thing Torus does on a new stack is nothing at all. For four days it only listens, building a picture of what normal looks like for every service, so that later it can tell when something is not.
Listening first
Read-only keys mean Torus can see metrics, logs and deploys but cannot change a thing. That is deliberate. Teams get a full report of what was learned before a single rule is switched on.
What the report shows
Busy hours per service, the usual cost per day, the alerts that fired and needed no action, and the three fixes Torus would make first. Most teams recognise their own stack in it, and a few surprises.
Day by day
- Day 1: connect accounts and clusters
- Day 2: map services and dependencies
- Day 3: learn daily rhythms
- Day 4: first report and suggested rules
Key takeaways
- Listening builds trust
- A good baseline is worth four days
- The first report is the start, not the sale
Inside the first days of a new Torus account.
