Explore Prefect concepts
Develop
| Keyword |
Description |
| Flows |
A Prefect workflow, modeled as a Python function. |
| Tasks |
Discrete units of work in a Prefect workflow. |
| Results |
The data returned by a flow or a task. |
| Artifacts |
Formatted outputs rendered in the Prefect UI, such as markdown, tables, or links. |
| States |
The status of a particular task run or flow run. |
| Task Runners |
Enable you to engage specific executors for Prefect tasks, such as concurrent, parallel, or distributed execution of tasks. |
| Runtime Context |
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. |
| Blocks |
Prefect primitives that enable the storage of configuration and provide a UI interface. |
| Variables |
Named, mutable string values, much like environment variables. |
Deploy
| Keyword |
Description |
| Deployments |
A server-side concept that encapsulates a flow, allowing it to be scheduled and triggered via API. |
| Projects |
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. |
| Storage |
Lets you configure how flow code for deployments is persisted and retrieved by Prefect agents. |
| Filesystems |
Blocks that allow you to read and write data from paths. |
| Infrastructure |
Blocks that specify infrastructure for flow runs created by the deployment. |
| Schedules |
Tell the Prefect API how to create new flow runs for you automatically on a specified cadence. |
| Logging |
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.