Create beautiful, interactive reports — entirely offline. AI agents or humans, CLI or editor, your machine or your server. Publish anywhere, or don't publish at all.
No AI agent? Just open the editor
npx richview
generate
report.json
-o
report.html
An agent creates a report spec via the CLI or MCP server. Charts, tables, prose sections, annotations — everything described as a structured document.
RichView's verification pipeline checks for rendering issues: overlapping legends, unreadable font sizes, truncated labels, data label collisions. Agents self-correct before publishing.
One command publishes to a shareable URL. No deployment config, no build step. The report is live, interactive, and version-tracked.
Every section in a RichView report toggles between write and read mode with Ctrl+Enter. In write mode, you see the chart builder, the text editor, the data bindings. In read mode, you see the published output — exactly as your audience will.
The inline chart editor works entirely without AI. A step-by-step manual builder walks you through data mapping, chart type selection, axis configuration, and annotation placement. No modals. No context switches. Everything happens in the document flow, like cells in a computational notebook.
When AI does assist, it proposes edits — never overwrites. You accept, reject, or modify each suggestion. The analyst is always the curator, never the passenger.
Bar, line, scatter, area, pie, heatmap, and table. ECharts under the hood, but you never see the raw config. Our internal chart spec handles data binding, axis formatting, and responsive sizing. Annotations — data point callouts, range highlights, trend lines — are first-class citizens.
Switches via prefers-color-scheme. No settings UI. Dark
mode feels like reading by warm lamplight — warm sand neutrals, not
inverted neon.
Pull quotes that shrink-wrap to content. Tufte sidenotes in the margin. Text flowing around charts like print editorial. Per-line typographic control via pretext.
Agents self-check their output: font readability, label collisions, legend overlap, axis truncation. Reports that fail verification get flagged before publishing.
Docker Compose for self-hosting. Cloudflare Pages for published reports. Fly.io for the API. Or run the whole stack locally — it's one repo.
RichView is source-available under Elastic License 2.0 — free to use, modify, and self-host. The entire platform — editor, renderer, CLI, MCP server, verification pipeline — lives in a single TypeScript monorepo. No microservices, no polyglot complexity, no vendor lock-in. Install it, disconnect from the internet, and it still works. The hosted service at richview.uk is just a convenient publishing option — not a requirement.