Skip to content
NewYour data: charts, lists and meters that take your records

Your data

Which components take your records through a data input, and which only show demo data and are templates.

View as Markdown

Every component runs on its own, so the ones that display records (series, rows, certificates, rules) come with demo data. The demo data is invented. It is there so a preview works, never to be shown to your users.

Each component page says, right under the preview, which kind it is:

  • Your data: the component takes your records or values, through data or the attributes its note names. It shows demo data only until you pass them, and with your data nothing invented is mixed in: no generated values, no simulated live updates.
  • Demo data: the component cannot show your own data yet. Some of them take a label or a single value, but the records they show are invented. Use them as templates: the source is yours, so replace the invented data before it shows anything real.

Components without a note display no data of their own, such as buttons, sliders and inputs.

Passing data

Components with records to show take them as data, a property and an attribute. As a property it takes the records directly; as an attribute it takes the same records as JSON. The React wrappers accept arrays and objects and write the JSON for you.

React
import { HfArea } from "@/components/lumesec/hf-area";

export function TokenUsage({ days }: { days: { date: string; value: number }[] }) {
  return <HfArea label="Tokens per day" data={days} />;
}
HTML
<hf-area id="usage" label="Tokens per day"></hf-area>

<script type="module">
  const res = await fetch("/api/usage");
  document.getElementById("usage").data = await res.json();
</script>

data is observed: set it again and the component updates, animating where it can. Invalid entries are skipped, invalid JSON logs a warning, and an empty array shows an empty state rather than demo data. Each component page lists the exact record type under Attributes and Properties, and some add methods such as push() for live feeds.

The native React components (Location and some Pixel UI components) take your records through typed props instead, such as region and latency on the region badge. Each component page names them.

Components that take your data

Pixel Lab · 9

  • Rate-limit hourglassSet duration to the seconds left until your limit resets, and again whenever you learn a new value; nothing else is shown.
  • Split-flap boardPass your messages in messages or call show(). Without them the board cycles demo messages.
  • Materializing streamPass your sentence as text. Without it a sample sentence streams.
  • Secret fieldPass your key as value. Without it the field shows a fake demo key.
  • Status orbSet the agent's state with state. Without it the orb starts at thinking.
  • Pixel reactionsPass the starting reaction count as count. Without it the count starts at 128.
  • Pixel checklistPass your tasks in items. Without it the list shows demo tasks.
  • Notification bellPass the unread count as count and call notify() or clearAll(). Without it the bell starts at 2 unread.
  • Uptime historyPass your daily uptime records per service as data. Without it the element shows demo services and statuses.

Pixel UI · 3

  • Search with resultsPass your entries as items, and label and placeholder to describe them. Without items it searches 14 invented settings pages.
  • SparklinePass your series as data. Without it the sparkline shows an invented sample series.
  • Bar chartPass your bars as data. Without it the chart shows a sample week of seven invented values.

Pixel HD · 17

  • ProgressSet value from 0 to 100, or omit it for an indeterminate bar. The bubbles are decoration, not data.
  • GaugeSet value (with min, max and zones). Without it the gauge shows a demo value.
  • Goal ringsPass up to three Name:current/goal rings as rings. Without it the rings show invented usage figures.
  • CountdownSet the duration in seconds or call restart(seconds). Without it a demo countdown of 2 h 14 min 9 s runs.
  • Area chartPass your daily values as data. Without it the chart shows demo data seeded from label.
  • DonutPass your Label:value segments as data (and total for the centre). Without it the chart shows invented usage shares.
  • Stat tileSet value, delta and the sparkline data. Without them the tile shows a demo number, a demo delta and a generated sparkline.
  • FunnelPass your Label:count stages as data. Without it the funnel shows invented visitor counts.
  • Bar listPass your label:value rows as data; the read-only items property returns them parsed. Without it the list shows demo file names with invented edit counts.
  • Secret fieldPass the value to hide as secret. Without it a demo API key is shown.
  • Range filterPass your histogram as data and the count factor as scale. Without data the histogram is a generated demo distribution.
  • Filter chipsPass your chips and counts as options (Label:count). Without it the chips show demo languages with invented counts.
  • Diff reviewPass your unified diff as the element's text content. Without it a built-in sample diff is shown.
  • Changed filesPass your changed files as paths (path:M, :A or :D). Without it a demo path list is shown.
  • PII redactionPass your text as the element's text content and the names to redact as names. Without them a built-in sample is redacted.
  • CandlesticksPass your OHLC candles as data and stream new ones with push(). Without it the chart shows a demo random walk that ticks live.
  • Live leaderboardPass your rows as data ({ name, value }); they are ranked and re-ranked as you update them. Without it six demo teams receive random score increases.

