GraphQL has settled into a predictable shape by 2026: most teams aren’t writing a resolver layer from scratch, they’re buying or self-hosting a platform that handles federation, schema governance, and gateway routing for them. Three names keep coming up in that conversation, and they’re no longer directly interchangeable the way they once looked. Apollo GraphQL has consolidated around GraphOS, a managed control plane paired with its open-source Router. Hasura has moved its flagship product to Hasura DDN, a metadata-driven “data delivery network” that generates APIs over existing sources. And WunderGraph — once a broader backend-as-a-service style API gateway — has narrowed its focus entirely to Cosmo, an Apache 2.0-licensed, eBay-backed open-source GraphQL federation platform. This piece compares what each one actually is today, not what it was marketed as two years ago.
At a Glance
| Platform | Core Model | Free Tier | Entry Paid Tier | Open Source? |
|---|---|---|---|---|
| Apollo GraphOS | Managed schema registry + self-hosted Router | Up to 3 devs, 1-day data retention, Router capped at 60 req/min | Developer: from $5 per million ops/month | Router is source-available; GraphOS platform is closed |
| Hasura DDN | Metadata-driven instant GraphQL/REST over data sources | DDN Free (fallback after trial) | DDN Base (30-day free trial, then usage-based) | Core engine has open-source roots; DDN billing is proprietary |
| WunderGraph Cosmo | Full-lifecycle federation platform (registry, router, analytics) | Developer: 1 federated graph, 10M req/month, self-hosted router | Launch: $499/month, 2 graphs, 250M req/month | Yes — Apache 2.0, Go-based router |
Short Verdict
If your organization already runs Apollo Server/Client and needs an enterprise-grade managed control plane with deep tooling (contracts, schema proposals, operation-level observability), Apollo GraphOS is the safest default — at a price. If you want to expose GraphQL (and REST/JSON:API) over existing Postgres, MySQL, or other data sources without hand-writing resolvers, Hasura DDN remains the fastest path from database to API. If you want a fully open-source federation gateway you can self-host indefinitely with no vendor lock-in, and you’re comfortable running your own schema registry, WunderGraph Cosmo is the strongest free option of the three.
Apollo GraphOS: The Incumbent’s Control Plane
Apollo’s business today is GraphOS — a cloud platform that pairs a schema registry, usage reporting, and change-check tooling with the self-hosted GraphOS Router, a Rust-based gateway that executes federated queries across subgraphs. The Router supports federated subscriptions, the @defer directive, automatic persisted queries, JWT-based authorization, and distributed query-plan caching.
Pricing is tiered by developer seat count and data retention rather than purely by request volume: the Free plan supports up to 3 developers with just 1 day of operation history and a Router capped at 60 requests per minute, which is really a sandbox limit, not a production one. The Developer plan starts at $5 per million operations billed monthly, supports up to 10 developers, and includes a $50 signup credit. Standard and Enterprise move to custom, sales-negotiated pricing with longer data retention (90 days and 18 months respectively) and formal SLAs.
Hasura DDN: Instant APIs Over Your Data
Hasura’s pitch has always been different from Apollo’s: instead of federating hand-written GraphQL services, it generates a GraphQL (and JSON:API) layer directly from your connected data sources, with role-based authorization baked in. The current product line is Hasura DDN (“Data Delivery Network”), which replaces the older Hasura v2 engine with a metadata-first model built around “Model” and “Command” objects.
DDN ships three plans — Free, Base, and Advanced — with Base and Advanced each offering a 30-day free trial that does not auto-convert to paid. Billing is unusual among the three platforms here: it’s based on the number of models and “active models” (those queried more than 1,000 times a month), the number of availability zones you run in, and data transfer, rather than a flat per-request rate. Hasura’s own pricing page is explicit that costs don’t scale directly with traffic, which is a meaningfully different cost model than Apollo’s per-operation billing.
WunderGraph Cosmo: The Open-Source Federation Bet
This is where the “verify current product status” caveat matters most. WunderGraph originally marketed itself as a broader API/BaaS-style gateway product. That positioning has effectively been replaced: WunderGraph’s site today centers on Cosmo, described as “full lifecycle API management for (federated) GraphQL” — a schema registry, composition checker, analytics/tracing layer, and a Go-based router, all released under the Apache 2.0 license on GitHub. According to TechCrunch’s March 2025 reporting, eBay backed WunderGraph specifically to build Cosmo as an open-source federation gateway, reflecting eBay’s own internal use of federated GraphQL at scale.
Cosmo’s pricing runs Developer (free, self-hosted router, 1 federated graph, up to 10M requests/month, Discord support), Launch ($499/month, 2 graphs, 250M requests/month, email support), Scale (custom, 5 graphs, up to 1B requests/month, SSO/RBAC), and Enterprise (custom, dedicated solutions architect, up to 99.99% uptime SLA). Every tier, including Enterprise, lists a self-hosted router option — the managed/cloud control plane is what you’re really paying for as you move up tiers.
Feature Comparison
| Capability | Apollo GraphOS | Hasura DDN | WunderGraph Cosmo |
|---|---|---|---|
| Federation support | Yes (Apollo Federation spec) | Limited — primarily single-engine over connected sources | Yes (Federation v1 and v2) |
| Auto-generated API from DB | No — you write subgraphs | Yes, this is the core value proposition | No — connects existing GraphQL services |
| Self-hosted router license | Elastic License (source-available) | Varies by component | Apache 2.0 (fully open source) |
| Event/streaming integration | Via subscriptions | Event triggers | Streams (Kafka, NATS, Redis) |
| Billing basis | Per-operation + seats | Models + AZs + data transfer | Graphs + requests/month |
Pros and Cons
- Apollo GraphOS pros: mature tooling, the de facto federation standard, strong enterprise support tier.
- Apollo GraphOS cons: free tier’s 60 req/min Router cap is production-unfriendly; per-seat pricing penalizes larger teams.
- Hasura DDN pros: fastest time-to-API over existing databases; traffic-independent pricing can be cheaper at high volume.
- Hasura DDN cons: billing model (models/AZs) is harder to forecast than flat request pricing; less suited to hand-rolled federation across many bespoke services.
- WunderGraph Cosmo pros: genuinely open source end to end; generous free tier (10M requests/month); no lock-in.
- WunderGraph Cosmo cons: smaller ecosystem and community than Apollo; you manage more infrastructure yourself even on paid tiers.
Who Each Platform Fits Best
Apollo GraphOS fits teams already invested in the Apollo ecosystem (Apollo Client, Apollo Server) that need enterprise governance features like schema proposals and contracts. Hasura DDN fits teams that want to expose a GraphQL API over Postgres or other databases quickly, without maintaining resolver code. WunderGraph Cosmo fits platform engineering teams building a federated graph from many existing services who want full control and no recurring vendor fee for the core router.
Bottom Line
These three products solve related but distinct problems. Apollo sells governance and federation tooling around a router you still have to design subgraphs for. Hasura sells speed — turning a database into a GraphQL API with minimal code. WunderGraph’s Cosmo sells openness — a federation gateway you can run entirely on your own terms, backed now by real production use at eBay scale. Picking between them should start with which problem you actually have, not which name is most familiar.
FAQ
Is WunderGraph still a separate BaaS product?
No. WunderGraph’s current public-facing product is Cosmo, an open-source GraphQL federation platform; the company’s site no longer centers on a general-purpose BaaS gateway offering.
Can I self-host Apollo’s router for free in production?
The Router binary itself is source-available and free to run, but GraphOS’s Free plan throttles the managed control plane to 60 requests per minute, so production use typically requires at least the Developer tier.
Does Hasura DDN replace Hasura v2?
DDN is Hasura’s current flagship product line with a different metadata model (Models/Commands) and a different, traffic-independent billing approach than the older v2 engine.
Is Cosmo compatible with Apollo Federation?
Yes — Cosmo states support for both Federation v1 and v2, so existing Apollo-style subgraphs can generally be composed through Cosmo’s router.
