Interactive examples · Free Core and Premium

Every chart. Every variant. Live.

Start with MIT-licensed Core charts and features. Premium flagships, specialist chart types and compositions are collected in their own paid section. Every example is labelled by what it requires.

Example directory · 528 original examples

528 original JavaScript chart examples: 333 Free Core and 195 Premium examples, with source pages, configuration references and an interactive data editor.

Read the complete directory as Markdown

Chart types

Line

Area

Column

Bar

Mixed / combo

Range area

Streamgraph

Waterfall

Dumbbell

Timeline / range bar

Funnel

Candlestick

Box plot

Violin

Raincloud

Histogram

Bubble

Scatter

Heatmap

Treemap

Sunburst

Icicle

Unit & pictogram

Beeswarm

Waffle

Slope

Pie & donut

Radial bar

Gauge

Radar

Polar area

Sparklines

Dashboards & interaction

Crossfilter dashboards

Custom series

Interactivity

Narrative & state

Trellis

Highlight filter

Core features

Drilldown

Link & crossfilter

Highlight filter

Perspectives

History / rewind

Storyboard

Narrative

Trellis

Canvas renderer

Theming

Themes

Labs

Type labs

Flagships

Quint-Semantics: an ops day on one time axis

  • Quint timeline: SaaS ops control room, 24 h · Premium

    Five lanes, one time axis: requests per 10 min coloured by error rate with deploys and pipeline runs, cost per cluster, error budget left (availability · p95 latency), p95 latency per service and traffic by region. Click to crossfilter, Esc clears.

    Original sample · Configuration Markdown · Edit data
  • Quint convergence: the 18:40 EU incident · Premium

    The same lanes with a labelled focus lens around the incident on eu-k8s-2 after the checkout v2.41 deploy. Each lane calls out its value at the incident; L or the lens button switches to a linear axis.

    Original sample · Configuration Markdown · Edit data
  • Three-lane convergence · Premium

    Requests, p95 latency and regional traffic with a ×6 lens and 30 min of context on each side.

    Original sample · Configuration Markdown · Edit data
  • Quint semantics on a clock: SaaS ops, 24 h · Premium

    The Quint timeline's data on one ring (24 h clock, UTC, 10-min slots). Outside: requests per 10 min, colour = error rate, rim band = vs a typical day, ◆ deploys, ● pipeline runs, red ◆ the 18:40 alert. Inside, aligned with the slots: cost per cluster (€ / h; eu-k8s-2, eu-k8s-1, us-k8s-1 from the outside in) and p95 latency (ms; Checkout, Payments, Search, also from the outside in) as named heatmap rings, brighter = higher (log colour scale, keyed under the ring; "All 6 rows" shows every service and cluster); then error budget left per service over 30 days (legend %, ring label: availability · p95 latency) and Region › Service traffic (M requests in 24 h). The red wedge marks the incident 18:40–19:20 across every ring: hover or pin a slot in it and eu-k8s-2 cost, Checkout latency and EU traffic light up together. Compact screens keep every 10-minute slot and every displayed service/cluster row; only the empty centre, ring gaps and legend placement shrink. The two heat layers still show the explicitly named three-row story selection, not an aggregate of six rows.

    Original sample · Configuration Markdown · Edit data

Medicine & practice

Ops control rooms

  • Quad semantics: SaaS ops control room, 24 h · Premium

    Four layers keyed by service and time. Outside: requests per 10 min (colour = error rate, rim band = vs a typical day, ◆ deploys, ● pipeline runs). Then cost per cluster (labelled by cluster type), per-service error budget left (ring label: availability · p95 latency), and Region › Service traffic at the core. Click a service, a cluster or a time slot to pin it; Esc clears. The story: an EU spike at 18:40 on eu-k8s-2 right after checkout v2.41. Compact layout retains every time slot, all six service budgets, all cluster costs and both Region › Service depths; ring space is shared by actual ring count.

    Original sample · Configuration Markdown · Edit data
  • Nested radial cascade: four levels of one incident · Premium

    One ring, four levels: Sector › Subsystem › 48 components › anomalies, with dependency ribbons at the core and the last six hours as a heat ring. The story: the 18:20 checkout deploy pushes eu gateways, queues, redis and postgres into the red, and it shows up as revenue at risk. Hover or click any level; the others follow.

    Original sample · Configuration Markdown · Edit data
  • Matrix lattice: status grid linked to relation flows · Premium

    A service × cluster status grid (worst severity per cell, with glyphs so it reads without colour) is linked by crossfilter to severity and cause charts and to a cause › service › impact flow. Click a cell, a severity or a cause; everything else, the flow and the summary narrow to the matching signals. Esc or a summary chip clears.

    Original sample · Configuration Markdown · Edit data
  • Net lattice: cluster topology with anomaly badges · Premium

    Six clusters as soft hulls (macro topology), their services as nodes (size = requests/s), relations as weighted edges, and anomaly nodes coloured by severity with an S1/S2/S3 badge in the label. The red edges trace the propagation path of the eu-west-2 incident. Switch to the bundled macro view, click a node for its details.

    Original sample · Configuration Markdown · Edit data
  • Matrix core: service calls inside error budgets and latency · Premium

    The centre is a call matrix (row calls column, req/s); around it the error budget left per service; outside the p95 latency per service in 4-hour windows. Every layer is keyed by service. Hover a cell to light both services in each ring and the reverse call; hover a header to light its whole row or column. Arrow keys move through the grid. The story: Matching is hot in the evening and has burnt most of its budget. Below 600 px, all eight current error budgets become one service-aligned heat band, each percentage repeated unchanged over that service's six windows (not a time series). The full 8 × 8 calls matrix and all 48 latency windows remain. EDG/RID/DRV/MAT/PRC/GEO/PAY/NTF abbreviate the same full service names in tooltips and matrix headers.

    Original sample · Configuration Markdown · Edit data
  • Matrix core: health checks, owners and 14 days of alerts · Premium

    A status grid of ten services × six checks. Severity is colour and pattern (solid ok, dots info, hatch warning, cross-hatch critical), so it reads without hue. Around it the owning teams; outside the alert minutes per service over two weeks. Hover a status in the legend to find it; click it to hide those cells. A check lights the service-days it fired on (the last four days of each service where it fails).

    Original sample · Configuration Markdown · Edit data

