The Sched app allows you to build your schedule but you must also be registered for GraphQLConf 2026 to participate in the sessions.
Please note: This schedule is automatically displayed in Pacific Daylight Time (UTC-7). To see the schedule in your preferred timezone, please select from the drop-down located at the bottom of the menu to the right.
IMPORTANT NOTE: Timing of sessions and room locations are subject to change.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
GraphQL and Federation solve real problems: replacing hand-written orchestration with a declarative, typed contract between clients and backends. That model works. But the landscape is shifting — AI agents are becoming first-class API clients, and they need to compose across services, reshape responses, and build workflows faster than coordinated schema design allows.
The core insight: one graph doesn't have to mean one API. What if the supergraph were less a single schema and more a catalog of data and services? That shift opens up a different kind of client language: one with expressions, data restructuring, and the ability to call non-GraphQL APIs directly.
I'll show the result of our explorations: a language that keeps what makes GraphQL powerful — strong typing, composability, field-level selection — and extends it with the primitives clients need to work across service boundaries. It should feel familiar and is designed for any client — web, mobile, and AI agents alike. I'll explain what we learned from pushing GraphQL and Federation to their limits, and make the case that breaking the mold doesn't mean starting over.
Martijn Walraven lives in Amsterdam and has been with Apollo since the early days of our GraphQL journey. He is one of the co-creators of Apollo Federation.
