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 →

Gantt, timeline, kanban, calendar and D3 charts as configured views of a query

A query becomes a Gantt with editable tasks, a timeline with grouping, a kanban, a calendar whose events are dragged, or a D3 dendrogram, flowchart, graph or org chart, through JSON view configuration rather than code.

A list of rows is one way to see a query. Over two years the platform added the others, each as a view type configured in JSON on the object rather than programmed in the client.

The views

  • D3 charts An advanced chart view type, then dendrogram, flowchart, graph, org chart and tangled tree sharing one zoom controller, and a process flow chart of some 1,300 lines.
  • Gantt Opaque tasks, start expanded, a group column, and task editing in place.
  • Timeline Item grouping, and a timeline that joins the table view types.
  • Calendar A second-generation calendar with event creation, editing and deletion, events moved by dragging, and events created from a dragged range.
  • Battery charts with thresholds.

Configured, not coded

  • View configuration as JSON A processor registry reads the configuration per view type; tree, list and timeline migrated to it first.

The analytical card was the first of these to reach the blog. The rest shipped quietly over two years and deserve their own entry.