Prefect

Orchestration

46.7
Overall Score
428 quotes

Dimension Scores

Setup & Ease of Use 57
216 quotes
Documentation Quality 25
212 quotes

Overview

Prefect serves as a solution in the orchestration space. The platform has built a user base for its approach to handling data workflows. Users have provided feedback on various aspects of the platform's functionality and operational characteristics.

Key aspects that emerge from user feedback include both strengths in specific operational domains and challenges that teams face when deploying or scaling the solution. The platform's positioning within the orchestration category means it competes on specific dimensions that matter to that market segment.

Like any data integration tool, Prefect has both capabilities and constraints that vary depending on deployment context and specific use case requirements.

Strengths

  • Referenced strength from user feedback
  • Additional capability noted by users
  • Feature or approach valued by practitioners

Limitations

  • Operational consideration mentioned in feedback
  • Scaling or deployment challenge noted
  • Area for improvement identified by users

Pricing Model

Pricing model varies by deployment option. Check the vendor's website for current rates.

User Evidence

Positive hn
"After multiple years fighting with Celery, we moved to Prefect last year and have been mostly happy with it."
View original →
Positive hn
"Also for totally non-data stuff, Prefect is great."
View original →
Negative hn
"requires you to use the (somewhat immature) prefect task APIs to implement that concurrency"
View original →
Positive hn
"On Dagster and Prefect you communicate between tasks as if you were writing pure Python."
View original →
Negative hn
"Prefect is like an hour just to put up the kubernetes environment required for it."
View original →
Positive hn
"We are using prefect+dbt and I like it."
View original →

Last updated: Jun 17, 2026