
# Software on Northflank

Explore software with documented Northflank deployment, customer-account guidance, licensing qualifications and source evidence.

Canonical page: https://launchinyourcloud.com/clouds/northflank/
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.

4 listings.


## Joomla!

Customer-operated content management and website publishing platform.

- Listing: https://launchinyourcloud.com/directory/joomla/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci, digitalocean, linode, vultr, northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Joomla web application, database, web server and persistent site assets.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.joomla.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Joomla web application, database, web server and persistent site assets. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Customer-operated content management and website publishing platform.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/joomla-with-mds/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/openlitespeed-joomla (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application (checked 2026-11-19). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-joomla-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Architecture (oci): https://docs.oracle.com/en/solutions/joomla-with-mds/
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/openlitespeed-joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Vultr Docs (vultr): https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Northflank Guide (northflank): https://northflank.com/guides/deploy-joomla-on-northflank
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes brianteeman, wilsonge, infograf768, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/joomla/joomla-cms/graphs/contributors

- Upstream project: https://github.com/joomla/joomla-cms

### Sources

- OCI Architecture: https://docs.oracle.com/en/solutions/joomla-with-mds/

- DO Marketplace: https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- Vultr Docs: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- Northflank Guide: https://northflank.com/guides/deploy-joomla-on-northflank

- GPL-2.0 LICENSE.txt: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

- Releases v6.2.1-rc1: https://github.com/joomla/joomla-cms/releases

### Licensing sources

- https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

### Infrastructure sources

- https://docs.oracle.com/en/solutions/joomla-with-mds/

- https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- https://northflank.com/guides/deploy-joomla-on-northflank


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Edition-dependent. miniOrange publishes a SAML service-provider extension and explicitly states Joomla 3/4/5/6 compatibility. This is a third-party extension with its own plan and support terms, not an included Joomla-core feature; validate the exact site version, provider and purchased plugin capabilities. Scope: Extension vendor documentation for Joomla 6-compatible SAML; not upstream Joomla support. Source: https://plugins.miniorange.com/joomla-single-sign-on-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Akamai documents deploying its Joomla Quick Deploy application through Cloud Manager, API, CLI or Terraform using StackScript 985372. This is a provider-maintained package/recipe; verify the installed Joomla version and upgrade path separately from the upstream release. Scope: Akamai/Linode Joomla application deployment recipe; not a Joomla upstream HA template. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (reviewed 2026-11-20). Deployment artifact: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla. Artifact reference: Current provider StackScript 985372 examples; package/application versions can differ.

- Minimum footprint / sizing: Sources checked — unresolved. The current Joomla 6.x technical requirements recommend a PHP memory limit of at least 256 MB and specify supported PHP, database and web-server versions. That limit is per PHP process, not a VM/RAM or HA capacity floor; whole-deployment sizing remains unconfirmed. Scope: Joomla 6.x software requirements; no complete host footprint established. Source: https://manual.joomla.org/docs/next/get-started/technical-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Joomla!; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 6.2.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Joomla! upstream application; verify compatibility with the selected package. Source: https://github.com/joomla/joomla-cms/releases/tag/6.2.0 (reviewed 2026-11-19).







## KeystoneJS (Keystone 6)

Self-hosted content backend with a configurable GraphQL API and administration interface.

- Listing: https://launchinyourcloud.com/directory/keystonejs/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Keystone 6 application and PostgreSQL using the Northflank template.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://keystonejs.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Keystone is a developer framework that requires a project schema and application configuration; it is not a ready-made editorial website.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Keystone 6 application and PostgreSQL using the Northflank template. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content backend with a configurable GraphQL API and administration interface.

- backend-platforms: Self-hosted content backend with a configurable GraphQL API and administration interface.

### Deployment boundaries


- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-keystonejs-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- Northflank Guide (northflank): https://northflank.com/guides/deploy-keystonejs-on-northflank
  Keystone 6 application and PostgreSQL using the Northflank template. Keystone is a developer framework that requires a project schema and application configuration; it is not a ready-made editorial website.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes timleslie, emmatown, jesstelford, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/keystonejs/keystone/graphs/contributors

- Upstream project: https://github.com/keystonejs/keystone

### Sources

- Northflank Guide: https://northflank.com/guides/deploy-keystonejs-on-northflank

- MIT LICENSE: https://github.com/keystonejs/keystone/blob/main/LICENSE

- Releases 2026-11: https://github.com/keystonejs/keystone/releases

### Licensing sources

- https://github.com/keystonejs/keystone/blob/main/LICENSE

### Infrastructure sources