Facet network

Multi-semantic radial

Orientation

  • Orientation: the SaaS clock turned to the evening incident · Premium

    The quint clock opens turned 90° so the evening sits on top: 18:00 at 12 o'clock, the 00:00 start at 3 o'clock (bold label, dashed seam). Every ring — latency, cost, error budget, traffic, the incident wedge — turns with the bars. Use the buttons top right, [ and ] on the focused chart (3-hour steps), Home to reset, or double-click a slot (Shift+Enter on a focused one) to bring it to the top. The turn is part of the view state and share link. Compact screens keep every 10-minute slot and every displayed service/cluster row; only the empty centre, ring gaps and legend placement shrink. The two heat layers still show the explicitly named three-row story selection, not an aggregate of six rows.

    Original sample · Configuration Markdown · Edit data
  • Orientation: goal rings turned to the second half of the month · Premium

    The team goal rings with the month around them, turned so day 16 opens at the top. The goal arcs, their laps and shadows turn with the day ring; the ring names and the legend stay level. Rotate in three-day steps with [ and ], or pick a day or a goal: a goal arc brings its end — where the team stands now — to the target. Compact layout keeps all seven teams and all thirty days, puts the complete goal legend below the dial and uses a smaller empty centre.

    Original sample · Configuration Markdown · Edit data

Wave ring

  • Wave ring: a week of cluster load cycles · Premium

    Seven day sectors, one smooth lane per cluster (CPU %, the inner lane in front). The grey band is each cluster's normal range, the hatched band and dashed crest the forecast after now (Sun 14:00), ◆ points outside the normal range (also on the rim). Outside: requests per hour; inside: cost per cluster, keyed to the lanes. Hover a lane for the hour across all clusters, a day for its 24 columns.

    Original sample · Configuration Markdown · Edit data
  • Wave ring: the seasonal cycle of a typical day · Premium

    A 300° ring of months; in each sector the typical day (00–24 h) of solar, wind and grid supply, stacked (GW). Solar swells towards summer, wind towards winter, the grid fills the evening gap. Sectors link to the monthly totals outside by name; the core shows the annual mix.

    Original sample · Configuration Markdown · Edit data

Chord inside

Triple semantics

Linked layers

Time rings & goals

  • Time ring: a week of chats, hour by hour · Premium

    A heatmap ring (Monday inside, Sunday outside, one cell per hour) sits under the hourly totals: the cells share the columns' angles, so hovering an hour lights that hour on every day and the tooltip lists the seven days. In the middle a polar area of the channel mix (radius = volume, independent of the ring). Compact layout retains the seven separate days × 24 hours and all five channels; no weekday averaging or row omission is applied.

    Original sample · Configuration Markdown · Edit data
  • Team goals: seven rings inside a month of output · Premium

    Activity-style goal rings, one per team (any number; thickness and gaps adapt to the space). Past 100 % a ring laps over itself, the end cap casts a soft shadow. Outside: work items shipped per day. Hover a ring to light the days that team hit its daily target; hover a day to see which teams did. Compact layout keeps all seven teams and all thirty days, puts the complete goal legend below the dial and uses a smaller empty centre.

    Original sample · Configuration Markdown · Edit data
  • Server load live: gauge now, ring = last 60 minutes · Premium

    The gauge in the middle is the current load; the column ring is the same metric over the last 60 minutes, newest at the dashed “now” tick. Every tick the gauge animates and the oldest minute rolls off the ring (simulated; pauses while the tab is hidden).

    Original sample · Configuration Markdown · Edit data

Radial column basics

Chart types

Sankey

Gantt

Tree

Stock

Maps

Originals: variants

WCC originals

Open page