Core concepts
The few ideas the rest of the docs build on, from workspaces and sources to the answer gate and the learning loop.
The big picture
You connect a source to a workspace. The analyst answers questions from it, guided by your knowledge and semantic layer. Every answer passes the answer gate before you see it. When the analyst gets something wrong, your correction enters the learning loop, and once approved, the fix applies to everyone. Questions you come back to become dashboards, built by the analyst for a job, and routines, which run on their own.
Glossary
| Term | Meaning |
|---|---|
| Workspace | An organization in OpenDash: its members, sources, knowledge and everything built from them. Data never crosses between workspaces. |
| Project | A group inside a workspace for sharing conversations and dashboards with some people rather than everyone. |
| Source | A database OpenDash reads through a read-only user: PostgreSQL, MySQL or ClickHouse. |
| Catalog | What OpenDash learned about a source: its tables, columns and profiles. |
| Analyst | The agent that answers questions. It searches your knowledge, runs queries through the gateway, and writes the answer. |
| Run | One turn of the analyst, with every model call, tool call and query recorded. Its trace shows all of it. |
| Query gateway | The only way queries reach a source: read-only sessions, time and row limits, per-dialect safety checks, personal-data columns never returned. |
| Answer gate | Deterministic code that resolves and recomputes every number in an answer. An answer it can't check is marked Unverified, never hidden. |
| Dataset | A YAML definition of a table or query: its grain, columns, measures, segments and relationships. |
| Metric | A named, governed number over a dataset's measure, such as MRR. |
| Governed path | The order the analyst tries: a verified query, then a metric, then SQL over datasets, then raw SQL (labelled Unmodelled). |
| Glossary term | What a word means at your company, optionally mapped to a column and values. |
| Guide | Markdown advice for the analyst, pinned to every question or found by search. |
| Verified query | A metric query an admin saved from a good answer, used as a template for similar questions. |
| Skill | A named, step-by-step procedure the analyst follows when it fits. |
| Memory | Short notes the analyst keeps for one person only, such as a preference. |
| Proposal | A suggested change to shared knowledge, from a correction. It is checked and tested, then approved or rejected. |
| Dashboard | A live page the analyst builds for one job, from named queries it runs as the viewer. A draft until its owner publishes it. |
| Connected service | A service such as Jira or HubSpot, connected over MCP, that the analyst and dashboards can read. |
| Routine | Something that happens on its own: on a schedule, or when a check finds something. |
| Insight | Something a routine found: an anomaly, a crossed line, a goal at risk, missing data. It can be investigated and turned into a task. |
Two promises
Read-only. OpenDash never writes to your databases. Each query runs in a read-only session with a server-side time limit, as the user you connected, and the connection check warns you if that user could change data.
Every number is traceable. If a figure appears in an answer, it came from a query result you can open. That's what makes it safe to forward an answer to someone who wasn't in the conversation.