Why we built an MIT Angular data grid instead of paying for the enterprise tier

Description and use

The team built an MIT‑licensed Angular data grid to replace expensive enterprise tiers, offering full features with a small footprint and no licensing fees.

Problem

Angular applications often require advanced data grid features (grouping, aggregation, Excel export, etc.) that are locked behind expensive enterprise licenses, creating cost, licensing, and maintenance burdens.

Outcome

inandu-grid delivers all enterprise‑level grid features under a single MIT license, eliminates per‑seat licensing costs, keeps bundle size small, and allows developers to manage data outside the grid.

Workflow

• 1. Identified feature gaps in lightweight grids and high cost of enterprise tiers.
• 2. Drafted a brief prioritizing MIT licensing, small footprint, Angular‑native design, and data‑agnostic API.
• 3. Designed inandu-grid as standalone components with signal‑based inputs/outputs.
• 4. Implemented core features: sorting, filtering, grouping, aggregation, export, inline editing, pagination.
• 5. Published the package @inandu-solutions/grid-angular on npm.
• 6. Integrated the grid into an Angular app using <inandu-grid> and <inandu-column> components.
• 7. Handled data mutations via emitted events (rowSave, rowCreate, rowDelete).

Evidence

We kept landing in pile 2, and kept bouncing off the same wall. This is why we ended up building inandu-grid — @inandu-solutions/grid-angular, MIT, every feature free — and the decisions that shaped it.

Source

The grid never owns your data. It consumes a plain array and emits every mutation — rowSave, rowCreate, rowDelete, selectionChange.

Source

MIT, in full. No tier. Row grouping, aggregates, CSV/Excel/PDF export, cell-range selection, inline editing — all in the one package, all under the one licence.

Source