Location · 29

  • Connection globePass your places as locations and your connections as connections, or call push() on the ref for a live feed. Without connections the globe plays a seeded demo stream between 12 demo regions.
  • Horizon globePass your pairs of places as connections. Without it the component shows arcs between demo cities, and between demo land points where no two cities are on the visible cap.
  • Day and nightPass your places as cities. Without it the globe shows lights for 60 demo cities.
  • Event spikesPass your counts per location as data. Without it the component shows demo counts for 24 cities.
  • Globe to mapPass your routes as routes. Without it the component shows 8 demo routes between cloud regions; an empty array shows the land with no routes.
  • Region badgePass your region as region (an id from your regions or a region object) and your measured round trip as latency. Without them the badge shows the built-in region eu-central and no latency.
  • Marker mapPass your places as markers. Without it the map shows 14 demo cities with invented request counts.
  • Live visitorsPass your visits as events, or add them with push() through ref. Without events the component shows a seeded demo stream of invented visits.
  • Region trafficPass your regions as regions and your traffic as flows. Without either the component shows 12 demo cloud regions and 14 demo flows with invented throughput that drifts every 3 s; regions alone shows an empty map.
  • Country valuesPass your values per country as data. Without it the component shows demo values for 41 countries.
  • Clustered mapPass your locations as points ({ id, lat, lon, label? }). Without it the component shows 600 demo points around large cities: tight metro groups plus a wider scatter across each region.
  • Location cellPass your place as location ({ lat, lon, label?, detail?, timeZone? }) and, for the distance row, a reference point as from. Without location the cell shows a demo location (Singapore).
  • Anycast catchmentPass your points of presence as sites, the ids in service as active and your request sources as clients. Without sites the component shows ten demo sites with demo traffic from 60 cities; your sites without clients show no request numbers.
  • Mesh connectionsPass this device as device, the other devices as peers, your relay servers as relays and the current path to each peer as paths. Only while all four are undefined does the component show its demo: a laptop in Amsterdam with 6 invented peers in Europe and North America, 3 relays and invented latencies, each relayed peer going through the relay nearest to it, playing a seeded sequence of upgrades and fallbacks. Once any of them is given, the others default to empty.
  • TraceroutePass your trace as hops. Without it the component shows an invented 11-hop demo trace from a home router through Frankfurt, Marseille and Mumbai to Singapore, with private and documentation-range addresses and example.net names.
  • Latency matrixPass your regions as regions and your round-trip times as measurements. Without either the component shows eight demo regions with demo latencies (the fibre minimum times a seeded stretch of 1.3 to 1.9); regions alone shows every pair as "no data".
  • Global checksPass your probe locations as probes and each round's results as a new results array, with onRun to start a check from the button. Without results the component runs demo rounds with invented latencies.
  • Distance from herePass your places as places. Without it the component shows 15 demo cities, centred on London.
  • Sign-in travelPass your sign-ins as signIns. Without it the component shows six invented demo sign-ins.
  • Attack originsPass your requests as events, or call push() on the ref for a live feed; an empty array shows "No requests in the last minute". Without events the component shows a seeded demo stream of about four requests a second, 80 % blocked, from invented sources around real cities, on a prefilled window of invented counts.
  • GeofencePass your tracked devices as devices and your zones as zones or defaultZones. Without devices the component shows six demo trackers on a simulated walk.
  • Active sessionsPass your sessions as sessions (or defaultSessions) and sign them out in onRevoke. Without them the component shows six invented demo sessions.
  • Data residencyPass your jurisdiction as zone, your sites as sites and the data moving between them as transfers. Without sites and transfers the component shows invented demo data: the zone Germany, five sites (Frankfurt, Berlin, Hamburg, Dublin and a us-east region) and three transfers.
  • IP lookupPass your lookup as resolve. Without it the component invents a location for every public address from a hash of the address, which is only useful for demos.
  • Region pickerPass your regions as regions and the user's location as from. Without regions the picker shows 16 demo regions; nothing about the viewer's location is read or inferred.
  • Location pickerPass your own places as places. Without it the search and snapping use 60 demo cities; nothing about the viewer's location is read or inferred, and the picker starts without a pin unless you pass one.
  • Area selectPass your records as points ({ lat, lon }). Without it the map shows 2,400 seeded demo points around 60 large cities and starts with a box over Europe; with your points nothing invented is added and the area starts empty unless you pass defaultValue. An empty array shows no points and hides the count. Nothing about the viewer's location is read or inferred.
  • Meeting plannerPass your rows as cities (or defaultCities): { id, label, timeZone }. Without either the component shows London, Berlin, New York and São Paulo. Nothing reads the viewer's time zone: the window follows the reference city, and the cursor starts at the current instant only when neither value nor defaultValue is set.
  • Route playbackPass your recorded positions as track. Without it the component plays an invented 23-day container-ship voyage from Rotterdam to Singapore via Suez, with port stops at Algeciras, Port Said, Jeddah and Colombo. An empty array shows an empty map.

