A console that admits what it does not know

A dashboard is a claim about your system, made a hundred times a page. The most valuable thing this one does is refuse to make a claim it cannot support: where a panel has no source behind it, it says so on screen rather than drawing a plausible number you might act on at three in the morning.

7
groups, one navigation
2
themes, both measured for contrast
EN / FR
the whole interface, not just the marketing

What is on it

One column of navigation, grouped by the question you arrived with rather than by which team built the feature.

Monitoring

Overview, incidents, alerts, services, performance, errors, logs, traces and uptime. Nine destinations, and where most of an incident is spent.

Release

Releases with their health, deployments, and change tracking — the timeline that root-cause analysis reads from rather than a separate history page.

Infrastructure

Infrastructure, containers, databases, queues and scheduled jobs, each built off the span attributes your services already send.

User observability

Affected users, session replays and the feedback people submitted, joined to the errors they hit rather than sitting in a separate inbox.

Insights

Custom dashboards with their widgets, and scheduled reports.

AI

Anomaly detection and root-cause analysis. Two destinations, not five doors into the same room under different names.

Management

Projects, teams, integrations, API keys, billing, the audit log and settings — including single sign-on and per-project data controls.

A panel with no data says so

This is the design rule the rest of the console is built on, and it is unusual enough to be worth stating.

Where a panel has a real source, it shows real data. Where it does not — because the feature behind it is not finished, or because your project has never sent that signal — it says that on screen. It does not render a sample. It does not draw a smooth sparkline from nothing.

The reason is narrow and practical: a plausible fabricated number is indistinguishable from a real one at a glance, and the moment you most need to trust the console is the moment you are least able to check it.

Two themes, both actually measured

Light and dark are both first-class, and the contrast of each was measured rather than eyeballed. A dark mode that ships as an inverted stylesheet fails on exactly the things you read under pressure: the secondary label, the muted timestamp, the state colour on a small pill.

Every page has also been opened and looked at on a tenant carrying real telemetry, which is a lower bar than it sounds and one a surprising amount of software does not clear. Looking is what catches the things measurement does not — including, once, a security control that could not be reached from anywhere in the interface.

Both languages, all the way down

The interface ships in English and in French, and the French is authored rather than machine-translated. That covers the whole console — not the marketing pages with an English product behind them, which is the usual arrangement and is worse than being monolingual, because it promises something the product then withdraws at sign-in.

The language is a setting on your account, so it follows you rather than following the address bar.

The project is in the shell, not in the sidebar

Every project-scoped view reads one selected project, and that selector sits in the top bar where it is visible from every page. It used to be a second sidebar listing nineteen destinations that the first sidebar also listed — one navigation drawn twice, taking a column of screen to say nothing new.

A link that offers a second name for the thing on the next line of the same menu is not a shortcut. It is a promise of a distinction that does not exist, and those were removed rather than kept for symmetry.

Look at it with your own data in it

Screenshots of a dashboard are worth very little; a dashboard with your own services in it is worth an afternoon. The free plan needs no card.