Expose your own long-running work as an async API. The caller POSTs, gets a job id back in milliseconds, and the answer is pushed to a realtime channel when it lands, with a status route as the fallback. Nothing holds a request open, so work that outlives a proxy timeout still completes and is still retrievable. SQLite, so it runs with nothing installed.
The Postgres build of Async Job API: the same submit-then-push job API, on a database that handles concurrent writers. result is jsonb so outcomes are queryable, jobs are indexed by owner, and the status response carries elapsed time. Use this one to deploy; the SQLite sibling exists to be run with nothing installed.
The simplest realtime: a PUBLIC WebSocket feed your website visitors subscribe to with NO auth — live scores, status, prices, announcements. Your backend publishes; every open browser gets it instantly. Ably/Pusher public channel, no keys in the browser, no broker to run.
The Ably/Pusher alternative: pub/sub channels, presence, history-rewind and retained state over WebSocket — with open, Air Pipe-issued, or bring-your-own-JWT auth, and your pipeline running on every message. No broker or Redis to run.
Stream a model's answer to the browser token by token. Air Pipe reads the provider's token stream and forwards it to a realtime channel, so a chat UI renders text while the model is still writing. Works with any OpenAI-compatible provider.