grid, dashboards, Gantt, Kanban, forms
Build data-driven applications on a high-performance data grid.
Statistical analysis, Gantt, Kanban and forms built in, joined by a data routing engine, all on the same live data.
Explain the total
Compare groups on monthly cost
Used in production by
pick your product
One grid, and a view for every kind of work.
Each card is a running component. Open the section that matches what you are building.
-
Grid
Compare groups, explain a number, cluster rows and derive grids, computed from the live rows in the browser.
Open section: Grid → -
Dashboards
KPI tiles, charts and maps on the rows you already have, built in the Designer or in code.
Open section: Dashboards → -
Scheduler
People and machines allocated to work, with over-allocation flagged.
Open section: Scheduler →
the analysis, in one demo
Derive, compare, explain and cluster, on one dataset.
Five thousand generated cloud-cost rows, all in your browser. Filter the grid and every result is worked out again over the rows that are left.
A second grid built from the first: cost rolled up by service. Filter the grid above and this one recomputes over what is left. Derived grids →
Tick two or more services and the grid picks the test, then reports the p-value, the interval on the difference and the verdict. Compare groups demo →
What the total is made of, ranked with each share. It follows the filters, so narrow to one environment and read it again. Explain a number →
The Segment column gives every row a cluster over cost and change. The centres and sizes below are read from the grid, and re-found as you filter. Clustering demo →
one feed, every view
One live feed drives a whole screen of linked views.
Orders, shipments and incidents land on a single stream. Point one router at it, partition it by what each record is, and every grid and chart fills with only its own slice, live. No connection per panel.
works in your stack
Start in the framework you already work in.
Open a running example, copy the starter into your own page. Prefer markup over script? The htmx pages start from a plain server-rendered table.
-
JavaScript
import { createGrid } from '@toclocoinc/lattice-grid';Open the example → -
React
import { createLatticeGrid } from '@toclocoinc/lattice-grid/modules/react';Open the example → -
Vue
import { createLatticeVue } from '@toclocoinc/lattice-grid/modules/vue';Open the example → -
Svelte
import Grid from '@toclocoinc/lattice-grid/svelte/Grid.svelte';Open the example → -
Angular
import { LatticeGridComponent, provideLattice } from '@toclocoinc/lattice-grid/angular';Open the example → -
Web Component
import '@toclocoinc/lattice-grid/modules/webcomponent';Open the example → -
htmx
<table id="circuits" data-lattice-grid>Open the example → -
Python
import lattice_grid_dashOpen the example →
one licence
Free on localhost. One licence to ship.
| You are | You need | You get |
|---|---|---|
| Building on your machine | Nothing | The full grid on localhost, no key and no time limit. |
| Testing on staging, preview or CI | Nothing | The full grid with a small watermark. Nothing breaks. |
| A personal, teaching or open-source project | The non-commercial key | No watermark. One domain, six months, renewable. |
| Shipping a product or an internal tool | A licence per domain, $1,000 each | No watermark, unlimited developers and a year of support. |
Free on localhost Full pricing and what counts as a domain →