SDK Architecture

Ironflow provides three SDKs that communicate with the server through different protocols. The browser SDK connects inward via WebSocket or ConnectRPC for real-time subscriptions. In push mode, the server connects outward to user endpoints via HTTP POST. In pull mode, workers connect inward and poll the server over HTTP for jobs (an opt-in ConnectRPC streaming worker is also available). The @ironflow/core package provides shared types, schemas, and error classes used by both browser and node packages. A fourth SDK, sdk/python, is experimental and client-only — it can emit events and query resources but ships no worker runtime, so it is not shown here. @ironflow/langgraph is also outside the diagram: it is an integration package, not an SDK layer — a LangGraph checkpoint saver backed by entity streams.