DB
Get started
Back homeIndustry

Energy & utilities

Interval reads in compressed columnar tables, windowed KPIs and the current state of the grid in keyed tables, in one engine.

The problem

Where the usual stack breaks

  1. 01

    Smart-meter interval reads and grid sensor data are a stream with a long memory: billing needs years of durable history, operations needs the state of the grid right now, and both read the same streams.

  2. 02

    Splitting those needs across a historian, a cache and a warehouse multiplies schemas and makes the operational questions, which feeders are overloaded, which meters went dark, depend on pipeline lag.

  3. 03

    You want durable columnar history, keyed current state per meter or feeder, and windowed aggregation in the same SQL.

Where NYXDB fits

Use-case journeys

01

AMI interval ingest

Compressed columnar history that stays queryable for billing.

Time-series & monitoring
02

Grid observability

Live per-feeder metric relations maintained by the engine.

Observability & logs
03

Operations dashboards

Control-room views read keyed state and subscribe to live changes.

Real-time dashboards

Architecture

How NYXDB fits grid data

Interval reads land in columnar tables with codecs and an index on time; grouped transformations keep per-feeder totals current; keyed tables answer per-feeder and per-meter state questions.

  1. 01

    Durable ingest

    Every interval read is in the write-ahead log before it is acknowledged.

  2. 02

    Compact history

    History stays compact: COLUMNAR storage with DoubleDelta and ZSTD codecs, and a MINMAX index on the read time.

  3. 03

    Rollups

    Per-feeder totals stay current, maintained by grouped transformations; windows run in STREAM SELECT.

  4. 04

    Grid state

    The latest row per (feeder, metric), in an UPSERT table.

In practice

Representative query

The examples use the same two tables on every page. See the SQL reference for full syntax.

Current balances of one address
SELECT address, token, amount, updated_at
FROM balances
WHERE chain_id = 1 AND address = '0x9c2e4f1a';

Capabilities

What you get out of the box

Durable ingest

Write-ahead log persistence before acknowledgement.

Windowed KPIs

Tumbling and hopping windows in STREAM SELECT.

Keyed grid state

Latest row per feeder or meter.

Columnar history

Per-column codecs and MINMAX pruning.

Learn more

Go deeper

Storage

Profiles and codecs.

SELECT

GROUP BY and HAVING.

Transformations

Continuous rollups.

One engine from substation to billing

Explore the time-series solution or run a node.

Get startedRead the docs