ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
UI experience · Charts

Charts ordered by the question they answer, not by the shape they make.

Magnitude, change over time, part to whole, distribution, correlation, hierarchy, flow and network, and radial. Thirty types across those eight families, each a view type on a result set and configured rather than coded — so the decision in front of a consultant is which encoding suits the question, not whether the charting library supports it. Sixteen of them are small enough to render inside a single grid cell, which is what lets a table read as a dashboard without becoming one.

A chord diagram of an energy system: forty-odd sources and sinks around a ring — thermal generation, wind, solar, oil, gas, nuclear, the electricity grid, industry, transport, heating — with weighted ribbons crossing between them, each coloured from its origin.
How a chart is made

The chart is wired to the columns, not built from them

A diagram: a result set of five columns on the left, each tagged as a dimension, a split or a measure; their connectors converging into a mapping card that names the measure, the split, the axis and the type; and that mapping feeding four renderings of the same data — line, bar, treemap and donut.

See these on your own numbers.

A 30-minute working session — a result set of yours rendered through several encodings, with the view type changed live. Architecture conversation, not a marketing demo.