Workflow automation on Hetzner
Business automation, integrations, scripts and API workflows.
2 documented options on Hetzner Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| n8n Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean, Heroku, Hetzner | Customer-operated Servers / containers | Source Available Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components | Docker Compose with persistent data; database and worker topology selected for workload | Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| Windmill Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean, Render, Hetzner, Fly.io, Ubicloud | Customer-operated Servers / containers | Open Source / Open Core AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits | Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas | Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
n8n Self-Hosted
Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.
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.
- 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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Windmill Self-Hosted
Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.
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.
- 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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
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.
Plan this deployment
Account boundary: Hetzner account and cloud project. Access: Project access and server SSH keys. Network: Cloud networks, public IPs and firewalls.
Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings