WunderGraph

Capabilities

• Cosmo composes REST and GraphQL services, and databases, into one unified API, so teams expose a single gateway endpoint instead of many service endpoints.[1][2]

• The router is written in Go, runs the federated graph, and deploys self-hosted through the all-in-one Docker Compose quickstart or the documented Helm charts.[1]

• Subgraphs can be written in any language, with schema checks and contracts guarding the federated graph against breaking changes.[1]

• Authentication and authorization run at the gateway: the platform supports any compliant OIDC provider and enforces RBAC from JWT claims.[1]

• Field-level instrumentation integrates with OpenTelemetry tooling, and real-time GraphQL subscriptions run over NATS.[1]

Good fit

• Platform teams that run many REST and GraphQL services and want one governed entrypoint fit best, since composition, schema checks, and gateway auth are the core workflow.[1][2]

• Regulated companies that must keep the API layer on their own infrastructure fit well: the stack is fully open source, self-hosting is free, and the vendor reports approval by leading regulated companies.[1][2]

Limitations

• A self-hosted control plane cannot invite members or share a project with others; teams that need that collaboration must use Cosmo Cloud.[1]

• The model centers on GraphQL federation, so teams that want a pure REST-transformation gateway without GraphQL semantics should weigh that scope before adopting.[1][2]

• Evaluation is quick through Docker Compose, but production federation across subgraphs with checks and Kubernetes operations takes real platform effort.[1][2]

Compatibility