# patterns.konigi.com > Pattern libraries for user interfaces. Every entry is a named design pattern with a > problem statement, trade-offs, a pre-ship checklist, and—where they exist—dated > screenshots of shipping products hot-spotted to the pattern they demonstrate. The model: a **library** is a set of patterns for one kind of interface, and it declares its own groups. A **pattern** is a recurring solution to a recurring problem. A **product** is a shipping application. A **capture** is one dated screenshot of one product, hot-spotted to the patterns it shows. Patterns are the canonical pages; product and domain pages are generated indexes and are shared across libraries. Every pattern page has a markdown twin at `//.md`. Prefer those. Currently 109 patterns across 2 libraries, 32 products, 39 captures. ## AI Assistant Patterns Patterns for chat assistants and AI features within apps. Index: https://patterns.konigi.com/ai-assistants ### Starting a request Help people write a request, add files, and choose how the assistant should respond. - [Attachment tray](https://patterns.konigi.com/ai-assistants/attachment-tray.md): People need to know which attached files the assistant can read. Also called: file drop, upload chip, context attachment. - [Command menu](https://patterns.konigi.com/ai-assistants/command-menu.md): People need a quick way to choose an action or select a specific item. Also called: slash commands, at-mentions, prompt shortcuts. - [Composer](https://patterns.konigi.com/ai-assistants/composer.md): People need space to write a prompt without losing sight of the conversation. Also called: prompt box, input bar, message box. - [First-run state](https://patterns.konigi.com/ai-assistants/first-run-state.md): New users need to understand what the assistant can do and how to start. Also called: empty chat, onboarding state, zero state. - [Mode switch](https://patterns.konigi.com/ai-assistants/mode-switch.md): People need to choose between a quick answer and more time spent on research or analysis. Also called: search toggle, think harder, deep research. - [Model picker](https://patterns.konigi.com/ai-assistants/model-picker.md): People need to understand which model fits their task and what using it will cost. Also called: model switcher, engine selector. - [Prompt starters](https://patterns.konigi.com/ai-assistants/prompt-starters.md): People need examples of useful requests when they do not know what to ask. Also called: suggested prompts, example questions, conversation starters. ### Messages and responses Make conversations easy to follow and give people control over the answers they receive. - [Edit and resend](https://patterns.konigi.com/ai-assistants/edit-and-resend.md): People need to correct an earlier question without losing the conversation that followed it. Also called: edit prompt, revise question, fork from here. - [Message turn](https://patterns.konigi.com/ai-assistants/message-turn.md): Readers need to distinguish their messages from the assistant’s answers. Also called: chat bubble, turn, message pair. - [Regenerate](https://patterns.konigi.com/ai-assistants/regenerate.md): People need another attempt at an answer without retyping their question. Also called: try again, retry response, alternate response. - [Response actions](https://patterns.konigi.com/ai-assistants/response-actions.md): People need easy access to actions on an answer without crowding the conversation. Also called: message toolbar, copy and rate, feedback row. - [Stop generation](https://patterns.konigi.com/ai-assistants/stop-generation.md): People need to stop an unwanted answer before it finishes. Also called: interrupt, halt, cancel response. - [Streaming response](https://patterns.konigi.com/ai-assistants/streaming-response.md): People need to start reading an answer while the assistant is still generating it. Also called: token streaming, progressive rendering, typewriter effect. ### Answer formats Present answers in formats people can read, edit, and use elsewhere. - [Artifact panel](https://patterns.konigi.com/ai-assistants/artifact-panel.md): People need room to read and revise generated documents without losing the conversation. Also called: canvas, side-by-side output, preview pane. - [Code block actions](https://patterns.konigi.com/ai-assistants/code-block-actions.md): People need to copy or use generated code without losing its formatting. Also called: copy button, run snippet, apply to file. - [Response collapse](https://patterns.konigi.com/ai-assistants/response-collapse.md): People need to scan a conversation without long answers pushing everything else out of view. Also called: long answer fold, show more, truncated response. - [Structured output](https://patterns.konigi.com/ai-assistants/structured-output.md): People need answers in a format that makes the information easy to use. Also called: generated table, comparison grid, formatted answer. ### Understanding answers Show the sources, actions, and limits behind an answer so people can check it. - [Citation chip](https://patterns.konigi.com/ai-assistants/citation-chip.md): Readers need to check the source behind a specific claim. Also called: source badge, inline citation, footnote marker. - [Knowledge cutoff notice](https://patterns.konigi.com/ai-assistants/knowledge-cutoff-notice.md): People need to know when an answer may rely on outdated information. Also called: training date, staleness warning, may be outdated. - [Reasoning disclosure](https://patterns.konigi.com/ai-assistants/reasoning-disclosure.md): People waiting for an answer need enough information to spot a misunderstood request. Also called: thinking, chain of thought, show work. - [Source list](https://patterns.konigi.com/ai-assistants/source-list.md): Readers need to review the sources used to produce an answer. Also called: references panel, sources rail, retrieved documents. - [Tool call trace](https://patterns.konigi.com/ai-assistants/tool-call-trace.md): People need to see which actions the assistant took and whether they succeeded. Also called: function call, action log, ran a search. ### Memory and context Let people see and control what the assistant remembers and which information it can use. - [Context meter](https://patterns.konigi.com/ai-assistants/context-meter.md): People need to know when a conversation is approaching the amount of information the assistant can use. Also called: context window indicator, token budget, conversation length. - [Conversation history](https://patterns.konigi.com/ai-assistants/conversation-history.md): People need to find and return to earlier conversations. Also called: thread list, chat sidebar, recents. - [Custom instructions](https://patterns.konigi.com/ai-assistants/custom-instructions.md): People need to save preferences they would otherwise repeat in every conversation. Also called: system prompt, preferences, style guide. - [Memory chip](https://patterns.konigi.com/ai-assistants/memory-chip.md): People need to see and control the details an assistant saves about them. Also called: remembered, saved detail, persistent context. - [Scoped context](https://patterns.konigi.com/ai-assistants/scoped-context.md): People need to know which files and workspace content the assistant can access. Also called: context pills, working set, what it can see. ### Help within apps Let people use AI where they are already working, without switching to a separate chat. - [AI entry point](https://patterns.konigi.com/ai-assistants/ai-entry-point.md): People need to find the AI feature and understand what it can do. Also called: sparkle button, magic icon, assist affordance. - [Assistant sidebar](https://patterns.konigi.com/ai-assistants/assistant-sidebar.md): People need to use the assistant while keeping their work in view. Also called: AI panel, chat drawer, side rail assistant. - [Ghost text](https://patterns.konigi.com/ai-assistants/ghost-text.md): Writers need to distinguish suggested words from text they have already accepted. Also called: inline completion, autosuggest, grey text. - [Inline assist](https://patterns.konigi.com/ai-assistants/inline-assist.md): People need to revise selected text without leaving the document. Also called: select to edit, rewrite selection, contextual AI. - [Suggestion diff](https://patterns.konigi.com/ai-assistants/suggestion-diff.md): People need to see what the assistant changed before accepting a revision. Also called: accept or reject, tracked change, proposed edit. ### Limits and errors Explain why a request cannot be completed and give people a useful next step. - [Generation error](https://patterns.konigi.com/ai-assistants/generation-error.md): People need to know when an answer has failed and how to try again. Also called: failed response, retry state, network interruption. - [Refusal](https://patterns.konigi.com/ai-assistants/refusal.md): People need to understand why a request cannot be fulfilled and what they can do next. Also called: declined response, safe completion, guardrail message. - [Usage meter](https://patterns.konigi.com/ai-assistants/usage-meter.md): People need to see their remaining allowance before they run out. Also called: rate limit, message quota, plan ceiling. ## Dashboard Patterns Patterns for dashboard charts, layouts, and controls. Index: https://patterns.konigi.com/dashboards Taxonomy: Bach et al., Dashboard Design Patterns (IEEE VIS 2023), https://dashboarddesignpatterns.github.io/patterns.html ### Key measures Show important values with the comparisons and context people need to understand them. - [Delta indicator](https://patterns.konigi.com/dashboards/delta-indicator.md): People need to see how much a value changed and what it was compared with. Also called: change badge, trend arrow, vs-previous. (4 captures) - [KPI tile](https://patterns.konigi.com/dashboards/kpi-tile.md): People need to check a key value and understand whether it needs attention. Also called: stat card, big number, BAN, metric card, scorecard tile, stat panel. (3 captures) - [Percentile summary](https://patterns.konigi.com/dashboards/percentile-summary.md): People need to see slower experiences that an average can hide. Also called: p50/p95/p99, latency percentiles, tail latency. (1 capture) - [Ranked list](https://patterns.konigi.com/dashboards/ranked-list.md): People need to find the items contributing most to a result. Also called: top-N, leaderboard, toplist. (4 captures) - [Ratio and rate](https://patterns.konigi.com/dashboards/ratio-and-rate.md): People need to judge a count in relation to overall volume or time. Also called: percent-of, per-unit, normalized metric. (7 captures) - [Sparkline](https://patterns.konigi.com/dashboards/sparkline.md): People need a compact view of recent changes beside a value. Also called: inline trend, micro-chart, word-sized graphic. (4 captures) - [Target and progress](https://patterns.konigi.com/dashboards/target-and-progress.md): People need to see how far they are from a goal and whether they are on pace. Also called: bullet graph, goal bar, quota bar. (2 captures) ### Labels and context Explain what the data means, where it comes from, and when it was updated. - [Annotation](https://patterns.konigi.com/dashboards/annotation.md): People need to compare changes in a chart with events that may help explain them. Also called: event marker, deploy marker, note on chart. (2 captures) - [Data source badge](https://patterns.konigi.com/dashboards/data-source-badge.md): People need to know where a panel’s data comes from and whether that source is working. Also called: provenance, connector health. (2 captures) - [Explain this metric](https://patterns.konigi.com/dashboards/explain-this-metric.md): People need a shared definition of what a metric counts. Also called: definition tooltip, metric glossary. (2 captures) - [Freshness indicator](https://patterns.konigi.com/dashboards/freshness-indicator.md): People need to know how old the data is before acting on it. Also called: last updated, stale-data warning, live pulse. (4 captures) - [Legend and series toggle](https://patterns.konigi.com/dashboards/legend-and-series-toggle.md): People need to identify chart series and isolate the ones they want to compare. Also called: toggleable legend, multi-toggle KPI header. (3 captures) - [Time-range picker](https://patterns.konigi.com/dashboards/time-range-picker.md): People need to choose the period a dashboard shows and see that choice clearly. Also called: date range, relative time, quick ranges. (4 captures) ### Charts and data displays Choose a way to show the data that fits the question people need to answer. - [Anomaly band](https://patterns.konigi.com/dashboards/anomaly-band.md): People need to distinguish unusual changes from a metric’s normal ups and downs. Also called: expected range, forecast band, confidence ribbon, seasonal baseline, anomaly detection overlay. (1 capture) - [Bed map and track board](https://patterns.konigi.com/dashboards/bed-map.md): Staff need to see bed availability and what each patient is waiting for in one place. Also called: census board, ED whiteboard, patient tracking board. - [Calendar heatmap](https://patterns.konigi.com/dashboards/calendar-heatmap.md): People need to spot recurring patterns and gaps in daily activity. Also called: contribution graph, punch card, day grid. (2 captures) - [Cohort grid](https://patterns.konigi.com/dashboards/cohort-grid.md): People need to compare how groups return over time after joining. Also called: retention grid, triangle chart, cohort table. (1 capture) - [Data table](https://patterns.konigi.com/dashboards/data-table.md): People need to scan, sort, and compare exact values for many items. Also called: metrics table, sortable grid. (5 captures) - [Funnel](https://patterns.konigi.com/dashboards/funnel.md): People need to see where participants leave a sequence of steps. Also called: conversion funnel, step drop-off. (1 capture) - [Gauge and dial](https://patterns.konigi.com/dashboards/gauge.md): People need to see where a value sits within a known range. Also called: radial gauge, speedometer, dial. (4 captures) - [Geo map with markers](https://patterns.konigi.com/dashboards/geo-map.md): People need to see how values and conditions vary by location. Also called: map panel, choropleth, geospatial view. (3 captures) - [Heatmap](https://patterns.konigi.com/dashboards/heatmap.md): People need to see how a large set of values is distributed over time. Also called: density heatmap, latency heatmap, BubbleUp. (2 captures) - [Histogram and distribution](https://patterns.konigi.com/dashboards/histogram.md): People need to see how values are spread out rather than relying on an average. Also called: distribution chart, bucketed bar. (2 captures) - [Host map](https://patterns.konigi.com/dashboards/host-map.md): People need to spot unusual machines within a large fleet. Also called: hexagon map, fleet grid, infrastructure map. (1 capture) - [Log tail](https://patterns.konigi.com/dashboards/log-tail.md): People need to inspect individual events as they arrive. Also called: live tail, log stream. (1 capture) - [Order book and depth](https://patterns.konigi.com/dashboards/order-book.md): People need to see the buy and sell quantities currently listed at each price. Also called: market depth, level 2, DOM. (1 capture) - [Process mimic](https://patterns.konigi.com/dashboards/process-mimic.md): Operators need to see live values alongside the equipment and connections they describe. Also called: mimic diagram, P&ID display, SCADA schematic. (1 capture) - [Sankey and path](https://patterns.konigi.com/dashboards/sankey-and-path.md): People need to see how quantities split and move through different routes. Also called: flow diagram, user path, alluvial. (1 capture) - [Service map](https://patterns.konigi.com/dashboards/service-map.md): People need to see service dependencies and locate problems among them. Also called: dependency graph, topology view, service graph. (1 capture) - [Small multiples](https://patterns.konigi.com/dashboards/small-multiples.md): People need to compare separate charts using the same scales and layout. Also called: trellis, faceted charts, panel series. (3 captures) - [Stacked composition](https://patterns.konigi.com/dashboards/stacked-composition.md): People need to see how individual parts contribute to a changing total. Also called: stacked area, stacked bar, part-to-whole. (3 captures) - [Status history](https://patterns.konigi.com/dashboards/status-history.md): People need to see when a state changed and how long it lasted. Also called: state timeline, uptime bar, availability strip. (1 capture) - [Threshold line and region](https://patterns.konigi.com/dashboards/threshold-line.md): People need a visible limit to judge the values on a chart. Also called: SLO line, alert threshold, alarm limit. (2 captures) - [Time series](https://patterns.konigi.com/dashboards/time-series.md): People need to see how a value changed over time and when a change began. Also called: line chart, area chart, trend chart. (5 captures) - [Trace waterfall](https://patterns.konigi.com/dashboards/trace-waterfall.md): People need to see where time was spent within a single request. Also called: span waterfall, distributed trace, flame chart. (1 capture) ### Interaction Help people explore the data and return to views they use often. - [Compare periods](https://patterns.konigi.com/dashboards/compare-periods.md): People need to compare periods to judge whether a change is unusual. Also called: period over period, year over year, time shift. (3 captures) - [Cross-filter](https://patterns.konigi.com/dashboards/cross-filter.md): People need to select data in one panel and inspect the same records in other panels. Also called: brushing and linking, click to filter, coordinated views. (2 captures) - [Drill-down](https://patterns.konigi.com/dashboards/drill-down.md): People need to move from a summary to the records behind it while keeping their filters and time range. Also called: click through, expand to detail, navigate to scope. (2 captures) - [Hover detail](https://patterns.konigi.com/dashboards/hover-detail.md): People need exact values for a point without leaving the chart. Also called: tooltip, crosshair, shared crosshair. (1 capture) - [Saved view](https://patterns.konigi.com/dashboards/saved-view.md): People need to return to useful settings without recreating them each time. Also called: bookmark, saved search, personal dashboard. - [Search across panels](https://patterns.konigi.com/dashboards/search-across-panels.md): People need to find a panel or dashboard without knowing where it is stored. Also called: global search, find a metric, command palette. (4 captures) - [Template variable](https://patterns.konigi.com/dashboards/template-variable.md): People need to use one dashboard for different services, hosts, or environments. Also called: dashboard variable, global filter, environment switcher, scoped dashboard, parameterized dashboard. (1 capture) - [Zoom and pan on time](https://patterns.konigi.com/dashboards/zoom-and-pan.md): People need to focus on a brief event and explore the surrounding time period. Also called: drag to zoom, range brush, time navigation. (1 capture) ### Managing screen space Keep dashboards useful when content grows or the screen size changes. - [Collapsible row](https://patterns.konigi.com/dashboards/collapsible-row.md): People need a clear summary with less-used panels available when needed. Also called: panel group, section accordion. (1 capture) - [Detail on demand](https://patterns.konigi.com/dashboards/detail-on-demand.md): People need a closer look at one panel without losing their place in the dashboard. Also called: expand panel, full-screen panel, side panel. (2 captures) - [Mobile adaptation](https://patterns.konigi.com/dashboards/mobile-adaptation.md): People need to check important dashboard information on a phone. Also called: stacked cards, swipe between panels. (1 capture) - [Multi-page dashboard](https://patterns.konigi.com/dashboards/multi-page-dashboard.md): People need separate views when a dashboard covers too many questions for one page. Also called: tabs, sub-dashboards, dashboard set. (2 captures) - [Panel grid](https://patterns.konigi.com/dashboards/panel-grid.md): People need a clear arrangement of panels with enough space to read each one. Also called: widget grid, tile layout, dashboard canvas. (2 captures) - [Wallboard mode](https://patterns.konigi.com/dashboards/wallboard-mode.md): People need to read a shared dashboard from a distance without interacting with it. Also called: kiosk mode, TV mode, rotation. (1 capture) ### Organization and navigation Group related information and give people clear paths from summaries to details. - [Overview then detail](https://patterns.konigi.com/dashboards/overview-then-detail.md): People need to move from a broad overview to specific details without losing context. Also called: landing overview, hierarchical navigation, fleet-to-node. (4 captures) - [Semantic grouping](https://patterns.konigi.com/dashboards/semantic-grouping.md): People need related panels grouped together so they can find and compare them. Also called: grouped by service, grouped by team. (3 captures) - [Sidebar and canvas](https://patterns.konigi.com/dashboards/sidebar-and-canvas.md): People need to navigate between dashboards while keeping space for the data. Also called: nav rail plus dashboard, tree plus summary. (3 captures) - [Tabs as genres](https://patterns.konigi.com/dashboards/tabs-as-genres.md): People need distinct views for the different questions they ask of the same data. Also called: Overview / Content / Audience / Revenue. (3 captures) ### Page layout Arrange panels so people know where to start and can compare related information. - [Dense small-multiple layout](https://patterns.konigi.com/dashboards/dense-small-multiple-layout.md): Experienced users need to compare many related charts at once. Also called: Node Exporter style, wall of charts. (1 capture) - [Header KPI strip](https://patterns.konigi.com/dashboards/header-kpi-strip.md): People need a quick summary of the measures that require attention. Also called: top-row summary, hero metrics, summary row. (10 captures) - [Resizable card grid](https://patterns.konigi.com/dashboards/resizable-card-grid.md): People need to arrange shared dashboard panels to suit their own work. Also called: draggable widgets, customizable layout. (2 captures) - [Single-column narrative](https://patterns.konigi.com/dashboards/single-column-narrative.md): Occasional readers need a clear path through a dashboard’s main findings. Also called: one-screen dashboard, Plausible style. (1 capture) - [Two-pane list and detail](https://patterns.konigi.com/dashboards/two-pane-list-detail.md): People need to inspect items in a queue without losing their place in the list. Also called: issue list plus detail, master-detail. (1 capture) ### Color Use color to distinguish categories, compare values, and highlight warnings. - [Categorical series palette](https://patterns.konigi.com/dashboards/categorical-series-palette.md): People need to tell chart series apart and recognize them across views. Also called: series colors, qualitative palette. (4 captures) - [Dark-first data palette](https://patterns.konigi.com/dashboards/dark-first-data-palette.md): People need chart colors that remain readable on dark backgrounds. Also called: dark mode charts, NOC palette. (3 captures) - [Grayscale with alerts](https://patterns.konigi.com/dashboards/grayscale-with-alerts.md): People need warnings to stand out from routine information. Also called: ISA-101, muted-until-abnormal, high-performance HMI. (3 captures) - [Red/green direction coloring](https://patterns.konigi.com/dashboards/red-green-direction.md): People need to recognize upward and downward changes without relying on color alone. Also called: tick coloring, gain/loss color. (1 capture) - [Semantic status color](https://patterns.konigi.com/dashboards/semantic-status-color.md): People need consistent status cues to spot items requiring attention. Also called: good/warn/critical, severity scale, RAG. (11 captures) - [Sequential and diverging scales](https://patterns.konigi.com/dashboards/sequential-and-diverging-scales.md): People need color scales that clearly show value differences and meaningful reference points. Also called: heat scale, color ramp. (9 captures) ### Dashboard features Support filtering, sharing, and alerts, and explain when data is loading or unavailable. - [Alert rule attached to panel](https://patterns.konigi.com/dashboards/alert-rule.md): People need a notification when a metric requires attention. Also called: threshold alert, monitor from chart. (1 capture) - [Auto-insight](https://patterns.konigi.com/dashboards/auto-insight.md): People need help finding important changes across more data than they can inspect themselves. Also called: generated narrative, watchdog, anomaly feed. - [Comment and annotate](https://patterns.konigi.com/dashboards/comment-and-annotate.md): Teams need to discuss specific chart data and keep their findings attached to it. Also called: collaborative notes, panel comments. - [Dashboard builder](https://patterns.konigi.com/dashboards/dashboard-builder.md): People need to build dashboards for their own questions without relying on someone else for every change. Also called: add panel, edit mode, layout editor. (5 captures) - [Empty state](https://patterns.konigi.com/dashboards/empty-state.md): People need to know why a panel is empty and what to do next. Also called: no data yet, no results, zero state. (2 captures) - [Error and stale state](https://patterns.konigi.com/dashboards/error-and-stale-state.md): People need to distinguish valid results from missing, failed, or outdated data. Also called: data source down, partial data, degraded panel. (2 captures) - [Filter bar](https://patterns.konigi.com/dashboards/filter-bar.md): People need to narrow the data and see which filters are active. Also called: facet bar, query bar, filter chips. (6 captures) - [Loading and skeleton state](https://patterns.konigi.com/dashboards/loading-state.md): People need to know that data is still loading rather than missing or unavailable. Also called: skeleton, shimmer, placeholder panel. (1 capture) - [Metric targets](https://patterns.konigi.com/dashboards/metric-targets.md): Teams need an agreed goal that stays consistent across dashboards and alerts. Also called: set a goal, target line. (1 capture) - [Share and embed](https://patterns.konigi.com/dashboards/share-and-embed.md): People need to share a dashboard while preserving the context needed to understand it. Also called: public link, snapshot, iframe embed, scheduled export. (2 captures) ## Products Shared across libraries. Genre lives on the capture, not the product. - [Amplitude](https://patterns.konigi.com/products/amplitude): Builds the page around the question rather than the chart: funnels, retention grids and cohort comparisons are first-class objects, not panel types. Access: trial. Domains: product-analytics. - [Bloomberg Terminal](https://patterns.konigi.com/products/bloomberg-terminal): The densest display in the collection and the one with the most trained audience. Worth studying precisely because none of its choices would survive a usability test. Access: screenshots-only. Domains: banking-treasury, crypto-trading. - [Canvas](https://patterns.konigi.com/products/canvas): Progress and attainment read by a teacher about named students, where a red cell is about a person in the room rather than a server. Access: trial. Domains: education. - [Cloudflare Radar](https://patterns.konigi.com/products/cloudflare-radar): Public internet-traffic dashboards with location and time controls and links from summaries to detailed views. Access: live-public. Domains: security, infra-finops. - [Coinbase](https://patterns.konigi.com/products/coinbase): Consumer framing over a market display: the same order book and depth chart the professional products carry, deliberately buried a level down. Access: trial. Domains: crypto-trading, fintech-consumer. - [Datadog](https://patterns.konigi.com/products/datadog): Everything on one surface, which makes it the best place to see what a page looks like when the product refuses to choose between metrics, logs, traces and cost. Access: trial. Domains: observability-software, infra-finops, security. - [Epic](https://patterns.konigi.com/products/epic): The reference for the emergency department track board: every bed present whether occupied or not, read by a dozen roles who each need a different column. Access: screenshots-only. Domains: healthcare. - [Flexport](https://patterns.konigi.com/products/flexport): Freight in transit as a map and an exception list rather than a chart, because the question is which shipment is late, not what the average is. Access: screenshots-only. Domains: logistics. - [GitHub](https://patterns.konigi.com/products/github): The contribution calendar shows daily activity using a small set of color levels. Access: live-public. Domains: admin-devtools, devops-ci. - [Grafana](https://patterns.konigi.com/products/grafana): Examples of panel grids, shared selectors, stat tiles, and chart configuration. Access: live-public. Domains: observability-software, infra-finops, iot-energy. - [Home Assistant](https://patterns.konigi.com/products/home-assistant): Room-based card layouts combine household device states with controls. Access: live-public. Domains: iot-energy. - [Honeycomb](https://patterns.konigi.com/products/honeycomb): Query-driven views use heatmaps and selected regions to investigate differences between requests. Access: live-public. Domains: observability-software. - [HubSpot](https://patterns.konigi.com/products/hubspot): Pipeline by stage with a forecast on the same page, which is a dashboard carrying a projection and an actual in the same visual language. Access: trial. Domains: crm-sales. - [Ignition](https://patterns.konigi.com/products/ignition): A process-monitoring demo uses simulated plant data and offers simple or realistic equipment rendering. Access: live-public. Domains: iot-energy. - [Kibana](https://patterns.konigi.com/products/kibana): A query bar and filtering controls define the data shown in charts and document tables. Access: live-public. Domains: observability-software, security. - [Kraken Pro](https://patterns.konigi.com/products/kraken): A trading interface with price charts, an order book, and market-depth displays. Access: live-public. Domains: crypto-trading, fintech-consumer. - [LangSmith](https://patterns.konigi.com/products/langsmith): A trace waterfall for model calls, where the interesting span is usually the one waiting and the cost sits on the same axis as the latency. Access: trial. Domains: ai-llm-ops. - [Linear](https://patterns.konigi.com/products/linear): Almost no chrome and no configuration. A board where the layout is the data model, and the closest thing here to a dashboard with an editorial voice. Access: trial. Domains: project-management. - [Mixpanel](https://patterns.konigi.com/products/mixpanel): Board of saved reports rather than a designed page, which is what product analytics tends to become once more than one team is asking questions. Access: trial. Domains: product-analytics. - [Netdata](https://patterns.konigi.com/products/netdata): A large collection of system charts with per-chart controls and anomaly-rate views. Access: live-public. Domains: infra-finops, observability-software. - [PagerDuty](https://patterns.konigi.com/products/pagerduty): A queue rather than a chart. Two-pane list and detail with keyboard traversal, because the task is working through incidents rather than looking at them. Access: trial. Domains: support, observability-software. - [Plausible Analytics](https://patterns.konigi.com/products/plausible): A metric row controls the main chart, followed by focused traffic breakdowns. Access: live-public. Domains: product-analytics, seo-geo. - [Retool](https://patterns.konigi.com/products/retool): A builder aimed at people making internal tools, so it shows what a dashboard looks like when the person assembling it is the person who will use it. Access: trial. Domains: admin-devtools, embedded-analytics. - [Sentry](https://patterns.konigi.com/products/sentry): Issue-centric rather than metric-centric; the two-pane list-and-detail structure with sparklines inline on every row. Access: sandbox. Domains: observability-software. - [Shopify](https://patterns.konigi.com/products/shopify): Retail's weekly rhythm drawn against a comparison period by default, which is the only honest way to show a business with a Monday and a Black Friday. Access: trial. Domains: ecommerce. - [Stripe](https://patterns.konigi.com/products/stripe): The reference for a financial admin surface: dense tables with in-cell state, and a home page that is a small strip of numbers above a very long list. Access: trial. Domains: fintech-consumer, ecommerce, embedded-analytics. - [Tableau Public](https://patterns.konigi.com/products/tableau-public): Published workbooks show how individual authors arrange charts and interactions in Tableau. Access: live-public. Domains: embedded-analytics, product-analytics. - [Vercel](https://patterns.konigi.com/products/vercel): Deploy state, build logs and edge metrics in one console, with a log tail that has to stay readable while it moves. Access: trial. Domains: devops-ci, admin-devtools. - [VTS](https://patterns.konigi.com/products/vts): Occupancy and leasing pipeline over a horizon measured in years, which is the far end of the cadence range this collection covers. Access: screenshots-only. Domains: real-estate. - [Workday](https://patterns.konigi.com/products/workday): Headcount and attrition about identifiable people, which is the case where suppressing small numbers is a design requirement rather than a nicety. Access: screenshots-only. Domains: hr-people. - [YouTube Studio](https://patterns.konigi.com/products/youtube-studio): Analytics for an audience of one, about their own work, where the comparison that matters is against their own previous upload rather than against a benchmark. Access: trial. Domains: creator-media. - [Zendesk](https://patterns.konigi.com/products/zendesk): Queue depth and wait time for the people clearing the queue, with the same numbers again for the manager, on the same data and a different page. Access: trial. Domains: support. ## Facets Domains are shared across every library. Domains with content: - [Admin and devtools](https://patterns.konigi.com/domains/admin-devtools) - [AI and LLM ops](https://patterns.konigi.com/domains/ai-llm-ops) - [Banking and treasury](https://patterns.konigi.com/domains/banking-treasury) - [Creator and media](https://patterns.konigi.com/domains/creator-media) - [CRM and sales](https://patterns.konigi.com/domains/crm-sales) - [Crypto and trading](https://patterns.konigi.com/domains/crypto-trading) - [DevOps and CI](https://patterns.konigi.com/domains/devops-ci) - [Ecommerce](https://patterns.konigi.com/domains/ecommerce) - [Education](https://patterns.konigi.com/domains/education) - [Embedded analytics](https://patterns.konigi.com/domains/embedded-analytics) - [Consumer fintech](https://patterns.konigi.com/domains/fintech-consumer) - [Healthcare](https://patterns.konigi.com/domains/healthcare) - [HR and people](https://patterns.konigi.com/domains/hr-people) - [Infrastructure and FinOps](https://patterns.konigi.com/domains/infra-finops) - [IoT and energy](https://patterns.konigi.com/domains/iot-energy) - [Logistics](https://patterns.konigi.com/domains/logistics) - [Observability](https://patterns.konigi.com/domains/observability-software) - [Product analytics](https://patterns.konigi.com/domains/product-analytics) - [Project management](https://patterns.konigi.com/domains/project-management) - [Real estate](https://patterns.konigi.com/domains/real-estate) - [Security](https://patterns.konigi.com/domains/security) - [SEO and GEO](https://patterns.konigi.com/domains/seo-geo) - [Support](https://patterns.konigi.com/domains/support) Dashboards genres with content: - [Operational](https://patterns.konigi.com/dashboards/genres/operational) - [Tactical](https://patterns.konigi.com/dashboards/genres/tactical) - [Analytical](https://patterns.konigi.com/dashboards/genres/analytical) - [Personal](https://patterns.konigi.com/dashboards/genres/personal) - [Public](https://patterns.konigi.com/dashboards/genres/public) - [Wallboard](https://patterns.konigi.com/dashboards/genres/wallboard) ## Terms Screenshots are reproduced for commentary and criticism. Product names and marks belong to their owners. When citing an entry, link the canonical pattern URL and name the capture date; the captions are specific to the product version captured.