Interactive playground tracing, schema exploration, lint enforcement, usage-based pruning, and CLI automation — all built into Cosmo.
Playground, schema explorer, lint, pruning, and CLI. One platform.
Cosmo ships a complete set of developer tools alongside its federation engine. The same platform that composes your graph also provides the playground, schema explorer, lint enforcer, usage analyzer, and CLI you need to build and maintain it.
Every tool connects to the same graph and the same analytics data. There is no context-switching between a separate IDE, a lint tool, and a deployment script. You work in one place.
Generic IDEs and linters have no federation awareness. They see a single schema, not a composed graph with subgraphs, operation checks, and real traffic data.
Four problems that surface repeatedly without federation-native tooling.
Standard GraphQL IDEs return the final result. No subgraph-level timing, no routing information, no visibility into parallel execution.
Without automated enforcement, naming conventions, documentation requirements, and deprecation standards vary by team and erode over time.
Teams cannot safely remove fields without usage data. Fear of breaking consumers leads to schema bloat and growing technical debt.
Without a CI-integrated CLI, schema changes go out without checks. Breaking changes reach staging before they are caught.
Cosmo Developer Experience tools address all of this natively — no third-party IDEs, no custom lint scripts, no separate deployment tooling.
Enhanced GraphiQL with Advanced Request Tracing (ART). Add the X-WG-TRACE header and get tree and waterfall visualizations of query execution, including per-subgraph timing and inputs/outputs.
Free / Pro / Enterprise
Include the X-WG-Include-Query-Plan header to receive the full query plan in the response extensions. Use X-WG-Skip-Loader to inspect plans without making subgraph requests.
Free / Pro / Enterprise
Run JavaScript before and after operations. Pre-flight scripts handle authentication globally across tabs. Pre-operation and post-operation scripts run per-tab for setup, validation, and transformation. Supports CryptoJS and external fetch.
Free / Pro / Enterprise
Generate a URL that encodes a complete playground session — operation, variables, and headers. Recipients open the link and see the exact session, ready to run.
Free / Pro / Enterprise
| If you are… | Start here |
|---|---|
| Debugging a slow or unexpected federated query | GraphiQL Playground++ |
| Understanding how the router routes a query across subgraphs | Query Plan Visualization |
| Sharing a query session with a teammate for review or debugging | Shared Playground State |
| Browsing types, fields, and authentication requirements | Schema Explorer |
| Enforcing naming conventions and documentation on every check | Lint Policies |
| Finding unused or deprecated fields safe to remove | Graph Pruning |
| Approving an intentional breaking change without disabling checks | Breaking Change Overrides |
| Automating schema checks and deployments in CI/CD | Cosmo CLI (wgc) |
| Cosmo | Generic GraphQL IDEs | Custom tooling | |
|---|---|---|---|
| Query execution tracing | ART with tree and waterfall | Response only | Manual instrumentation |
| Schema lint enforcement | Built-in, runs on every check | Plugin-based, inconsistent | Custom scripts required |
| Usage-based field pruning | Built-in (Pro / Enterprise) | Not available | Analytics integration required |
| CLI schema check and publish | Built-in via wgc | Separate tooling | Custom scripts |
| Shareable playground sessions | Built-in | Rarely available | Not available |
Real debugging, governance, and automation patterns, and the Cosmo tool behind each one.
A product query takes 2 seconds. Multiple subgraphs contribute fields, but generic monitoring only shows the total request time.
Open the Cosmo Playground, add the X-WG-TRACE header, and run the query. The waterfall visualization shows timing for each subgraph call.
The slow subgraph is immediately visible. The fix is targeted — no need to instrument each service separately.
Multiple teams contribute subgraphs. Without enforcement, field names drift between camelCase and snake_case, types lose descriptions, and deprecated fields accumulate without context.
Enable Lint Policies with FIELD_NAMES_SHOULD_BE_CAMEL_CASE, ALL_TYPES_REQUIRE_DESCRIPTION, and REQUIRE_DEPRECATION_REASON as errors. Every wgc subgraph check enforces these rules automatically.
Schema conventions are enforced consistently. Code review stops catching style violations — the check does.
Schema changes require manual review in the Studio UI. Engineers forget to run checks, and breaking changes reach staging.
Add wgc subgraph check to the CI pipeline on pull requests. On merge, wgc subgraph publish deploys the schema. Set COSMO_API_KEY as a CI secret.
Every schema change is validated before merge. Deployments run automatically. Breaking changes surface in code review, not in staging.
wgc subgraph check runs on every pull request. Breaking changes surface before merge, not after deployment.Product
Resources
Related Projects
Certified & Compliant
SOC 2 Type II
HIPAA
ISO 27001© 2026 WunderGraph, Inc. All rights reserved.