Two deployment models, zero GraphQL servers required. Wrap REST, SOAP, or any gRPC service into the supergraph.
Router Plugins and gRPC Services. No GraphQL subgraph frameworks required.
Apollo Federation requires every backend to run a GraphQL server. Cosmo Connect removes that requirement. Define a standard subgraph schema, compile it to Protocol Buffer definitions, and implement the service in any gRPC language. The Router handles GraphQL query planning, batching, and response aggregation.
Two deployment models serve different needs. Router Plugins run as local processes alongside the Router for minimal latency and unified deployment. gRPC Services are independent microservices that can scale and deploy anywhere.
Adding backends to a federated graph should not require rewriting them or teaching every team GraphQL. Most organizations have more backends than GraphQL expertise.
Four barriers that slow federation adoption.
Every team contributing data needs GraphQL expertise. For Java, Python, or Go teams with no GraphQL background, that is a real adoption cost.
Some ecosystems have poor or unmaintained GraphQL server libraries. Teams in those ecosystems have no good path into federation.
REST, SOAP, and internal services need to be rebuilt from scratch to become Apollo Federation subgraphs. That is months of work per service.
Each new capability means a new service to deploy, monitor, and maintain with its own CI/CD pipeline and infrastructure.
Cosmo Connect removes all four barriers. Backend teams implement gRPC contracts. The Router handles GraphQL.
GraphQL Federation without GraphQL servers. Define a subgraph schema, compile to Protocol Buffers, implement in any gRPC language. The Router translates GraphQL operations to gRPC calls, batches with DataLoader, and assembles responses.
Free / Pro / Enterprise
Real integration patterns and the Cosmo Connect capability behind each one.
A financial services company has critical REST APIs that cannot be rewritten but need to appear in the federated graph.
Define a GraphQL subgraph schema representing the REST API. Generate protobuf definitions with the CLI. Implement a thin gRPC adapter that calls the REST endpoints. Connect it to the federated graph.
Legacy APIs join the supergraph without rewriting any business logic.
An e-commerce platform has services in Java, Python, and Go. Each team wants to keep its language.
Each team defines their subgraph schema, generates protobuf definitions, and implements the gRPC service in their language. The Router coordinates across all services.
Teams maintain technology autonomy while contributing to a unified API.
A team needs to expose multiple internal APIs through GraphQL quickly.
Define subgraph schemas. Provide OpenAPI specs or example requests to an AI coding assistant. Let it generate adapter code against the strongly-typed proto definitions.
Multiple integrations completed in hours with type-safe guarantees.
| If you are… | Start here |
|---|---|
| Learning what Cosmo Connect is | Cosmo Connect |
| Integrating a REST or SOAP API without a separate service | Router Plugins |
| Building a new microservice with language flexibility | gRPC Services |
| Needing independent scaling and team autonomy | gRPC Services |
| Wanting the lowest latency with unified deployment | Router Plugins |
| Cosmo Connect | Apollo Federation (GraphQL subgraphs) | Apollo Connectors | |
|---|---|---|---|
| Backend knowledge required | gRPC only | GraphQL + Federation | REST/HTTP mapping |
| Language support | Any gRPC language | Limited by library quality | N/A (declarative) |
| N+1 handling | DataLoader built-in | Framework-dependent | N+1 prone |
| Existing API integration | Wrap without rewriting | Rewrite required | Declarative mapping |
| Setup time | Hours | Days/weeks | Hours |
Product
Resources
Related Projects
Certified & Compliant
SOC 2 Type II
HIPAA
ISO 27001© 2026 WunderGraph, Inc. All rights reserved.
