--- title: Serverless Workers: from background jobs to complex agents description: Temporal Serverless Workers let your code run on AWS Lambda or Google Cloud Run while Temporal Cloud tracks job state and starts workers on demand. A single... canonical: https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Serverless Workers: from background jobs to complex agents | daily.dev og:description: Temporal Serverless Workers let your code run on AWS Lambda or Google Cloud Run while Temporal Cloud tracks job state and starts workers on demand. A single... og:url: https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim og:image: https://api.daily.dev/og/posts/P1XdtuSim.png og:image:alt: Serverless Workers: from background jobs to complex agents og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Serverless Workers: from background jobs to complex agents **[Temporal](https://daily.dev/sources/temporal)** · 6 min read · 0 upvotes · 0 comments ## Summary Temporal Serverless Workers let your code run on AWS Lambda or Google Cloud Run while Temporal Cloud tracks job state and starts workers on demand. A single Lambda invocation can process multiple jobs, and Cloud Run worker pools scale to zero when idle. You can start with a Standalone Activity as a durable background job, then grow it into a full multi-step Workflow for things like document processing or AI agents without rewriting the function. Temporal also supports Amazon Bedrock AgentCore Runtime for agentic apps. Lambda and Cloud Run support are in Public Preview; AgentCore Runtime support is in Pre-release as of October 2026. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does Temporal run workers on AWS Lambda without keeping a fleet running all the time? Temporal Cloud queues the work and invokes a Lambda worker only when capacity is needed. A single Lambda invocation can process multiple jobs, and the worker exits once available work finishes. This lets a background job queue, such as webhook delivery, scale up during bursts and return to zero between them instead of running an always-on worker fleet. _Developers wiring serverless compute into durable job queues can track Temporal's Lambda integration details on daily.dev._ ### What is the difference between a Temporal Standalone Activity and a Workflow? A Standalone Activity submits a single function, like a webhook delivery, directly to Temporal as a durable background job without needing a larger Workflow defined around it. A Workflow coordinates multiple dependent Activities, preserving progress between steps and retrying individual Activities, such as a document-processing pipeline that extracts text, calls a model, and produces a report. _Anyone deciding between a simple job queue and full workflow orchestration can compare these patterns on daily.dev._ ### Which cloud compute options support Temporal Serverless Workers and what stage are they in? Temporal Serverless Workers support AWS Lambda for event-driven jobs, Google Cloud Run Worker Pools for containerized workloads with longer execution times, and Amazon Bedrock AgentCore Runtime for agentic applications on AWS. As of October 2026, Lambda and Cloud Run support are in Public Preview, while AgentCore Runtime support is in Pre-release. _Teams evaluating serverless backends for AI agents can follow these preview rollouts on daily.dev._ ## Similar posts on daily.dev - [Introducing Temporal Serverless Workers: Deploy Temporal Workers to AWS Lambda](https://daily.dev/posts/introducing-temporal-serverless-workers-deploy-temporal-workers-to-aws-lambda-lhywlkbgj) · Temporal · 0 upvotes · 0 comments - [Temporal Serverless Workers on Cloud Run worker pools](https://daily.dev/posts/temporal-serverless-workers-on-cloud-run-worker-pools-yuktusfm3) · Google Cloud · 0 upvotes · 0 comments - [Temporal reveals serverless option for its Durable Execution platform](https://daily.dev/posts/temporal-reveals-serverless-option-for-its-durable-execution-platform-o3rnnfwsf) · The New Stack · 2 upvotes · 0 comments --- Tags: [#gcp](https://daily.dev/tags/gcp), [#serverless](https://daily.dev/tags/serverless), [#aws-lambda](https://daily.dev/tags/aws-lambda) [View this post on daily.dev](https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Serverless Workers: from background jobs to complex agents","url":"https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim"},"datePublished":"2026-10-28T13:06:58.047Z","dateModified":"2026-10-29T13:04:10.811Z","description":"Temporal Serverless Workers let your code run on AWS Lambda or Google Cloud Run while Temporal Cloud tracks job state and starts workers on demand. A single...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/86c11a05efbfc4f370c28a134f6518d4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/86c11a05efbfc4f370c28a134f6518d4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Temporal","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Temporal","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/65290ca7e3ab46a7b1df76f2757800c2","url":"https://daily.dev/sources/temporal"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"gcp,serverless,aws-lambda","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Temporal","item":"https://daily.dev/sources/temporal"},{"@type":"ListItem","position":3,"name":"Serverless Workers: from background jobs to complex agents"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/serverless-workers-from-background-jobs-to-complex-agents-p1xdtusim#faq","mainEntity":[{"@type":"Question","name":"How does Temporal run workers on AWS Lambda without keeping a fleet running all the time?","acceptedAnswer":{"@type":"Answer","text":"Temporal Cloud queues the work and invokes a Lambda worker only when capacity is needed. A single Lambda invocation can process multiple jobs, and the worker exits once available work finishes. This lets a background job queue, such as webhook delivery, scale up during bursts and return to zero between them instead of running an always-on worker fleet. Developers wiring serverless compute into durable job queues can track Temporal's Lambda integration details on daily.dev."}},{"@type":"Question","name":"What is the difference between a Temporal Standalone Activity and a Workflow?","acceptedAnswer":{"@type":"Answer","text":"A Standalone Activity submits a single function, like a webhook delivery, directly to Temporal as a durable background job without needing a larger Workflow defined around it. A Workflow coordinates multiple dependent Activities, preserving progress between steps and retrying individual Activities, such as a document-processing pipeline that extracts text, calls a model, and produces a report. Anyone deciding between a simple job queue and full workflow orchestration can compare these patterns on daily.dev."}},{"@type":"Question","name":"Which cloud compute options support Temporal Serverless Workers and what stage are they in?","acceptedAnswer":{"@type":"Answer","text":"Temporal Serverless Workers support AWS Lambda for event-driven jobs, Google Cloud Run Worker Pools for containerized workloads with longer execution times, and Amazon Bedrock AgentCore Runtime for agentic applications on AWS. As of October 2026, Lambda and Cloud Run support are in Public Preview, while AgentCore Runtime support is in Pre-release. Teams evaluating serverless backends for AI agents can follow these preview rollouts on daily.dev."}}]} ```