Where does the dashboard data come from?

From collections you declare, seeded with realistic records, or from an external read-only source fetched through a server route and cached. Either way the app reads through one runtime contract rather than a hard-coded array.

Are the charts real or images?

Real components, platform-owned and immutable, fed by the data series in your model. A reachable chart with an empty series is treated as an unfinished placeholder and fails the build.

Is a generated dashboard usable with a screen reader?

Chart and map surfaces ship an accessible equivalent of the same data alongside the visual, and every route is scored for accessibility in a real browser before publishing.

Can I restrict who sees it?

Yes. Publish behind a password or restrict access to named workspace members, and declare roles in the model so different people get different generated views.

AI dashboard generator

Generate an internal dashboard that is readable without a mouse.

Tervane generates operational dashboards — metrics, pipelines, tables, and charts — from platform-owned components that ship with accessible equivalents and are checked in a real browser before publishing.

Generate a dashboard Browse dashboard starters

Platform-owned surfaces

Charts, tables, and map surfaces come from immutable platform components rather than markup improvised per project.

Accessible by construction

Chart and map surfaces ship a screen-reader equivalent of the same data, not a decorative image.

Checked in a browser

Every route is loaded in real headless Chromium and scored on layout, hierarchy, and accessibility before it can be published.

Finance, CRM, inventory, and content starters.

Empty, loading, and error states generated with the happy path.

Light and dark, both contrast-validated.

Generated dashboards usually fail on the second screen

The first screen of a generated dashboard is easy: some cards, a chart, a table with plausible rows. The failures show up immediately afterwards — a chart with no data series, a table that has no empty state, a filter that renders but filters nothing, or a metric card that is a picture of a number rather than a number.

Tervane treats those as build failures rather than cosmetic issues. A reachable chart surface with an empty data series is a diagnostic that has to be repaired before the artifact is accepted.

Charts and tables come from the platform, not the model

Data-dense components are the ones most worth not improvising. Chart, table, and map surfaces are platform-owned and immutable: the model chooses where they go and what data feeds them, and cannot rewrite their internals or replace them with demo markup.

That is what makes their accessibility guarantees hold. A chart ships with a screen-reader-readable version of the same series, and a map surface ships a focusable list of the same locations, because those come with the component rather than depending on the model remembering to add them.

The states that operational tools actually spend their time in

Internal tools live in their edge states. A dashboard is empty on day one, loading on a slow connection, and showing an error when a source is down — and those are the states a demo never shows.

Generated interactive elements are held to a full state set including hover, focus-visible, active, disabled, loading, empty, and error, and motion honours the visitor's reduced-motion setting at the token level rather than as an afterthought.

Legible in both themes, on the screen you actually use

Each design pack ships two authored colour schemes, and both are contrast-validated against the same rules before generation begins — a dashboard that is readable in light mode and muddy in dark mode fails that check rather than shipping.

Rendered screenshots are captured at phone, tablet, and desktop widths and scored across several dimensions independently, so a route cannot pass on a strong average while one dimension is broken.

Frequently asked questions

Where does the dashboard data come from?: From collections you declare, seeded with realistic records, or from an external read-only source fetched through a server route and cached. Either way the app reads through one runtime contract rather than a hard-coded array.
Are the charts real or images?: Real components, platform-owned and immutable, fed by the data series in your model. A reachable chart with an empty series is treated as an unfinished placeholder and fails the build.
Is a generated dashboard usable with a screen reader?: Chart and map surfaces ship an accessible equivalent of the same data alongside the visual, and every route is scored for accessibility in a real browser before publishing.
Can I restrict who sees it?: Yes. Publish behind a password or restrict access to named workspace members, and declare roles in the model so different people get different generated views.