Ironflow SDK Architecture

Ironflow SDK Architecture An architecture diagram generated by Archify. Your application code · functions, workers, UI · Architecture component Your application code functions, workers, UI @ironflow/browser · client, subscriptions, KV, config · SDK packages @ironflow/browser client, subscriptions, KV, config @ironflow/node · serve, createWorker, createFunction · SDK packages @ironflow/node serve, createWorker, createFunction @ironflow/core · types, schemas, errors, upcasters · SDK packages · shared @ironflow/core types, schemas, errors, upcasters shared Go SDK · client, worker, functions · SDK packages · no JS dependency Go SDK client, worker, functions no JS dependency Ironflow server · ConnectRPC + REST mux, :9123 · Architecture component Ironflow server ConnectRPC + REST mux, :9123 imports shared types + schemas WebSocket or ConnectRPC, connects inward push: HTTP POST to your endpoint pull: long-poll for jobs HTTP or gRPC SDK packages Legend Frontend Backend External

Who opens the connection

  • • Browser: connects inward over WebSocket or ConnectRPC for live subscriptions
  • • Push: the server connects outward and POSTs your endpoint, under 10s per call
  • • Pull: the worker polls GET /api/v1/workers/{id}/jobs inward, no timeout

Package layering

  • • @ironflow/core holds types, Zod schemas, errors, protocol and upcasters
  • • Both JS packages depend on it; the Go SDK does not
  • • Opt-in streaming worker at @ironflow/node/worker-streaming

Not shown here

  • • sdk/python is experimental and client-only — no worker runtime
  • • @ironflow/langgraph is an integration, not an SDK layer