Portal Community

Two Deployment Modes

Workflow Mode

An execution node is instantiated and executed as a step inside a Flow Studio workflow. The workflow engine controls the node's lifecycle — start, execute, pass data, terminate.

Best for: sequential business processes, approval chains, data transformation pipelines.

Server Group Mode

An execution node runs as a long-lived HTTP service registered in a Server Group. Callers — workflows, agents, and other services — invoke it over HTTP without knowing the implementation details.

Best for: shared infrastructure, AI inference endpoints, high-throughput stateless services.

Conceptual Comparison

AspectWorkflow ModeServer Group Mode
LifecycleCreated per workflow execution, destroyed on completionLong-lived process, shared across many callers
StateStateful — carries workflow context and variablesStateless by convention; shared state via external store
InvocationWorkflow engine calls ExecuteAsync(nodeContext)HTTP calls to REST endpoints
ScalabilityScales with workflow parallelismIndependently scalable (Kubernetes HPA)
DiscoveryFlow Studio node palette, drag-and-dropServer Group registry, URL-based
ReusePer-workflow — one instance per runShared — many workflows call the same server

What This Guide Covers

PageTopic
Workflow ModeNode executor lifecycle, BaseNodeExecutor pattern, when to use workflow nodes
Server Group ModeServer Group registration, HTTP invocation, load balancing, health probes
Server Node as a ServiceWhy server nodes are powerful shared services; patterns for high-throughput scenarios
AI Inference Server NodeServing AI models as server nodes — GPU allocation, batching, token streaming
Decision Framework10-question guide to choosing workflow vs server group mode
Satellite NodesEdge-deployed execution nodes that report back to the central server group
Octopus as a Server NodeDeploying the Octopus agent runtime itself as a server node inside a Server Group