01 · API observability
Uptime, latency, incidents
API monitoring — health, incidents, detail.
- 01
Status
All your endpoints, green or red, at a glance.
- 02
Incidents
Clear timeline, post-mortems ready to share.
- 03
Alerts
Slack / PagerDuty when p99 drifts.
01b · Engineering
Technical sheet
Stack, shipping and my role on this build — for recruiters and tech leads.
- Technologies
- Next.js
- TypeScript
- React
- Tailwind CSS
- Libraries & tools
- Status timeline
- mock metrics
- Deployment
/play demo — simulated ops app, mock data
- Role
Data UX · dense UI · business components
- Context
Playable prototype — filters, states, navigation
02 · Inside the product
One scroll, one screen
Each section locks to the viewport — keep scrolling past the last screen to return to the brief.
Uptime, latency, incidents
OpenStatus
128 k€
Incidents
98,2 %
Alerts
14
Incidents
OpenOpen Signal
OpenSélection
API health at a glance
Hook a demo endpoint and watch the graphs.
Activité
We cut MTTD from 18 to 4 minutes.
SRE · marketplace
The client status page updates itself.
CTO · fintech
Back to the brief
You’ve left the demo screens — next: try it, then the craft notes.
03 · Ops
They sleep a bit better
“We cut MTTD from 18 to 4 minutes.”
“The client status page updates itself.”
04 · Sandbox
Open Signal
Hook a demo endpoint and watch the graphs.
- →Hero + below-the-fold sections (not just a hook)
- →Visual hierarchy and primary CTA
- →Information density vs readability
05 · Same family
Other directions of the same type — to compare density and mood.
06 · What to look at
- 01Hero + below-the-fold sections (not just a hook)
- 02Visual hierarchy and primary CTA
- 03Information density vs readability
- 04Interactive states (hover, selection, feedback)