Prefect Server
Self-hosted workflow server and Python framework for resilient task and data pipelines.
8 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Prefect GitRepository credential-log fix is prerelease-only
Prefect 3.9.4.dev6 stops GitRepository URL credentials from appearing in DEBUG logs and repr output and adds same-origin UI redirect validation.
Scope: Prefect GitRepository logging and UI v2 redirects; no stable remediated release was available when reviewed.
Credential-bearing repository URLs, DEBUG logging and the UI v2 login redirect path determine exposure.
Action: Avoid credentials in repository URLs, restrict logs, rotate exposed tokens and validate the eventual stable fixed release before production use.
Primary source · Credential-log fix · Same-origin redirect validation · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.
Runs in
Documented customer environment
Customer-operated API/UI, background services, database and execution workers
- Northflank: Customer platform workspace
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
- Northflank
Servers / containers
Operated by
Your team
Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
Deployment boundaries by provider
- Northflank: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Self-hosted Prefect server and worker on Northflank ↗ · Source checked 2026-11-12
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Prefect deployment through Northflank BYOC ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Prefect deployment through Northflank BYOC ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Prefect deployment through Northflank BYOC ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances. |
|---|---|
| Infrastructure | Servers / containers Customer-operated API/UI, background services, database and execution workers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 4 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The self-hosted security guide documents shared Basic authentication, proxy configuration and client headers, not a specific SAML/OIDC user federation integration. Prefect Cloud API keys and Cloud SSO are separate. An identity-aware proxy design would need verified UI/API coverage, individual account mapping and client/worker authorization.
Prefect Server security settings; external user federation remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
Prefect 3.9.4.dev6 prevents GitRepository credentials embedded in URLs from appearing in DEBUG logs or repr output and validates same-origin UI v2 post-login redirects. No stable fixed release was available at review time; avoid credential-bearing URLs, protect logs and rotate exposed tokens.
Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed · Source ↗ · 3.9.4.dev6 prerelease ↗ · Same-origin redirect hardening ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The self-hosted scaling guide supplies Compose with multiple API/background services, PostgreSQL, Redis and migrations. This scaled architecture is distinct from a single local SQLite instance and requires coordinated versions and persistence.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The scaling guide specifies multiple API/background-service instances, PostgreSQL and persistent Redis coordination, but no numeric whole-stack CPU/RAM/storage minimum. Workflow workers and execution infrastructure are separate. Size run/event rate, queues, database history/retention and failover before estimating the requested HA workload.
Current multi-server topology; numeric production/worker sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Prefect 3.9.3 upstream Server; not a Prefect Cloud subscription; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was 3.9.3, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The prerelease 3.9.4.dev6 contains credential-log and same-origin redirect hardening; it is not a stable upgrade target.
Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ · Source ↗ · Prerelease-only security fixes ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Configure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.
Community & maintenance
The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases.
Category fit
- Workflow orchestration
- Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.
Compare within Workflow orchestration
- Apache AirflowWorkflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.
- AWS
- DigitalOcean
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- Dagster OSSData orchestration platform for developing, scheduling and observing data-asset workflows.
- AWS
- HashiCorp Nomad EnterpriseCommercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.
- AWS
- Azure
- Google Cloud
- Kestra Self-HostedSelf-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Temporal Self-HostedOrchestrate durable application workflows with a customer-operated Temporal Service.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow orchestration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗raw.githubusercontent.com
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- Self-hosted startup and workflow functionality ↗raw.githubusercontent.com
- Prefect deployment through Northflank BYOC ↗northflank.com
- Prefect 3.9.4.dev6 prerelease ↗github.com
- GitRepository credential-log fix ↗github.com
- UI v2 redirect hardening ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Self-hosted Prefect server and worker on Northflank ↗ · Northflank
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Northflank documents the Prefect server/API/UI, PostgreSQL and worker in a customer project, with flow runs launched as separate jobs. This covers the self-hosted control plane, not a worker connected to Prefect Cloud. The hosted platform manages underlying infrastructure; customer project ownership does not imply ownership of its underlying hyperscaler account.
- Prefect deployment through Northflank BYOC ↗ · AWS, Azure, Google Cloud
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The provider guide installs the self-hosted Prefect server/API/UI, PostgreSQL and worker and explicitly offers AWS, Google Cloud or Azure through Northflank Bring Your Own Cloud. These hyperscaler badges require the BYOC deployment option and its commercial/access prerequisites; a default Northflank hosted project does not run in the customer hyperscaler account. This is a Northflank deployment recipe, not a claim of Prefect vendor-managed BYOC.
- Self-hosted Prefect server and worker on Northflank ↗ · Northflank
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked