
# Software on Hetzner

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

Canonical page: https://launchinyourcloud.com/clouds/hetzner/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde



## Related questions

- [What open-source apps can I deploy on a VPS like DigitalOcean, Hetzner or Vultr?](https://launchinyourcloud.com/questions/apps-on-vps/)
- [What software runs on European cloud providers like STACKIT, Scaleway or Hetzner?](https://launchinyourcloud.com/questions/european-clouds/)


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: Hetzner account and cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.hetzner.com/cloud/servers/getting-started/creating-a-server/ (checked 2026-11-20).
- Network: Cloud networks, public IPs and firewalls
- Identity and access: Project access and server SSH keys
- Installation guidance: Create a server with a supported OS and install the application; manage updates, storage and backups in the customer project.
- Guidance source: https://docs.hetzner.com/cloud/servers/getting-started/creating-a-server/
- Guidance reviewed: 2026-11-12


### Private networking

Hetzner Networks provide private layer-3 links between cloud servers; a vSwitch can connect a Network to dedicated servers. Plan subnet routes and access controls rather than relying on a public VM address.
Source: https://docs.hetzner.com/networking/networks/overview/ (reviewed 2026-11-14).

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

9 listings.


## BigBlueButton

Self-hosted conferencing and virtual classroom platform.

- Listing: https://launchinyourcloud.com/directory/bigbluebutton/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, scaleway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Official bbb-install.sh from the maintained 4.0 installer branch on supported Ubuntu
- Architecture: BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure.
- 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://bigbluebutton.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee. The maintained 4.0 installer also explicitly documents Scaleway and Azure behind-NAT deployments.

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

BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted conferencing and virtual classroom platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- scaleway: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 (aws, azure, gcp, digitalocean, hetzner, scaleway): https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md
  BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes antobinary, ritzalam, ramonlsouza, 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/bigbluebutton/bigbluebutton/graphs/contributors

- Upstream project: https://github.com/bigbluebutton/bigbluebutton

### Sources

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md

- Official Install Docs: https://docs.bigbluebutton.org/administration/install/

- bbb-install README: https://raw.githubusercontent.com/bigbluebutton/bbb-install/master/README.md

- LGPL-3.0 LICENSE: https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE

- Releases v4.0.2: https://github.com/bigbluebutton/bigbluebutton/releases

### Licensing sources

- https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Documented. The optional Greenlight v3 front end supports external authentication through OpenID Connect and can connect to an external identity server. This is a Greenlight user-login capability, not the conferencing engine shared-secret API or an assurance about every LMS/front-end integration. Scope: BigBlueButton with the separately configured Greenlight v3 front end. Source: https://docs.bigbluebutton.org/greenlight/v3/install/ (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 official 4.0 installation instructions link the maintained bbb-install.sh branch for Ubuntu 24.04. The older master README describes 2.6 and must not be used as the 4.0 installer reference. Scope: BigBlueButton 4.0 installer; verify the selected release line, dedicated CPU, public address and media firewall rules. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-19). Deployment artifact: https://github.com/bigbluebutton/bbb-install/blob/v4.0.x-release/bbb-install.sh. Artifact reference: v4.0.x-release (moving maintained 4.0 installer branch).

- Minimum footprint / sizing: Documented. The production guide recommends Ubuntu 24.04, 8 CPU cores, 16 GB RAM, symmetric 250 Mbit/s networking and 500 GB free recording space, or 50 GB without recording. Smaller 4-core/8-GB development settings are separate. Concurrent media usage and HA need additional design. Scope: Current upstream production conferencing-node requirements; not meeting capacity for every workload. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-20).

- License pricing: Documented. GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: BigBlueButton; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Collabora Online (CODE)

Community office editing server for integration with a document platform.

- Listing: https://launchinyourcloud.com/directory/collabora-online/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: Collabora Online Development Edition server and a separate WOPI-compatible file platform.
- 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://collaboraonline.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package.

Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Collabora Online Development Edition server and a separate WOPI-compatible file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community office editing server for integration with a document platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/ (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/collabora-online.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/
  Collabora Online Development Edition server and a separate WOPI-compatible file platform. CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Ashod, eszkadev, timar, 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/CollaboraOnline/online/graphs/contributors

- Upstream project: https://github.com/CollaboraOnline/online

### Sources

- Cloudron Store: https://www.cloudron.io/store/collabora-online.html

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/

- MPL-2.0 COPYING: https://github.com/CollaboraOnline/online/blob/master/COPYING

- Releases 2026: https://github.com/CollaboraOnline/online/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/CollaboraOnline/online/blob/master/COPYING

### Infrastructure sources

- https://www.cloudron.io/store/collabora-online.html

- https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 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: Sources checked — unresolved. The reviewed CODE material describes an embedded editing service and integrations, but does not establish standalone corporate SAML/OIDC user login in the listed development edition. Confirm the identity-providing document host, connector and edition instead of assigning its SSO to the editing engine. Scope: CODE engine identity versus external document-platform authentication. Source: https://www.collaboraonline.com/code/ (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. Collabora publishes the collabora/code container image for the CODE development/small-team edition, which the vendor does not recommend for production. Pin a suitable image and configure a document host/connector. Active source development moved to Gerrit; the retained GitHub build/chart artifacts do not make a nightly or commercial build equivalent to CODE. Scope: Listed CODE development edition; not Collabora Online commercial production support. Source: https://www.collaboraonline.com/code/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/collabora/code. Artifact reference: Select a supported version-tagged CODE image; distinguish nightly and commercial builds. Supporting source: Upstream source/build repository locations — https://raw.githubusercontent.com/CollaboraOnline/online/master/README.md.

- Minimum footprint / sizing: Documented. The Cloudron package declares 1024MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/collabora-online.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Collabora Online (CODE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/CollaboraOnline/online/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Discourse

Self-hosted discussion and community platform for workplace collaboration and customer support communities.

- Listing: https://launchinyourcloud.com/directory/discourse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, linode, vultr, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-2.0 core; review extensions separately
- Licensing model: open-source
- Installation: Official Docker installer on a Linux cloud or local server
- Architecture: Persistent Docker server; the standalone template includes web, PostgreSQL and Redis services with host-mounted data volumes.
- Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
- Product website: https://www.discourse.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.

The listed self-hosted core has a GNU GPL version 2 license. Official paid hosting is a separate service; review the licenses of selected extensions separately.

The official installer requires a Linux server and Docker. Its standalone configuration mounts persistent host storage and includes PostgreSQL and Redis; this is a server workload.


### Category fit

- collaboration: Public or private discussion communities with searchable topics, chat and shared knowledge.

- customer-support: Customer and peer-support communities; this is a discussion platform rather than an agent-ticket helpdesk.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 


### Cloud deployment evidence

- Discourse supported cloud server installation (aws, gcp, digitalocean, linode, vultr, hetzner): https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md
  The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official customer directory identifies Docker, Elastic and GitLab support communities as Discourse users, without establishing their hosting model. The official release service records security-maintenance updates on November 10, 2026 for the latest, monthly and ESR channels; the supported 2026.10.1 release includes 38 security fixes.

Reviewed 2026-11-14.

- Named support-community adopters: https://www.discourse.org/customers

- Current releases and support timelines: https://releases.discourse.org/

- 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Sources

- Official self-hosting installation guide: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- Official standalone Docker service and storage template: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml

- Discussion, chat and administration features: https://www.discourse.org/features

- Discourse core license: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- Official releases and support timelines: https://releases.discourse.org/

- Official customer community directory: https://www.discourse.org/customers

- Discourse 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Licensing sources

- https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

### Infrastructure sources

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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: Documented. DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service. Scope: Official DiscourseConnect self-hosted forum authentication. Source: https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 (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 official discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology. Scope: Official self-hosted launcher and standalone container installation. Source: https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml. Artifact reference: main (moving branch). Supporting source: Standalone configuration template — https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml.

- Minimum footprint / sizing: Documented. The upstream cloud guide lists 1 CPU core, 1 GB RAM with swap and 10 GB disk as minima; 2+ cores, 2 GB+ RAM and 20 GB+ disk are recommended. Plugins, traffic and data growth change sizing. Scope: Upstream standalone cloud install baseline. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (reviewed 2026-11-14).

- License pricing: Documented. The upstream Discourse software is GPL version 2. Hosted subscription prices on discourse.org are for separately operated hosting/services and should not be presented as the license cost of the self-hosted core. Infrastructure, implementation and optional services are separate. Scope: Upstream self-hosted core license; hosted plan pricing is a different offering. Source: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## n8n Self-Hosted

Automate integrations and business processes with a customer-hosted workflow editor and runtime.

- Listing: https://launchinyourcloud.com/directory/n8n/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
- Licensing model: source-available
- Installation: Docker Compose with persistent data; database and worker topology selected for workload
- Architecture: Customer-operated workflow runtime, credentials store and persistent execution data
- Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
- Product website: https://n8n.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.

Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.


### Category fit

- workflow-automation: Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

- ai-tools: Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner (checked 2026-11-12). 


### Cloud deployment evidence

- n8n deployment on AWS (aws): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws
  Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Azure (azure): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure
  Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Google Cloud Run (gcp): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run
  The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on DigitalOcean (digitalocean): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Heroku (heroku): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Hetzner (hetzner): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current self-hosted Docker Compose guide: https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose

- Official license boundaries: https://github.com/n8n-io/n8n/blob/master/LICENSE.md

- Workflow automation project: https://github.com/n8n-io/n8n

- AI workflow components and integrations: https://docs.n8n.io/build/integrate-ai.md

- n8n self-hosted deployment on DigitalOcean: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean

- n8n self-hosted deployment on Heroku: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku

- n8n self-hosted deployment on Hetzner: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner

- n8n@2.48.6 release: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6

- n8n@1.123.99 release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99

- Patched V8 runtime integration: https://github.com/n8n-io/n8n/pull/43703

### Licensing sources

- https://github.com/n8n-io/n8n/blob/master/LICENSE.md

### Infrastructure sources

- https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose


### 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. SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it. Scope: Self-hosted Business and Enterprise; not the unlicensed Community edition. Source: https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md (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 vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA. Scope: Official self-hosted Compose deployment. Source: https://docs.n8n.io/hosting/installation/server-setups/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://github.com/n8n-io/n8n-hosting. Artifact reference: Select and pin a compatible versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows. Scope: Self-hosted workflow-dependent sizing; complete production footprint unresolved. Source: https://docs.n8n.io/hosting/scaling/memory-errors/ (reviewed 2026-11-20). Supporting source: Production topology and dependencies — https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md.

- License pricing: Documented. The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3. Scope: Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build. Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7. Supporting source: Maintained 1.x runtime fix — https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99. Supporting source: Patched V8 runtime integration — https://github.com/n8n-io/n8n/pull/43703.







## NetBird Self-Hosted Community Edition

Open-source zero-trust networking control plane self-hosted on a customer cloud VM.

- Listing: https://launchinyourcloud.com/directory/netbird-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
- Licensing model: open-source
- Installation: Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity provider
- Architecture: Customer-operated management, signal, relay or STUN, dashboard, identity and state services; peers form direct WireGuard tunnels where possible
- Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
- Product website: https://netbird.io/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.

Community code is open source but mixed-licensed: most repository code is BSD-3-Clause, while server control-plane directories are AGPL-3.0. Enterprise-licensed features are excluded.

The quickstart deploys the full control plane as persistent containers on a customer-operated Linux VM.


### Category fit

- identity-access-management: Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 


### Cloud deployment evidence

- NetBird self-hosted control plane on a cloud VM (aws, azure, gcp, digitalocean, hetzner, oci): https://docs.netbird.io/selfhosted/selfhosted-guide
  The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Community Edition.


### Community and maintenance

The reviewed upstream contributor history includes mlsmaycon, pascal-fischer, lixmal, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

- Reviewed upstream application release: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

### Sources

- NetBird self-hosting quickstart: https://docs.netbird.io/selfhosted/selfhosted-quickstart

- NetBird advanced self-hosting guide: https://docs.netbird.io/selfhosted/selfhosted-guide

- NetBird repository license: https://github.com/netbirdio/netbird/blob/main/LICENSE

- NetBird Enterprise edition boundary: https://docs.netbird.io/selfhosted/enterprise

- Reviewed deployment artifact reference: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh

- Upstream release and published installer digest: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

### Licensing sources

- https://github.com/netbirdio/netbird/blob/main/LICENSE

- https://docs.netbird.io/selfhosted/enterprise

### Infrastructure sources

- https://docs.netbird.io/selfhosted/selfhosted-quickstart

- https://docs.netbird.io/selfhosted/selfhosted-guide


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Single sign-on: Documented. The advanced Community self-hosting guide supports a custom OpenID Connect identity provider and names self-hosted and managed IdP options. Enterprise-only identity lifecycle features are separate. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- SCIM provisioning: Explicitly unsupported. NetBird's edition comparison places SCIM user and group provisioning in the Enterprise Commercial License, not Community Edition. Treat SCIM as unavailable for this selected Community listing. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/enterprise (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- Security controls: Edition-dependent. The self-hosted control plane supports OIDC identity, policy-controlled peer access and customer-managed TLS, firewall and state. Community Edition excludes Enterprise SCIM, traffic-flow logging and active-active HA; secure relay, backup and upgrade operations remain customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19). Supporting source: Community and Enterprise capability boundary — https://docs.netbird.io/selfhosted/enterprise.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The v0.83.1 release publishes getting-started.sh with a verified SHA-256 digest. The script defaults several NetBird containers to latest, so pinning the script does not pin the complete deployment. Review and lock the generated Compose images and persistent state before production use. Scope: Community combined-server quickstart script; advanced multi-container configuration is separate. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19). Deployment artifact: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh. Artifact reference: v0.83.1/getting-started.sh; sha256:25ee5000a7421cb51a7c4c0f9090788951f531aba171d1fbff676f66d3265bfe. Supporting source: Upstream release and published installer digest — https://github.com/netbirdio/netbird/releases/tag/v0.83.1.

- Minimum footprint / sizing: Documented. The quickstart specifies one publicly reachable Linux VM with at least 1 CPU and 2 GB RAM plus Docker Compose, a domain and required TCP/UDP ports. This is a small single-node baseline, not an HA or large-fleet sizing recommendation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- License pricing: Documented. The selected Community Edition is open source under mixed BSD-3-Clause and AGPL-3.0 terms and does not require the Enterprise license. Enterprise HA, SCIM and related capabilities are separately commercial. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://github.com/netbirdio/netbird/blob/main/LICENSE (reviewed 2026-11-19). Supporting source: Enterprise license boundary — https://docs.netbird.io/selfhosted/enterprise.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v0.83.1 release was published 2026-11-13. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. Scope: NetBird Self-Hosted Community Edition upstream application, independently versioned from provider packages. Source: https://github.com/netbirdio/netbird/releases/tag/v0.83.1 (reviewed 2026-11-19).







## ONLYOFFICE Docs (Community Edition)

Community browser-based office document editing and co-authoring server.

- Listing: https://launchinyourcloud.com/directory/onlyoffice-docs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform.
- 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.onlyoffice.com/see-it-in-action
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. The supplied Vultr article installs DocSpace rather than Docs; the Vultr badge here comes from the reviewed Cloudron Docs package instead.

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

ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community browser-based office document editing and co-authoring server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

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

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/ (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/onlyoffice-docs.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. This source is distinct from the Cloudron package.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes agolybev, ShockwaveNN, trofim24, 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/ONLYOFFICE/DocumentServer/graphs/contributors

- Upstream project: https://github.com/ONLYOFFICE/DocumentServer

### Sources

- Cloudron Store: https://www.cloudron.io/store/onlyoffice-docs.html

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

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/

- AGPL-3.0 LICENSE: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

- Releases v10.0.0: https://github.com/ONLYOFFICE/DocumentServer/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/onlyoffice-docs.html

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

- https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/


### 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: Sources checked — unresolved. The reviewed Docs integration uses a host platform and signed JWT requests to the editor service. This does not establish standalone SAML/OIDC user login in the listed Docs Community engine. Confirm the identity-providing host and connector instead of transferring DocSpace SSO claims. Scope: Docs Community editor engine; host-platform identity is a separate layer. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (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 official Community guide installs the DocumentServer container with persistent data and configuration, including the JWT secret used by host integrations. The editor service still needs a document-management host/connector; deploying it alone does not supply a complete authenticated collaboration portal. Scope: ONLYOFFICE Docs Community editor-engine container, not DocSpace/Workspace. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (reviewed 2026-11-20). Deployment artifact: https://github.com/ONLYOFFICE/Docker-DocumentServer. Artifact reference: Current official Community Docker guide; pin an application-compatible image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/onlyoffice-docs.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: ONLYOFFICE Docs (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## OpenCRVS

Open-source civil registration software for birth, death and related registration workflows.

- Listing: https://launchinyourcloud.com/directory/opencrvs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Kubernetes manifests
- Architecture: OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates.
- 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.opencrvs.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.

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

OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Open-source civil registration software for birth, death and related registration workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS Terraform (aws): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP GKE Terraform (gcp): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner K8s Terraform (hetzner): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rikukissa, euanmillar, makelicious, 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/opencrvs/opencrvs-core/graphs/contributors

- Upstream project: https://github.com/opencrvs/opencrvs-core

### Sources

- AWS EKS Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md

- GCP GKE Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md

- Hetzner K8s Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf

- MPL-2.0: https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE

- Releases: https://github.com/opencrvs/opencrvs-core/releases

### Licensing sources

- https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 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: Sources checked — unresolved. The server-hosting guide distinguishes production user two-factor codes, test accounts and government VPN access, but does not establish a supported external user SAML/OIDC login path. VPN/server identity and the application authentication service are separate; verify the selected current release and country configuration. Scope: OpenCRVS enterprise/user federation remains unconfirmed. Source: https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/opencrvs/cloud-infrastructure/tree/main/terraform-templates/amazon-web-services. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The v1.7 guide lists production/staging at 8 CPUs/16 GB RAM with storage calculated from registration volume/attachments, versus development/QA at 4 CPUs/16 GB/320 GB. It specifies x86_64 Ubuntu 24.04 and separate backup requirements. Revalidate the selected release, clustering, throughput and recovery rather than applying this as an unrestricted current HA minimum. Scope: Versioned OpenCRVS v1.7 environment-specific baseline; current deployment/version sizing separate. Source: https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment (reviewed 2026-11-21).

- License pricing: Documented. GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: OpenCRVS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Plone

Self-hosted enterprise content management and publishing platform.

- Listing: https://launchinyourcloud.com/directory/plone/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, linode, digitalocean, hetzner
- 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: CloudFormation; Docker / Compose; Application platform deployment
- Architecture: Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box.
- 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://plone.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 community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.

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

Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted enterprise content management and publishing platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 


### Cloud deployment evidence

- plone-in-a-box (aws, linode, digitalocean, hetzner): https://github.com/collective/plone-in-a-box
  Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mauritsvanrees, jensens, vangheem, 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/plone/Products.CMFPlone/graphs/contributors

- Upstream project: https://github.com/plone/Products.CMFPlone

### Sources

- plone-in-a-box: https://github.com/collective/plone-in-a-box

- GPL-2.0 LICENSE.md: https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

- Releases v6.2.3: https://github.com/plone/Products.CMFPlone/releases

### Licensing sources

- https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

### Infrastructure sources

- https://github.com/collective/plone-in-a-box


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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: Documented. The community pas.plugins.oidc add-on documents OpenID Connect authentication for Plone. This is an add-on integration rather than a universal core entitlement; validate its Plone/backend/front-end compatibility and provider mapping for the selected deployment. Scope: Maintainer documentation for a Plone PAS OIDC add-on. Source: https://github.com/collective/pas.plugins.oidc (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. Cookieplone is the upstream-recommended project generator and creates the selected Plone backend/frontend project. It supplies an application project/deployment workflow, not an automatically hardened cloud-account infrastructure stack. Scope: Plone 6 Cookieplone project generation; Classic and Volto variants have different requirements. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (reviewed 2026-11-20). Deployment artifact: https://github.com/plone/cookieplone. Artifact reference: Moving generator repository; select compatible pinned template/dependency versions.

- Minimum footprint / sizing: Documented. The Plone 6 guide recommends 2 GB or more RAM per site and 40 GB or more disk. Volto frontend installation needs at least 2 GB RAM; lower backend process minima and swap figures are not whole-stack sizing. Addons, caches, builds and HA require additional resources. Scope: Rough upstream Classic/Volto requirements, not a 100-user/1-TB HA benchmark. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (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: Plone; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/plone/Products.CMFPlone/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Windmill Self-Hosted

Run scripts and workflows with customer-operated execution workers and an app builder.

- Listing: https://launchinyourcloud.com/directory/windmill/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas
- Architecture: Customer-operated server, worker processes and PostgreSQL job/state storage
- Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
- Product website: https://www.windmill.dev/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.

Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately.

Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- workflow-automation: Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- ubicloud: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). Source: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial (checked 2026-11-12). 


### Cloud deployment evidence

- Windmill upstream self-hosting provider compatibility (aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud): https://github.com/windmill-labs/windmill
  The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Windmill production deployment on Ubicloud Kubernetes (ubicloud): https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial
  Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-host architecture, Docker and provider guidance: https://www.windmill.dev/docs/advanced/self_host

- Project capabilities and license files: https://github.com/windmill-labs/windmill

- Self-hosted edition limits: https://www.windmill.dev/pricing

- Licensing and edition terms: https://github.com/windmill-labs/windmill/blob/main/LICENSE

- Windmill production deployment on Ubicloud Kubernetes: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial

- Windmill v1.878.0 release: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0

- Windmill v1.877.0 policy hardening: https://github.com/windmill-labs/windmill/releases/tag/v1.877.0

- Configured AI-key model enforcement: https://github.com/windmill-labs/windmill/pull/12527

- GitHub App repository approval persistence: https://github.com/windmill-labs/windmill/pull/12524

### Licensing sources

- https://github.com/windmill-labs/windmill/blob/main/LICENSE

- https://www.windmill.dev/pricing

### Infrastructure sources

- https://www.windmill.dev/docs/advanced/self_host


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 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. The self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits. Scope: Instance user login; built-in SSO and Enterprise SAML have different entitlements. Source: https://www.windmill.dev/docs/advanced/setup_oauth (reviewed 2026-11-20). Supporting source: Enterprise SAML and SCIM — https://www.windmill.dev/docs/advanced/saml_and_scim.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access. Scope: Windmill configured AI-key proxy and GitHub App repository-resource authorization. Source: https://github.com/windmill-labs/windmill/pull/12527 (reviewed 2026-11-19). Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval behavior — https://github.com/windmill-labs/windmill/pull/12524.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases. Scope: Upstream self-hosted stack; database upgrades require explicit migration planning. Source: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing. Scope: Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design. Source: https://www.windmill.dev/docs/advanced/self_host (reviewed 2026-11-20).

- License pricing: Documented. At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence. Scope: Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate. Source: https://github.com/windmill-labs/windmill/blob/v1.878.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use. Scope: Upstream Windmill self-hosted release. Source: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/windmill-labs/windmill/releases/tag/v1.875.0. Supporting source: v1.877.0 policy changes — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: AI model allowlist enforcement — https://github.com/windmill-labs/windmill/pull/12527. Supporting source: GitHub App repository approvals — https://github.com/windmill-labs/windmill/pull/12524.




### Security and lifecycle reviews

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

- Windmill v1.877.0 configured-AI-key policy hardening (security-advisory): Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list. Scope: Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill. Conditions: Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model. Action: Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources. Source: https://github.com/windmill-labs/windmill/pull/12527; reviewed 2026-11-19. Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval persistence — https://github.com/windmill-labs/windmill/pull/12524.



