Standalone Activities Announcement @ Replay 2026 | Durable Job Processing with Standalone Activities

Temporal has announced Standalone Activities, a new top-level primitive for durable job processing that eliminates the need for traditional job queue infrastructure. Now in public preview across Python, Go, Java, TypeScript, and .NET, standalone activities let developers execute any Temporal activity directly via a single SDK client call — without an enclosing workflow — while retaining all platform features: automatic retries, deduplication, heartbeating, priority/fairness, full UI visibility, and lifecycle control. Coinbase shared how they are migrating their homegrown Redis-backed background job service (200–600M jobs/day across 186 namespaces) to standalone activities to eliminate a single-coordinator bottleneck, noisy-neighbor retry contention, and operational overhead. Technically, standalone activities use the same durable state machine as workflow-embedded activities, making the feature set identical. Upcoming additions include start delay, schedule-based triggering, Nexus integration, and export support.