Error page 500
The 500 with a mono incident id, the team already paged, retry and status links.
Error page 404
Pro
Centered 404 page showing the failed path in mono, three reasons a workspace link goes stale, and search or dashboard as recovery actions.
More like this
Browse Application UI
First run checklist empty
Empty dashboard state with a 4-step setup checklist, progress bar, and honest note that panels appear as steps are completed.
Import in progress state
A panel for a running data import with a three step pipeline, a live progress bar, meta rows for timing, and notify or cancel actions.
Maintenance page
Full-page planned maintenance screen with a stated window, estimated time remaining, a do-nothing instruction, and a status-page link.
No access yet state
Pending-access gate naming the reviewer with avatar and ETA, plus a list of surfaces the user can reach in the meantime.
No data yet state
Empty panel with a geometric illustration, an events headline, an explanation of when data appears, and a primary API call action.
No integrations state
Empty integrations surface with unlock bullets, a browse CTA, and Slack, GitHub, and Jira quick-connect chips.
No search results state
The query kept, three scopes to widen, and what search covers stated.
Offline state
Offline state panel listing what still works locally and what is paused until reconnection, with a guarantee that queued drafts are never lost.
Onboarding empty dashboard
The dashboard before data, zeroed KPIs and the five minute fill promise.
Payment failed state
Payment failed billing gate showing the card on file, the exact decline code, a three attempt retry schedule, and update and retry actions.
Permission denied state
The 403 that names the role, the owners who grant it, and the request flow.