Integrations

UPG works with your whole stack

Product teams don't start from blank. Your strategy is in Vistaly, your research in Dovetail, your backlog in Linear, your docs in Notion. UPG is the semantic layer above all of it: a typed, connected, portable graph that gives everything else meaning, and gives AI agents the structured context they need to reason over your product.

All (9)Strategy & Discovery (2)Delivery (3)Research & Insights (1)Knowledge & Docs (1)Design (1)Analytics (1)

Strategy & Discovery

The closest thing to UPG in the market: OST-native, near 1:1 entity mapping.

View integration→

Dovetail→Beta

Research & Insights

Your research lives in Dovetail; UPG connects those insights to strategy, hypotheses, and execution.

View integration→

NotionMCP↔Beta

Knowledge & Docs

Notion organizes what you wrote. UPG structures what you know.

View integration→

Linear tracks what you're building. UPG explains why you're building it.

View integration→

Jira tracks your epics and stories. UPG asks why they exist.

View integration→

GitHub Issues→Beta

Issues and pull requests become epics, stories, and execution-layer nodes in your product graph.

View integration→

Productboard→Beta

Strategy & Discovery

Productboard captures features and insights. UPG adds the formal structure that makes them queryable and portable.

View integration→

Open-source analytics with native hypothesis fields: PostHog experiments become hypothesis_claim + experiment node pairs.

View integration→

Figma files and frames become design_spec and screen nodes: your designs connected to the features they express.

View integration→

Don't see your tool?

Request an integration or vote for the ones you need most. Every mapping doc we write is published as open-source context.

Request an integration→

Build your own adapter

The UPG spec is MIT licensed. The adapter interface is one TypeScript type. Build a mapping profile for your tool and submit it as a PR.

Adapter docs→