Every chart, from rows you can already see.
Pick a type from the catalogue, choose the sources and projects it reads, and the server draws it from your own tasks, meetings, expenses and deals under your own permissions. Switching type, regrouping or re-filtering costs nothing and asks no model anything.
- One catalogue, every type
- A projection drawn dashed
- Re-run for every viewer
The dashed columns are a projection from these rows, drawn as their own series.
- Send to chat
- Attach to a task
- Save to Files
- Insert into Grids
- Pin to the project Overview
- Download PNG
The model writes the spec. The server runs it.
A chart is a declarative spec - source, filters, grouping, aggregate, type - and the server executes it deterministically. That is what makes browsing, switching and reconfiguring free.
- Column
- Line
- Pie
- Pareto
- Gantt
- Fishbone (Ishikawa)
And 33 more, every one drawn from sample rows before a single query runs.
39 chart types, one catalogue
Comparison, trend, composition, distribution, relationship, project and table types, including Pareto, fishbone, burndown, Gantt and calendar heat maps. The picker, the search and Hoot read the same catalogue, so nothing here can advertise a chart the picker does not offer.
The two lines meet at July. Clamped at zero. The caption saying so travels with the chart.
A projection that says it is one
Ask for a forecast and the chart draws it as its own dashed series from arithmetic over the rows it just read, clamped at zero, never invented by a model and never drawn in the same ink as a measurement.
47 tasks drawn
16 tasks drawn
Same pin, same spec. A project Jo cannot open is a bar Jo never gets.
Every chart re-runs for whoever opens it
A chart pinned to a project Overview or sent to chat is executed again under the viewer's own visibility, so a manager's pin never shows a member rows they could not query.
Run under your own permissions
The set of projects you can see is resolved once and every query runs inside it. Field keys are validated against the catalogue before they reach the database.
Several sources on one axis, honestly
One chart can count tasks, meetings and expenses side by side, one query per source. Count is the only aggregate that crosses a source boundary, because a sum of money and a sum of minutes share an axis only by accident.
Where a chart goes
Send it to chat, attach it to a task or a meeting, save it to the project's Files, insert its rows into a Grid, pin it to the project Overview, or download PNG, SVG, PDF or CSV.
A chart is a question about the workspace.
What is included, and where the line is.
Every new workspace starts on a free trial of the full Business tier, no card needed, and lands on Free when it ends. Prices and limits are on the pricing page.
The catalogue, previews and editing
Browsing every type and reconfiguring a chart costs nothing on any plan.
Hoot drawing a chart from a sentence
A model turning words into a spec.
Pinning to the Overview, attaching, saving to Files or a Grid
The persisted destinations. Downloads are never gated.
Dashboards of several panels in one image
The heaviest thing the engine does per press.
The ones people ask first.
Does every chart cost a credit?
Can one chart cover several projects?
What is the dashed line?
Draw the answer.
Open any project, press the chart button, and browse the whole catalogue before a single query runs.
Free to start · No credit card required