FLAGSHIP · 0→1 · ENTERPRISE
Okta Private Cloud Status Page
During an incident, enterprise customers had no reliable way to tell whether it was their tenant or the broader platform — every ambiguous minute became a support ticket. I owned the architecture end to end: designing environment-specific status visibility, building it, and presenting the approach to the internal stakeholders who had to trust it before it shipped.
The hard part wasn't showing status — it was scoping it correctly. A company could have multiple tenants, and each tenant could have multiple people looking at it, so the architecture had to guarantee one customer's incident never leaked into another's view, no matter how many tenants or seats sat on either side.
My role: Sole architect and engineer, 0→1. Presented design and rollout plan directly to stakeholders.