JVM-native GraphQL federation gateway
The feddi Gateway is the first JVM-native GraphQL federation gateway, designed to operate without external runtimes. It allows for seamless integration of subgraphs while maintaining compliance and reducing latency. Built on the official GraphQL federation specification, it offers a self-hosted solution that keeps data secure within the user's infrastructure.
- ▪Feddi Gateway runs on the JVM, eliminating the need for external runtimes and reducing latency.
- ▪It automatically composes subgraphs and validates compatibility, preventing breaking changes before they reach production.
- ▪The platform is open source, self-hosted, and ensures that GraphQL traffic remains within the user's infrastructure.
Opening excerpt (first ~120 words) tap to expand
GraphQL Federation Platform The first JVM-native GraphQL federation gateway. Federation inside your JVM. No foreign runtime, no governance gap, no proprietary directives. Built on the GraphQL federation spec. Built by Andi Marek, creator of GraphQL Java, the runtime powering Spring GraphQL and Netflix DGS, and team. Sign up free Get started Always open source. Self-hosted. No vendor lock-in. # 1. authenticate ❯feddi auth login --token fddi_... ✓ Authenticated as [email protected] # 2. create your graph ❯feddi graph create $ORG_ID "payments-api" ✓ Created graph: payments-api ❯feddi variant create $GRAPH_ID production ✓ Created variant: production # 3. publish your subgraphs ❯feddi subgraph publish $ID --schema ./orders.graphqls ✓ Schema published. Composition successful.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Feddi.
Discussion
0 commentsMore from Feddi
%2Ffile%2Fdailymaverick%2Fwp-content%2Fuploads%2F2025%2F11%2FProfile-pic-1.jpg&w=320)
