Software on Hetzner
Software with a documented deployment path in a customer environment on Hetzner Cloud.
9 listings, including 9 from other publishers. Search and filter Hetzner listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Hetzner account and cloud project
- Network
- Cloud networks, public IPs and firewalls
- Identity & access
- Project access and server SSH keys
- Deployment tooling
- Create a server with a supported OS and install the application; manage updates, storage and backups in the customer project.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- 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. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Browse by category
7 categories on Hetzner. Counts show matching listings; a listing can appear in more than one category.
Business operations2 categories
Content & collaboration2 categories
Developer platforms & operations2 categories
AI tools & infrastructure1 category
No categories match your search.
Documented software
Deployment evidence and qualifications
Self-hosted conferencing and virtual classroom platform.
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Deployment evidence and qualifications
Community office editing server for integration with a document platform.
- Hetzner Tutorial ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Hetzner Tutorial ↗
Deployment evidence and qualifications
Self-hosted discussion and community platform for workplace collaboration and customer support communities.
- Discourse supported cloud server installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
Scope: 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.
License: GPL-2.0 core; review extensions separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Discourse supported cloud server installation ↗
Deployment evidence and qualifications
Automate integrations and business processes with a customer-hosted workflow editor and runtime.
- n8n self-hosted deployment on Hetzner ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope: 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.
License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- n8n self-hosted deployment on Hetzner ↗
Deployment evidence and qualifications
Open-source zero-trust networking control plane self-hosted on a customer cloud VM.
- NetBird self-hosted control plane on a cloud VM ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Community Edition. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
Scope: 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.
License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- NetBird self-hosted control plane on a cloud VM ↗
Deployment evidence and qualifications
Community browser-based office document editing and co-authoring server.
- Hetzner Tutorial ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Hetzner Tutorial ↗
Deployment evidence and qualifications
Open-source civil registration software for birth, death and related registration workflows.
- Hetzner K8s Terraform ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Hetzner K8s Terraform ↗
Deployment evidence and qualifications
Self-hosted enterprise content management and publishing platform.
- plone-in-a-box ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- plone-in-a-box ↗
Deployment evidence and qualifications
Run scripts and workflows with customer-operated execution workers and an app builder.
- Windmill upstream self-hosting provider compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
Scope: 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.
License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Windmill upstream self-hosting provider compatibility ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings