# Streaming
Source: https://www.inngest.com/docs/streaming

In select environments, the SDK allows streaming responses back to Inngest, hugely increasing maximum timeouts on many serverless platforms up to 15 minutes.

While we add wider support for streaming to other platforms, we currently support the following:

- [Cloudflare Workers](/docs/learn/serving-inngest-functions#framework-cloudflare-workers)
- [Express](/docs/learn/serving-inngest-functions#framework-express)
- [Next.js on Vercel Fluid Compute or Edge Functions](/docs/learn/serving-inngest-functions#framework-next-js)
- [Remix on Vercel Edge Functions](/docs/learn/serving-inngest-functions#framework-remix)

## Enabling streaming

Select your platform above and follow the relevant "Streaming" section to enable streaming for your application.

Every Inngest serve handler provides a `streaming` option, for example:

<CodeGroup>
```ts
serve({
  client: inngest,
  functions: [...fns],
  streaming: "allow",
});
```
</CodeGroup>

This can be one of the following values:

- `false` - Streaming will never be used. This is the default.
- `"allow"` - Streaming will be used if we can confidently detect support for it by verifying that the platform, environment, and serve handler support streaming.

<Callout>

⚠️ We also allow `"force"`, where streaming will be used if the serve handler supports it, but completely overrides the SDK's attempts to verify if the platform supports streaming.

This is not recommended, but is an escape hatch if you know that streaming is supported and you're in a restricted environment that has little or no access to the environment.

</Callout>