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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Feddi |
| Canonical URL | https://feddi.dev |
| Publication time | Wed, 27 May 2026 06:51:07 +0000 |
| Retrieval time | 2026-05-27T07:07:56.846Z |
| Last seen | 2026-05-27T07:07:56.846Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 7o0BAK3MQ-u0 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
