Feature Deep Dive
Build your incident command view from a clean canvas or the default layout, then rearrange panels to match how your team actually operates.
Version 1.0 did the important thing first: make the core workflows stable under pressure. As we kept shipping features, one part stayed static, the layout itself.
That layout reflected my own opinion of how an operations screen should look. It worked, but it could not match every team style, venue profile, or shift rhythm.
Some teams operate map-first. Others keep the live incident queue dominant and surface map context only when escalation starts. Flexible panels support both styles without forcing one workflow.
During live operations, layouts can shift as conditions change: widen timeline during review windows, expand incident feed during surges, and pull back to a compact close-out view after peak.
We wanted to preserve the speed of a trusted default while giving teams room to run their own command style.
Shamira product notes, 2.0.0
Day shift keeps reporting and timeline panels expanded for trend monitoring. Night shift switches to an incident-feed plus map-heavy layout during crowd peaks, then restores a baseline for close-out.
This feature is documented in the following public release notes.
Continue your evaluation with pricing, security, and release transparency pages.