Prefect
  • Blog
  • Customers
Get a Demo
Sign InSign Up

Product

  • Prefect Cloud
  • Prefect Open Source
  • Prefect Cloud vs OSS
  • Pricing
  • How Prefect Works
  • Prefect vs Airflow
  • Prefect vs Dagster
  • FastMCP
  • Prefect Horizon
    NEW

Resources

  • Docs
  • Case Studies
  • Blog
  • Resources
  • Community
  • Learn
  • Support
  • Cloud Status

Company

  • About
  • Contact
  • Careers
  • Legal
  • Security
  • Brand Assets
  • Open Source Pledge

Social

  • Twitter
  • GitHub
  • LinkedIn
  • YouTube

© Copyright 2026 Prefect Technologies, Inc. All rights reserved.

LearnVisual GuidesPush Work Pool Deployment

Push Work Pool Deployment

Architecture Diagram

How push work pools enable serverless workflow execution without persistent workers.

prefectwork-poolsserverlessdeploymentarchitecture
Push Work Pool Deployment

About This Diagram

Push work pools flip the script on traditional orchestration. Instead of running a worker that polls for jobs, you give Prefect Cloud credentials to your serverless platform and it submits work directly. No worker process to babysit. No compute sitting idle waiting for work.

When a flow run is ready, Prefect Cloud creates a container job on AWS ECS, Azure Container Instances, Google Cloud Run, Modal, or Coiled. Your code runs, reports back, and the container disappears. You pay only for actual execution time.

This model works best when you want maximum simplicity. Store your cloud credentials in a Prefect Block, point your deployment at a push work pool, and you're done. The tradeoff: flow runs are capped at 24 hours. For longer-running work, use a hybrid work pool with persistent workers instead.

For more on this setup, see the serverless deployment guide.

Download SVG