Oyren Features

Notes, boards and cloud machines for app development.

A dashboard built from data, open to change

A dashboard brief pairs a question with a real data export. A coding agent builds the view, and its numbers need comparison with the source. The running dashboard opens at a public URL, with the code available for inspection and changes as the questions develop.

See plans and usage pricing
Spreadsheets use-case poster
Illustrative spreadsheets use-case poster from the Oyren video collection.
App preview use-case poster
Illustrative app preview use-case poster from the Oyren video collection.

Questions and source data for a dashboard

A chart has a defined purpose when the brief names the question it should answer. An existing export or spreadsheet can provide the source, for example for revenue by week or products ordered most. An answer calculated by hand supplies a comparison for the finished view. The agent has actual data to build from, while the reviewer has a source-based value to check.

A kanban card records the data source, questions and refresh button. The export can be attached as a workspace file. Its columns and values provide the structure for the build instead of leaving the agent to invent a schema for the dashboard.

Charts, tables and refresh behavior

Assign to agent can send the card to a coding agent, or the task can be described to Claude Code, Codex CLI, opencode, Cursor CLI or Qwen Code, with Antigravity available from the terminal. The brief can specify the charts, table, date filter and refresh behavior. A first page provides a reviewable scope, with additional views or charts recorded as separate tasks.

The codespace runs Linux. Agent sign-ins or API keys are supplied separately, and the charting library needed by the build can be installed. VS Code provides access to inspect a calculation in the files and compare its logic with the source data.

Source comparisons and public-site review

Every codespace has a public URL. The Public site panel points it at the dashboard’s port. The running view can be compared with the manually calculated answer for the same period. A finished-looking dashboard still needs this check; its appearance does not establish that its numbers are correct.

Runtime is billed by the hour while the codespace runs. A snapshot supports pausing the machine and returning when more data or another question is available. The board retains the brief and subsequent changes, keeping the source and review criteria beside the next task.

Questions about a dashboard built from data, open to change

Do I need to know a charting library to get a dashboard?
The brief describes the charts and their questions. A coding agent can choose and install a charting library. The resulting dashboard still needs review against the data.
How do I know the dashboard's numbers are right?
A manually calculated answer from the source data provides a comparison for the dashboard over the same period. Changes to the data or build need that comparison repeated.
Can the dashboard update when I add new data?
A refresh button or export-reload behavior can be part of the agent’s task. Review needs to confirm that a refresh reads newly added data, beyond checking that the button is present.