The design philosophy behind Olsa's canvas

Dashboards are how software tells you what it did. They are rarely how people think about what they do. When we started designing Olsa, the first decision we made was to throw away the list view and start from a canvas.

Workflows are spatial

Ask an ops lead to explain a process and they reach for a whiteboard, not a table. Work has shape: things flow into other things, branch, wait, and merge. A canvas lets that shape stay visible, so the map your team draws is the system that actually runs.

Density is a choice, not a default

Linear dashboards force one level of detail on everyone. On the canvas, you zoom. Leadership sees the five big systems and how they connect; the engineer double-clicks into a single retry policy. Same source of truth, different altitudes.

Calm by default

Automation software loves to celebrate itself with badges and confetti. We went the other way: a quiet surface where the only things that light up are the things that need you. The best session in Olsa is a short one.

What we gave up

An open canvas costs something — onboarding is harder than a wizard, and empty space can intimidate. We think the trade is right: tools shape thought, and we would rather give teams a thinking surface than another inbox.