THE OPENDASH PRODUCT
One analyst that
shows its work.
Ask your database in plain English. Every answer comes with the SQL and rows behind it. Every correction can make the next answer better.

01 · TRACES
Every number
has a receipt.
Open any figure to see the query, definition and source rows behind it. A check written as code verifies the number against its recorded result.
$398.2k, with the working.
SELECT a.region, SUM(s.mrr) AS mrr
FROM subscriptions s
JOIN accounts a ON a.id = s.account_id
WHERE a.status = 'active'
GROUP BY a.region;| Account | Status | MRR |
|---|---|---|
| Halden Robotics | active | $4,200 |
| Pine & Fold | active | $960 |
| Brightwave | active | $4,100 |
Read-only query. Each figure points to its recorded result.
Saved for this conversation. Team knowledge goes through review.
− status IN ('active', 'past_due')+ status = 'active'
37 past-due accounts removed · $14.4k
02 · LEARNS
Correct it once.
Make the fix
team knowledge.
The analyst remembers your correction. A proposed change then passes query checks, evaluation and an admin’s review before the team uses it.
Previous versions stay available. Revert when the definition changes.
03 · BUILDS
A dashboard built around
your next decision.
Describe who it is for and what they need to decide. Review the plan, watch it take shape, then publish a checked result.
Launch readiness
Checkout v2 · building your draft
Sources stay attached to every widget. Publish when you’re ready.
04 · RUNS
Your Monday numbers.
Already in the channel.
Write the question once and choose a time. OpenDash runs it again, checks the results and delivers a brief to Slack or email.
The same reviewed definitions. Fresh source data. A trace behind every figure.
See the Monday SaaS reviewMonday SaaS review
EnabledA question worth asking every week.
Recent runs
Uses the team’s reviewed definitions on every run.
05 · IN SLACK
The next question
belongs in the thread.
Mention @OpenDash where the conversation is happening. It answers with the same definitions, the breakdown and a link to the working.
Your team can follow up without starting the analysis over.
How OpenDash works in SlackFits the way you work
Works with your stack. Any model you trust.
Connect your sources, choose your model, and get answers where your team works.
Your data
Jira, HubSpot and more through MCP
Your model · your keys
Read-only. Every number traced.
Where answers go
Answers with evidence
Briefs and findings
Jira, HubSpot and more through MCP
Single sign-on OIDCSAML 2.0
A FEW DETAILS
Questions,
answered plainly.
- How does it connect to my database?
- Through a read-only user on PostgreSQL, MySQL, ClickHouse, Snowflake, Databricks, BigQuery or Redshift. It never writes to your database.
- How is it different from a chat model?
- OpenDash runs queries on your database. Every figure points to a recorded result, with its query and source rows available to inspect.
- How are answers checked?
- Code verifies each figure against the recorded query result. Corrections are checked, tested and reviewed before the team uses them, and can be reverted.
- What does setup involve?
- Connect a read-only database user and choose a model. Bring your own provider key or book a demo to walk through setup with your data team.
- What recurring work can it own?
- Routines run on a schedule and post to Slack or email with the trace attached. A watch can follow a metric. Your source data stays read-only.
Ask a real question.
See what comes back.
Bring a real question. We’ll show you the working.
Book a demo