# Open-Source GraphQL Ecosystem for .NET

> Explore the open-source .NET GraphQL ecosystem behind Hot Chocolate, Fusion, Mocha and Strawberry Shake: public code, standards work, docs, and community.

Canonical source: https://chillicream.com/platform/ecosystem

[GitHub stars: 5,733](https://github.com/ChilliCream/graphql-platform/stargazers)

[MIT LICENSED](https://github.com/ChilliCream/graphql-platform/blob/main/LICENSE)

[](https://github.com/ChilliCream/graphql-platform)

[](https://slack.chillicream.com/)

[](https://chillicream.com/blog)

[![](https://avatars.githubusercontent.com/u/9714350?v=4)](https://github.com/michaelstaib)

[![](https://avatars.githubusercontent.com/u/261509?v=4)](https://github.com/glen-84)

[![](https://avatars.githubusercontent.com/u/14233220?v=4)](https://github.com/PascalSenn)

[![](https://avatars.githubusercontent.com/u/45513122?v=4)](https://github.com/tobias-tengler)

[![](https://avatars.githubusercontent.com/u/4325318?v=4)](https://github.com/rstaib)

[![](https://avatars.githubusercontent.com/u/157336?v=4)](https://github.com/benmccallum)

[![](https://avatars.githubusercontent.com/u/45466413?v=4)](https://github.com/N-Olbert)

[![](https://avatars.githubusercontent.com/u/681965?v=4)](https://github.com/wonbyte)

[![](https://avatars.githubusercontent.com/u/55194784?v=4)](https://github.com/danielreynolds1)

[![](https://avatars.githubusercontent.com/u/4927894?v=4)](https://github.com/sunghwan2789)

[![](https://avatars.githubusercontent.com/u/13761704?v=4)](https://github.com/glucaci)

[![](https://avatars.githubusercontent.com/u/8672758?v=4)](https://github.com/arif-hanif)

[![](https://avatars.githubusercontent.com/u/521449?v=4)](https://github.com/jorrit)

[![](https://avatars.githubusercontent.com/u/2009544?v=4)](https://github.com/matt-psaltis)

[![](https://avatars.githubusercontent.com/u/6015550?v=4)](https://github.com/PHILLIPS71)

[![](https://avatars.githubusercontent.com/u/9481836?v=4)](https://github.com/fredericbirke)

Explore the code, read the docs, and talk to the maintainers building the platform.

[Explore the code](https://github.com/ChilliCream/graphql-platform) [Read the docs](https://chillicream.com/docs)

Open source you can inspect. Standards you can follow. People you can reach.

## Built in the open, in one repository.

The server, gateway, client, and core libraries are all developed in a single public GitHub repository.

[ChilliCream/graphql-platformONE REPOSITORYThe core server, gateway, client, and libraries share one codebase, so the pieces stay in step.MIT LICENSEOpen source under the MIT license. Free to use in commercial products.PUBLIC DEVELOPMENTFollow issues, pull requests, releases, and changelogs as the work lands.](https://github.com/ChilliCream/graphql-platform)

## Helping write the standards we implement.

ChilliCream contributors help shape the specifications and conventions the platform implements. See the [official GraphQL team page](https://graphql.org/community/team/) for current roles and participation.

[TWO SEATSTechnical Steering CommitteeThe committee steering the GraphQL specification. Michael Staib and Pascal Senn both hold seats.github.com](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md) [HOSTComposite Schemas Working GroupMichael Staib hosts the Composite Schemas subcommittee, which develops an open standard for composing GraphQL services.github.com](https://github.com/graphql/composite-schemas-wg) [HOSTGraphQL/OpenTelemetry Working GroupPascal Senn hosts GraphQL/OTel, which develops OpenTelemetry conventions for GraphQL APIs.github.com](https://github.com/graphql/otel-wg) [ORGANIZERSGraphQL DayCommunity events around the world, organized with the GraphQL Foundation team.graphql.org](https://graphql.org/day) [MEMBERSGraphQL Working GroupThe main working group evolving the GraphQL specification itself.github.com](https://github.com/graphql/graphql-wg) [MEMBERSGraphQL over HTTPThe specification for transporting GraphQL over HTTP, so servers and clients interoperate.github.com](https://github.com/graphql/graphql-over-http) [MEMBERSAI Working GroupBest practices for GraphQL in AI systems and agent-powered applications.github.com](https://github.com/graphql/ai-wg)

## Find the people behind the code.

Follow the work on GitHub, bring questions to Slack, and learn from talks and engineering posts.

[GitHubIssues, discussions, pull requests, and the source itself.GitHub stars: 5,733](https://github.com/ChilliCream/graphql-platform) [SlackAsk questions and talk to the team and other users directly.Join ](https://slack.chillicream.com/) [YouTubeTalks, release walkthroughs, and deep dives.Watch ](https://www.youtube.com/c/ChilliCream) [BlogRelease notes, engineering write-ups, and announcements.Read ](https://chillicream.com/blog)

## From our blog

[View all](https://chillicream.com/blog)

- [![](https://chillicream.com/images/blog/2026-08-03-directives-all-the-way-down/header.png)Aug 2026Directives All the Way DownGraphQL directives can now be applied to directive definitions themselves in Hot Chocolate 16.4, so you can finally deprecate a directive and attach metadata to your schema's own extension points.Read](https://chillicream.com/blog/2026-08-03-directives-all-the-way-down)
- [![](https://chillicream.com/images/blog/2026-07-12-fusion-16-5/header.png)ReleaseJul 2026Fusion 16.5: The Gateway for EveryoneBuilt with C# and .NET, Fusion 16.5 is the only gateway supporting both federation standards, achieves 100% Apollo Federation compliance, and leads in real-world performance.Read](https://chillicream.com/blog/2026-07-12-fusion-16-5)
- [![](https://chillicream.com/images/blog/2026-07-06-federated-event-streams/header.png)ReleaseJul 2026Introducing Federated Event Streams for Fusion 16.4Federated Event Streams add broker-backed, resumable GraphQL subscriptions to Fusion 16.4, with stateless gateway scaling and client-owned resume cursors.Read](https://chillicream.com/blog/2026-07-06-federated-event-streams)

## See whether it fits your architecture.

Read the docs, run a focused evaluation, and talk to a maintainer about your architecture. Then decide.

[Read the docs](https://chillicream.com/docs) [Talk to a maintainer](https://slack.chillicream.com/)
