Noonlight
An internal dashboard system for security operations, owned end to end including authentication and access control.
Internal tooling where the operator is the critical path
Noonlight sits between connected devices and emergency services: an alarm fires, a live agent verifies it, and real dispatch follows. The internal tooling those agents work in is not back-office software, it is the mechanism by which an emergency gets a response.
That raises the stakes on access control specifically. Systems touching emergency events and user location need authentication and authorisation that are correct by construction, not bolted on once the dashboards work.
Own the auth boundary along with the surface
We took ownership of authentication and the permission model rather than treating them as someone else's dependency, which kept the security boundary coherent as the dashboard surface grew.
The internal surfaces agents work in, built as one system rather than an accumulation of one-off tools.
The sign-in and session model owned directly, so its behaviour was designed rather than inherited.
Permissions modelled around what operational roles are allowed to see and do, enforced consistently across the system.
Interfaces designed for staff working them continuously, where density and speed matter more than first-run friendliness.
An internal platform owned end to end
Rainier built and owned the internal dashboard system and its access control, for a platform that now powers emergency response behind a large number of consumer and commercial safety products.
Have a system with the same constraints?
Send us the scope and the compliance requirements. We will tell you what the architecture should look like before you commit to anything.