
# Workflow orchestration on Northflank

Compare documented Workflow orchestration deployments on Northflank, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/northflank/workflow-orchestration/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Northflank team and project; hosted platform or a separately connected customer cluster
- Provider group: application-platform
- Provider classification: The published Northflank recipes use its hosted platform. Northflank also offers connected customer clusters; those require separate application-specific evidence. Source: https://northflank.com/docs/v1/application/getting-started/create-a-project (checked 2026-11-20).
- Network: Private project services with explicitly exposed public ports
- Identity and access: Team/project roles, API tokens and secret groups
- Installation guidance: Deploy builds, containers, jobs and database add-ons in a project. The hosted platform is separate from Northflank BYOC: confirm the underlying account, cluster ownership and operating agreement for that option.
- Guidance source: https://northflank.com/docs/v1/application/getting-started/create-a-project
- Guidance reviewed: 2026-11-12


### Private and VPC ingress

Project-internal ports, public ingress and VPC ingress are distinct paths. Confirm the deployment mode and private-load-balancer availability; hosted-project documentation does not establish a customer-owned VPC deployment.
Source: https://northflank.com/docs/v1/application/network/networking-on-northflank (reviewed 2026-11-14).

The listings below have evidence for Northflank. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Prefect Server

Self-hosted workflow server and Python framework for resilient task and data pipelines.

- Listing: https://launchinyourcloud.com/directory/prefect/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: northflank, aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.
- Licensing model: open-source
- Installation: Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.
- Architecture: Customer-operated API/UI, background services, database and execution workers
- Operations: Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
- Product website: https://www.prefect.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

- workflow-orchestration: Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.

### Deployment boundaries


- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted Prefect server and worker on Northflank (northflank): https://northflank.com/guides/how-to-deploy-prefect
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Prefect deployment through Northflank BYOC (aws, azure, gcp): https://northflank.com/guides/how-to-deploy-prefect
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases.

Reviewed 2026-11-10.

- Release history and named contributor participation: https://github.com/PrefectHQ/prefect/releases

- Public project and self-hosted server usage: https://github.com/PrefectHQ/prefect

### Sources

- Official installation and runtime: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx

- Upstream project and capabilities: https://github.com/PrefectHQ/prefect

- Current upstream license: https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

- Self-hosted startup and workflow functionality: https://raw.githubusercontent.com/PrefectHQ/prefect/main/README.md

- Prefect deployment through Northflank BYOC: https://northflank.com/guides/how-to-deploy-prefect

- Prefect 3.9.4.dev6 prerelease: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6

- GitRepository credential-log fix: https://github.com/PrefectHQ/prefect/pull/23969

- UI v2 redirect hardening: https://github.com/PrefectHQ/prefect/pull/23980

### Licensing sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx


### Buyer diligence


Research coverage: 6/12 fields (50%); 4 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. 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. Scope: Prefect Server security settings; external user federation remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/security-settings (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. 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. Scope: Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed. Source: https://github.com/PrefectHQ/prefect/pull/23969 (reviewed 2026-11-19). Supporting source: 3.9.4.dev6 prerelease — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6. Supporting source: Same-origin redirect hardening — https://github.com/PrefectHQ/prefect/pull/23980.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Current multi-server topology; numeric production/worker sizing remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/self-hosted (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Prefect 3.9.3 upstream Server; not a Prefect Cloud subscription; software terms only, excluding infrastructure and operations. Source: https://github.com/PrefectHQ/prefect/blob/3.9.3/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.3 (reviewed 2026-11-19). Supporting source: Prerelease-only security fixes — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Prefect GitRepository credential-log fix is prerelease-only (security-advisory): 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. Conditions: 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. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6; reviewed 2026-11-19. Supporting source: Credential-log fix — https://github.com/PrefectHQ/prefect/pull/23969. Supporting source: Same-origin redirect validation — https://github.com/PrefectHQ/prefect/pull/23980.



