# Support for @stream in the router

**URL:** <https://community.apollographql.com/t/support-for-stream-in-the-router/9518>\
**Category:** Router\
**Tags:** router\
**Created:** [October 22, 2025, 3:21am UTC](https://community.apollographql.com/t/support-for-stream-in-the-router/9518 "2025-10-22T03:21:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjfaga](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/mjfaga/32/5533_2.png) [@mjfaga](https://community.apollographql.com/u/mjfaga)\
**Post date:** [October 22, 2025, 3:21am UTC](https://community.apollographql.com/t/support-for-stream-in-the-router/9518/1 "2025-10-22T03:21:42Z")

</div>

Hey folks - looking for some guidance on plans for supporting the `@stream` directive in the router. For now, unless I’m missing something, it looks like I’m going to have to leverage subscriptions to accomplish what I need in the short term, but it’s a bit non-ideal and I’m hoping someone has a better alternative if `@stream` is far out.

---

<div class="post-metadata">

**Author:** ![calvincestari](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/calvincestari/32/339_2.png) [@calvincestari](https://community.apollographql.com/u/calvincestari)\
**Post date:** [October 22, 2025, 8:05pm UTC](https://community.apollographql.com/t/support-for-stream-in-the-router/9518/2 "2025-10-22T20:05:38Z")

</div>

Hi Mark - we’re busy getting our OSS (Apollo Server, and the clients) to support the new incremental delivery format, which brings along support for `@stream` too.

Router support is a different story though. I’d like to learn more about your use case though, so If you’re interested in chatting about it [book a slot in this calendar](https://calendar.app.google/zyxHVXE44JmnRueA9) and we’ll go from there.
