PlatformRealtime

Realtime limits

Plan client connections and message volume before you stream updates to users.

Realtime has two plan limits: how many subscribers can be connected at once, and how many messages you can publish each day. Estimate both before you add Realtime to a high-volume job.

Plan limits

PlanConcurrent connectionsMessages per day
Free50250,000
Pro1,0001,000,000
Business5,0005,000,000
EnterpriseCustomCustom

See pricing for the current plan comparison. Connection limits apply to Realtime subscribers only. Worker connections and step concurrency have separate limits.

Keep message volume predictable

Every publish counts as one message. If you stream model output token by token, a single long answer can publish thousands of messages. Multiply by your expected runs per day and compare the total with your plan.

To reduce volume, publish meaningful state changes rather than every small tick, or batch several tokens into one message before you publish.

React hook memory and rendering

These useRealtime settings run in the browser. They don't change your plan limits or add server-side replay.

  • historyLimit keeps the latest 100 messages in messages.all by default. Raise it, or set null to keep every message, when the UI rebuilds text from a stream.
  • bufferInterval is 0 ms by default, so every message triggers a render. Set a larger interval to batch renders for fast streams.
  • pauseOnHidden and autoCloseOnTerminal default to true. The hook pauses in hidden tabs and closes when the run finishes, which frees the connection.

Next steps