- https://northflank.com/guides/deploy-keystonejs-on-northflank


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 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 reviewed guide provides session APIs and an opinionated auth package for custom Keystone applications. This alone does not establish a supported turnkey SAML/OIDC integration or its entitlement; confirm the application-specific identity implementation. Scope: Keystone 6 framework authentication APIs; not a packaged SSO feature. Source: https://keystonejs.com/docs/guides/auth-and-access-control (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream CLI guide documents building the application with keystone build, applying Prisma migrations and running keystone start. These commands deploy a custom Keystone project; they are not a prebuilt turnkey CMS image or cloud infrastructure template. Scope: Keystone 6 application build/start and Prisma migration workflow. Source: https://keystonejs.com/docs/guides/cli (reviewed 2026-11-20). Deployment artifact: https://keystonejs.com/docs/guides/cli. Artifact reference: Current CLI instructions; pin the project and database dependencies.

- Minimum footprint / sizing: Sources checked — unresolved. The CLI and first-project guides establish an application build, Node runtime and database-backed project, but no quantitative production CPU/RAM/storage baseline was established. Size the actual schema, database, uploads and concurrency rather than treating the tutorial as HA capacity. Scope: Custom Keystone 6 application; deployment-specific production sizing. Source: https://keystonejs.com/docs/guides/cli (reviewed 2026-11-20). Supporting source: Official first-project walkthrough — https://keystonejs.com/docs/walkthroughs/lesson-1.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: KeystoneJS (Keystone 6); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/keystonejs/keystone/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The 2026-11-03 monorepo release includes @keystone-6/core 8.3.0. Package versions differ within the Keystone 6 family; the date tag is a release bundle rather than one application semantic version. Scope: Keystone 6 monorepo package release bundle; selected project dependencies must be pinned separately. Source: https://github.com/keystonejs/keystone/releases/tag/2026-11-03 (reviewed 2026-11-19).







## 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.




## Umami

Self-hosted website and event analytics application with dashboards and PostgreSQL storage.

- Listing: https://launchinyourcloud.com/directory/umami/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, fly, heroku, northflank, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream Umami.
- Licensing model: open-source
- Installation: Build from source, run the official prebuilt container or use its Docker Compose application/PostgreSQL setup.
- Architecture: Customer-operated web analytics service and PostgreSQL database
- Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
- Product website: https://umami.is/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.

MIT License for upstream Umami. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web analytics service and PostgreSQL database. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website and event analytics through a deployed tracking endpoint and analytics application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-digitalocean (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-fly-io (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-heroku (checked 2026-11-12). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-northflank (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-railway (checked 2026-11-12). 


### Cloud deployment evidence

- Umami self-hosting on a DigitalOcean Droplet (digitalocean): https://docs.umami.is/docs/guides/running-on-digitalocean
  The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Fly.io (fly): https://docs.umami.is/docs/guides/running-on-fly-io
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Heroku (heroku): https://docs.umami.is/docs/guides/running-on-heroku
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Northflank (northflank): https://docs.umami.is/docs/guides/running-on-northflank
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Railway (railway): https://docs.umami.is/docs/guides/running-on-railway
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Upstream release notes document current runtime/security work and credit multiple named contributors across successive releases.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/umami-software/umami/releases

- Public upstream project: https://github.com/umami-software/umami

### Sources

- Official installation and runtime: https://docs.umami.is/docs/install

- Upstream project and capabilities: https://github.com/umami-software/umami

- Current upstream license: https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

- Umami self-hosted deployment on Fly.io: https://docs.umami.is/docs/guides/running-on-fly-io

- Umami self-hosted deployment on Heroku: https://docs.umami.is/docs/guides/running-on-heroku

- Umami self-hosted deployment on Northflank: https://docs.umami.is/docs/guides/running-on-northflank

- Umami self-hosted deployment on Railway: https://docs.umami.is/docs/guides/running-on-railway

### Licensing sources

- https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

### Infrastructure sources

- https://docs.umami.is/docs/install


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 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 API documents an SSO token endpoint requiring existing authentication and Redis. This does not establish a generic SAML/OIDC enterprise identity-provider integration or its edition entitlement. Scope: Authenticated token exchange checked; enterprise federation remains unresolved. Source: https://docs.umami.is/docs/api-reference/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide documents source builds, application containers and Compose. It explicitly identifies the HelmForge Kubernetes chart as third-party; change the default administrator password and configure the database and secrets. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.umami.is/docs/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide requires the application runtime and a PostgreSQL database, but does not give a numeric whole-stack production CPU/RAM/storage minimum. Event volume, retention, query concurrency and HA determine capacity; provider demo allocations are not a 100-user, 1 TB HA sizing guarantee. Scope: Current upstream self-hosted topology; whole-system sizing remains unconfirmed. Source: https://docs.umami.is/docs/install (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v3.5.0 application is MIT-licensed and can be self-hosted without a core software subscription. Retain the required copyright/licence notices; hosting, database, operations and Umami Cloud services are separate costs. Scope: Published self-hosted application terms; not a Cloud plan quote. Source: https://github.com/umami-software/umami/blob/v3.5.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v3.5.0, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream umami-software/umami release record; commercial editions and deployment packages may differ. Source: https://github.com/umami-software/umami/releases/tag/v3.5.0 (reviewed 2026-11-14).






