Grid Preview

One control, four ways to look at the same records, and a renderer whose frame costs the same for twenty columns as for a million, and for a thousand rows as for a hundred million.

The showcase “Order cockpit” scene, dark theme: a master grid with badges, a column of order cards, a region-by-status pivot and a revenue chart, all in one window. The showcase “Order cockpit” scene, light theme: a master grid with badges, a column of order cards, a region-by-status pivot and a revenue chart, all in one window.
The showcase “Order cockpit” scene: one order book, four views on the same live objects — master grid, cards, a region × status pivot and a chart; a ticker changes orders every 400 ms. Avalonia host, screenshot of the running app (0.1.0-preview.1). Pivot and chart are Pro modules.

What the table does

Pro modules

Separate NuGet packages on top of the open engine, documented chapter by chapter — free during the preview, also commercially (see Pricing).

The layers hold

Each layer names only what sits below it, and that boundary is enforced by tests rather than merely intended.

ArionUI.Core
The engine: virtualization, layout solver, scroll physics, interaction and the data sources. No UI framework — no Avalonia, WPF or Skia type appears anywhere in it.
ArionUI.Presentation
Views, column definitions, the cell composition model and theming. Framework-neutral.
ArionUI.Grid
The grid itself — panes, input wiring, the consumer API ArionGridApi, accessibility. It draws only through IRenderSurface.
ArionUI.Gpu and ArionUI.Rendering.Skia
OpenGL ES 3.0 through a host-supplied loader, and the single Skia renderer shared by every host.
ArionUI.Rendering.Avalonia, .Wpf and .WinForms
Thin hosts: input mapping, a surface and a frame clock. Because the renderer is shared, all three draw the same frame.

Measured in both directions

Frame cost while scrolling, WPF host20 × 1,00020,000 × 1,000,0001,000,000 × 100,000,000
Vertically0.86 ms1.04 ms1.02 ms
Horizontally, far right(too narrow)1.00 ms1.00 ms
Time to first picture1.0 s0.7 s5.4 s
Managed memory35 MB77 MB1.84 GB

Columns × rows. Median of the best of three runs, maximized window (grid 1920 × 1129), Intel laptop GPU (i7-11800H, UHD Graphics), 60 Hz display, measured on 31 October 2026 on 0.1.0-preview.2. All three hosts held the display rate while scrolling. A million columns cost their setup once, not every frame.

Built for the GPU

ArionUI is built for the GPU: plain table cells go to it in one instanced draw call from the engine's own shader program, and the frame follows the visible area, not your data. Everything else is for emergencies and special cases, such as a remote session without a GPU: the Avalonia host then switches to a CPU path that repaints only the strip newly scrolled into view, and the WPF and WinForms hosts keep drawing through ANGLE, which can land on a software rasterizer. Either way it logs what it did. Hosting and rendering has the details, Performance what stays in your hands, and why virtualizing rows is not enough how this differs from a control per row.

What it does not do yet

Stated here rather than discovered later.

What was built most recently, and what is not planned: Roadmap. Whole windows around the grid — boards, style sheets, drawn controls — are on Board & Styling. Coming from WinForms: Replace a DataGridView without rewriting the form.

Licence and source

The engine is open source under the Apache License 2.0, patent grant included; the source and the issues are on GitHub. The Pro modules are NuGet packages without source, free during the preview.

github.com/ArionUI/ArionUI