Meet WunderGraph Hub: GraphQL Federation's Missing Layer | WunderGraph Webinar - WunderGraph

Chapters

• 0:00 Why did we build Hub?
• 1:18 GraphQL Federation's Coordination Problem
• 2:12 Why Changes Are Slow
• 3:22 Broken Workflows
• 4:08 The Consequences of Doing Nothing
• 6:19 Subgraph-First Issues
• 6:56 From the API Consumer's Perspective
• 7:43 Going Supergraph-First
• 8:10 What Hub Does
• 9:21 LLMs & APIs
• 10:55 Demo: Setup
• 11:45 Demo: Explore Schema
• 12:56 Demo: New Use Case
• 14:15 Demo: From Screenshot to Query
• 15:41 Demo: Add Fields
• 16:38 Demo: Enable Governance
• 17:58 Demo: Assign Fields
• 18:24 Demo: Collaboration
• 19:04 Demo: Proposals
• 20:35 Demo: Why Not Just Use GitHub?
• 23:23 Demo: Code vs Schema First
• 25:59 Demo: From Canvas to Mock
• 27:07 Demo: New Subgraph
• 28:32 Demo: Git Integration
• 29:31 Summary
• 31:19 Q&A: Open Source & Roadmap
• 34:19 Q&A: UI Mockups & What's Next

About This Webinar

Why do schema changes take days, weeks, or even months in federated GraphQL?

In this video resource, Jens Neuse, Dustin Deus, and Nithin Kumar B break down why the real bottleneck today isn’t coding: it’s coordination across teams.

While federation solves composition and runtime, it leaves major gaps in design, governance, and ownership. The recording shows how WunderGraph Hub allows teams to design APIs visually, collaborate in real time, and avoid scattered communication across tools.

You’ll see how platform teams use Hub to design schema changes at the supergraph level before implementation, align ownership, and catch issues early: including a live demo of going from UI screenshot to query, detecting gaps, assigning subgraphs, and validating changes in real time.

Key Topics Covered

• Why schema changes slow down: coordination overhead, ownership ambiguity, and fragmented workflows
• The limitations of traditional federation workflows (subgraph-first design and late composition)
• A new approach: designing APIs from what the consumer needs
• The “dream query” workflow: define what you need first, then generate the schema
• How to automatically derive composable subgraphs from supergraph changes
• Demo walkthrough: explore a graph, create a new use case, detect missing fields, assign ownership, and validate changes
• How Hub enables real-time collaboration, discussions, and governance directly on the schema
• Q&A highlights: code-first vs schema-first, integrations, and roadmap

Who Should Watch

This webinar is ideal for:

• Platform and infrastructure engineers working with distributed systems
• API and GraphQL architects managing federated graphs
• Frontend engineers and product teams defining API requirements
• Engineering leaders dealing with cross-team coordination challenges
• Organizations scaling GraphQL across multiple teams and services

Frequently Asked Questions (FAQ)

What will I learn from this video?

In this session, you'll see why schema changes in federated GraphQL often take weeks—not because of coding, but because of coordination—and how WunderGraph Hub introduces a new, supergraph-first workflow. The recording walks through defining requirements as queries, detecting missing fields, assigning ownership, and generating subgraphs automatically using a new approach called 'Fission'.

What is WunderGraph Hub?

WunderGraph Hub is a collaborative API design and governance platform for federated GraphQL. It enables teams to design APIs from the consumer perspective, visualize relationships between subgraphs, coordinate schema changes, and keep a persistent history of decisions: all on one collaborative canvas.

What problem does Hub solve?

Hub addresses the coordination bottleneck in federated GraphQL. While tools like routers and schema registries solve runtime and composition, teams still struggle with ownership, cross-team communication, and lost context. Hub provides a shared workspace to design, discuss, and manage schema evolution without relying on fragmented tools like Slack, Jira, or GitHub comments.

Is this only for teams already using GraphQL Federation?

WunderGraph features such as Cosmo Connect (https://wundergraph.com/connect) allow users to federate any datasource, so the benefits of Hub go beyond strictly-GraphQL setups. For simplicity, this session focuses on federated GraphQL challenges, especially in large organizations with many teams and subgraphs.