Components with demo data only

Pixel Lab · 26

  • Agent workflowThe planner, the four agents and their run times are invented; nothing can be set.
  • Throughput gaugeThe tokens-per-second reading is simulated; only max can be set.
  • Voice inputNo microphone is used and the audio levels are generated; only the transcript can be set with text.
  • Model morphThe three models and their speed, depth and cost scores are invented; nothing can be set.
  • Fader & meterThe meter signal is simulated; only the fader position is a real control.
  • Histogram rangeThe response-time histogram and its run counts are invented; only the selected range is a real control.
  • Slide to deployThe deploy run and the Live state are simulated on a timer, not on your deploy; only version can be set.
  • Activity heatmapThe daily activity counts are generated from each date; nothing can be set.
  • Storage ringThe storage categories and their sizes are invented; nothing can be set.
  • Latency scopeThe latency samples, spikes and p50/p95 readout are simulated; nothing can be set.
  • Pixel uploadNothing is uploaded and the progress is simulated; the file name and size come from the chosen file and limit-mb can be set.
  • Level upThe starting XP of 196 is invented; only level can be set and gain() adds to it.
  • Dissolve to deleteThe five chats are invented; nothing can be set.
  • Release rocketThe countdown and the live state run on a timer, not on your release; only version can be set.
  • Radio tunerThe four radio stations are invented; nothing can be set.
  • EqualizerThe spectrum behind the bands is simulated; only the bands are a real control.
  • Jog wheelThe filmstrip footage and its length are generated; nothing can be set.
  • Context waffleThe starting context usage per source is invented; add() and compact() change it but it cannot be set.
  • LED tickerThe ticker items (model, latency, errors, agents, uptime) are invented; nothing can be set.
  • Service radarThe six service nodes and their latencies are invented; nothing can be set.
  • Waveform playerThe track, its length and its waveform are invented and no audio plays; nothing can be set.
  • Request globeThe regions, the traffic between them, the latencies and the request counter are simulated; nothing can be set.
  • Code minimapThe code is generated sample JavaScript; only the search query can be set with find().
  • Diffusion previewThe prompts and images are painted procedurally and no model is involved; nothing can be set.
  • Snake stepperThe five onboarding steps and their subtitles are fixed demo content; nothing can be set.
  • Usage batteryThe usage level starting at 64% and the Monday 09:00 reset time are invented; nothing can be set.

Pixel HD · 22

  • Drop zoneUpload progress is simulated on a timer; only the file names and sizes come from the files the user drops.
  • PricingThe −20% badge on Yearly is fixed text, not computed; plan, prices, currency and features can be set.
  • Context windowThe 200k window and its four segment sizes are invented; only addTo() and compact() change them.
  • UptimeDaily status and uptime are generated from a hash of name; only incidents and state override them.
  • TerminalCommands and their output are built-in demo content; print() adds your own lines.
  • Agent runStep durations are random and the token count is generated; only the step labels, label and the failing step can be set.
  • Streaming replyThe streaming, its timing and the tokens-per-second figures are simulated; only the text can be set.
  • @mention fieldThe six suggestions (files, people and an agent) are invented; only label, placeholder and value can be set.
  • Permission promptIt starts on, and its Next request button cycles through, four built-in demo requests; request() shows your own.
  • Agent graphThe agent graph, its labels and the run timings (partly random) are invented; only label and autoplay can be set.
  • CheckpointsThe five checkpoints and their code are invented; only label can be set.
  • Sources and citationsThe paragraph, citations and sources are invented; nothing can be set.
  • Usage heatmapThe weekday-by-hour message and token counts are synthetic; only label can be set.
  • Scatter with brushThe 270 runs in three model groups are seeded random points; only label can be set.
  • FlowThe sources, models and 100k request split are invented; only label can be set.
  • RoadmapThe six tasks, their dates and progress and the today line are invented; only label can be set.
  • Radial barsThe monthly values for 2025 and 2026 and the highlighted current month are invented; only label can be set.
  • Logo marqueeThe ten wordmarks are fictional placeholder logos; only label can be set.
  • Kanban boardThe three columns and six cards are invented; nothing can be set.
  • CarouselThe four slides, generated scenes with built-in captions, cannot be replaced; nothing can be set.
  • Product tourThe mock app and its four tour steps are built in; nothing can be set.
  • Before and afterThe document and its personal data are invented; nothing can be set.

Was this page helpful?