One place for the work behind your data.
MyDataWork is the workspace around the analytical work you already do. Keep using Excel, SQL, BI, notebooks, workflows and your data platforms; MyDataWork connects that work to its use cases, stakeholders, dependencies, outcomes and value — across the tools your team already uses. Metadata only.
Organize the work
Bring dashboards, spreadsheets, SQL, notebooks, workflows, and cloud assets into one searchable view — so the team sees what exists without opening sensitive data.
Explain the purpose
Link assets to use cases, owners, stakeholders, objectives, and the notes that lived only in people's heads.
Prove the value
Track estimated and realized value across teams, projects, and initiatives — and report what drives outcomes.
Prepare for AI
Expose trusted context over MCP and scope agentic use cases in Agent Studio before you build.
Dashboard
See health, value, ownership, and the latest Workspace Agent findings.
Assets
Catalog the files, queries, workflows, dashboards, and cloud objects that drive decisions.
Connectors
Index on-prem files and cloud data sources by metadata — via the Windows Connector and cloud connections.
Use Cases
Capture objectives, stakeholders, progress, notes, and value.
Lineage
Trace dependencies with evidence and confidence levels.
Portfolio
Export leadership-ready summaries as PDF or PowerPoint.
Architecture & Value
A leadership rollup of your estate — value, utilization, dependencies, and change impact. Team & Enterprise.
AI Analysis
Propose use cases, assess the estate, and prioritize next actions.
Agent Studio
Scope agentic use cases before implementation.
Workspace Agent
Find stale, risky, or under-connected work.
Solution Packs
Start from ready-made use cases for common scenarios instead of a blank workspace — free on every plan.
Action Plans
Turn AI recommendations into tracked next steps — and push them to Jira.
The Asset Health Dashboard
A 10-second read on your analytics estate: what's stale, what it's worth, who owns it, which tools are involved, and what the Workspace Agent recommended last.
Trace dependencies without opening the data.
MyDataWork builds lineage from metadata and labels each connection by confidence — confirmed, likely, or possible — with the evidence behind the link. External systems you depend on appear as ghost nodes, so hidden infrastructure becomes visible.
Because MyDataWork reads metadata and work context, never your data values or file contents, adopting it does not mean handing over your data. The security review that stalls so many tools becomes a much shorter conversation.
A column called order_date, and the fact that it is a DATE. Never the dates inside it. Not one row.
Names, types, structure, relationships, when it changed, and what people wrote about it.
Values, rows, query results, file contents, and anything a person typed into a cell.
Every one of them describes itself in its own dialect, and none of them agree. A catalog that simply stores what each tool hands it ends up with a separate pile per source and nothing that can be compared across them. Making them comparable is the work, and it is the part nobody explains. Here is the same column, as six of our sources describe it.
| Databricks | name: "order_date" | type_text: "date" |
| Power BI | name: "Order Date" | dataType: "dateTime" |
| ThoughtSpot | name: "Order Date" | data_type: "DATE" |
| Sigma | label: "Order Date" | type: { "kind": "date" } |
| Looker | name: "orders.created_date" | type: "date" |
| A spreadsheet | { "Orders": ["order_date", "region"] } | |
Six sources, six shapes, one result. The name may come through as
name, label, columnName or fieldName. The
type as type, dataType, data_type, or buried in a nested
object. Each one maps to the same two fields, attached to a named asset. That is the whole
trick, and everything downstream depends on it.
Six of the sixteen we support: Snowflake, BigQuery, Redshift, Databricks, Power BI, Tableau, Looker, Sigma, ThoughtSpot, dbt, Dataiku, Excel, CSV, Parquet, Avro and ORC. Every one speaks a different dialect. We normalize all sixteen into a single shape, which is what the rest of the product is built on.
Every source, however it phrases itself, becomes the same thing: a named column with a type, attached to a named asset.
MyDataWork holds this for every connected source: where each piece came from, how fresh it is, and, honestly, what a given source cannot publish. A CSV declares column names but no types, because the format has none. That is a fact about CSVs, not a gap in your catalog, and the page says so.
Turn recurring work into documented value.
Use cases connect the work to the business reason it exists — and make its value explicit and reportable.
- Objectives, stakeholders, notes, and progress
- Linked assets and dependencies
- Estimated vs. realized value
- Communication events — who was informed, and when
- Push next steps to Jira as an action plan
See your whole estate in one leadership picture.
A deterministic, credit-free rollup that turns the work your team already tracks into a portfolio a leader can act on — built from metadata only, shown as aggregates, never cost data. It’s the view for the team lead (your workspace admin); analysts don’t touch it — their work shows up because they already organize it in MyDataWork.
- Tool portfolio — every platform placed by value delivered against how heavily it’s used (Invest / Migrate / Tolerate / Eliminate), relative to your own estate
- Capability map — value rolled up by business function
- Dependencies — where value concentrates and which platforms are load-bearing
- Change impact — the value and use cases that depend on any one tool, split by confidence
MyDataWork uses the context you build — assets, use cases, lineage, value, and notes — to answer questions, propose use cases, plan modernizations, discover external data, and scope agentic workflows before anything is built. Metadata only.
AI Assistant
An always-available assistant on every screen — ask questions, get recommendations, and act on your workspace.
Workspace Agent
Surfaces stale work, hidden infrastructure, and work losing momentum — with next best actions.
Migration Assist
Plan and de-risk moving legacy workflows and spreadsheets — with lineage and business value attached to every step.
External data
Find free public datasets — FRED, Census, BLS, NOAA, EIA, SEC EDGAR, World Bank — that could improve the work you already track, plus marketplace listings from your cloud providers. A free readiness check runs first, then a connection recipe you run in your own environment. Accepted sources are catalogued in lineage like any other dependency.
Agent Studio
Define the trigger, inputs, agent role, actions, outcomes, guardrails, and handoff — then export a shareable spec.
Agent Access
Give agents metadata-only context over MCP — never data values or file contents.
Solution Packs load ready-made use cases for common scenarios — a structured plan you adapt to your work. Free on every plan.
Explore Solution Packs →Rationalize a reporting estate
Modernize legacy workflows & spreadsheets
Run planning & forecasting as a governed portfolio
Prove the analytics team's ROI
Cloud warehouses
Snowflake, BigQuery, Redshift, Databricks.
BI & dashboards
Power BI, Tableau, Looker, Sigma, ThoughtSpot.
Transformation & pipelines
dbt, Alteryx, Dataiku.
Notebooks & code
Python, SQL, GitHub.
Spreadsheets & files
Excel, CSV, and the workbooks where real work happens.
Cloud drives
Shared folders and exports across the org.
For the analyst
A persistent home for the work around your analysis: what it is for, what belongs to it, who depends on it, what changed and what it delivered.
For the team
Share assets and use cases when ready, with admin controls and seat-based access.
For leadership
Portfolio visibility across value, risk, ownership, and AI opportunity.
Asset Health Dashboard
A 10-second read on the estate.
Agent Studio
Scope an agentic use case — no code.
Solution Packs
Start from a plan, not a blank workspace.
Estate Assessment
An AI read on what to fix first.
Data catalogs describe your data. MyDataWork organizes the work around it — the Modern catalogs govern the data estate. MyDataWork gives practitioners a workspace around the analytical work that consumes it. Use them side by side: governed data context from the catalog, active work context from MyDataWork.
Try it with your own metadata.
Explorer is the whole product, free for 90 days. Start with demo data, then connect your own files, tools, and cloud assets when you're ready — metadata only. No credit card.
Stay informed
