Explore Prefect concepts
|A Prefect workflow, modeled as a Python function.
|Discrete units of work in a Prefect workflow.
|The data returned by a flow or a task.
|Formatted outputs rendered in the Prefect UI, such as markdown, tables, or links.
|The status of a particular task run or flow run.
|Enable you to engage specific executors for Prefect tasks, such as concurrent, parallel, or distributed execution of tasks.
|Information about the current flow or task run that you can refer to in your code.
|Profiles & Configuration
|Settings you can use to interact with Prefect Cloud and a Prefect server.
|Prefect primitives that enable the storage of configuration and provide a UI interface.
|Named, mutable string values, much like environment variables.
|A server-side concept that encapsulates a flow, allowing it to be scheduled and triggered via API.
|A minimally opinionated set of files that describe how to prepare one or more flow deployments.
|Work Pools, Workers & Agents
|Bridge the Prefect orchestration environment with your execution environment.
|Lets you configure how flow code for deployments is persisted and retrieved by Prefect agents.
|Blocks that allow you to read and write data from paths.
|Blocks that specify infrastructure for flow runs created by the deployment.
|Tell the Prefect API how to create new flow runs for you automatically on a specified cadence.
|Log a variety of useful information about your flow and task runs on the server.
Features specific to Prefect Cloud are in their own subheading.