Context Studio

Turn scattered definitions

into shared context.

Context Studio gathers the business definitions and rules you already have into one governed store, tracks their sources and surfaces conflicts. Every agent gets the same meaning, delivered alongside your data.

The problem

The agent isn’t the hard part. Context is.

Agents can read your schemas. What they can’t read is what your data means. That meaning lives in glossaries, BI tools, catalogs and pipelines, and each one defines revenue or customer a little differently. The agent picks one. When it picks wrong, the answer looks confident and is still wrong.

AI is confidently wrong

Missing or ambiguous definitions leave agents guessing what your data means.

Same question, different answers

Definitions vary across tools and teams, so agents can’t tell which meaning applies.

Maintaining context is manual

Every new use case means more discovery, curation and validation.

With Context Studio

One governed source of meaning for every agent.

Context Studio sits between where context lives and the agents that use it. Define once, and AIDA, Claude and your own agents all work from the same certified definitions over MCP.

Answers grounded in your business

Agents get the meaning behind your data, so they read metrics, relationships and rules the way your team does.

Consistent across every agent

AIDA and connected agents share one source of definitions, with the context to pick the right one.

Less repeated work

Reuse context from the tools you already have and maintain it in one place.

How it works

Harvest. Reconcile. Certify.

Starburst federates context the way it federates data. You don’t start from a blank page, and you don’t migrate anything first.

Harvest

Don’t rebuild your context. Bring it in from the places it already lives and keep it alongside your data.

  • Warm start with data in StarburstPreview

    Data Products, query history, catalogs

  • You push it inPreview

    Agents read dbt, Atlan, Cube.dev or markdown files

  • We pull it inRoadmap

    Out-of-the-box connectors for catalogs

Reconcile

Merge every source into one governed store, field by field. Different sources will disagree, and Context Studio finds where.

  • One store, field by field

    Terms, metrics, rules, synonyms and join keys from every source land in one place.

  • Conflicts surfaced

    Where two sources disagree, the conflict is flagged instead of silently picked.

  • Every field keeps its source

    Provenance tracks which source contributed each field, and the store stays current as sources change.

Certify

When definitions conflict, a person decides, not the agent. Agents then work from certified context.

  • No conflict, certified

    Values every source agrees on become certified context automatically.

  • People resolve the rest

    Decide the value for each open conflict in the UI or through the API. The cycle repeats as sources change.

  • Steward approval and version historyPlanned

    Named-steward workflows, approval history and tracing answers to exact context versions.

I don’t want another catalog that people forget to update. Context Studio pulls what we already wrote into one place, traces every rule back to its source, and flags when two rules disagree. Our agents start from the same answer someone on my team would give.
Zach EckelsStaff Data Engineer, Nerdy

Define once. Trust everywhere.

Context Studio is in private preview. Bring your business knowledge to every agent, without a rebuild.