head to head · open source
ProxmoxVE vs n8n-helm-chart
ProxmoxVE has 30,010 GitHub stars, 2,938 forks, 27 open issues and last shipped yesterday. n8n-helm-chart has 709 stars, 246 forks, 64 open issues and last shipped 2 months ago. ProxmoxVE leads on adoption by 4,133% (30,010 vs 709 stars). ProxmoxVE is written in Shell under MIT; n8n-helm-chart is written in Go Template under Apache-2.0. ProxmoxVE has attracted 10% as many forks as stars, n8n-helm-chart 35%. ProxmoxVE was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| ProxmoxVE | n8n-helm-chart | |
|---|---|---|
| GitHub stars | ★ 30K | ★ 709 |
| License | MIT | Apache-2.0 |
| Written in | Shell | Go Template |
| Last push | 2026-11-02 | 2026-09-15 |
| Forks | ⑂ 2.9K | ⑂ 246 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick ProxmoxVE if
- You weight community size — 30K stars and counting
- You want the MIT license terms
- Your stack matches Shell
- You value the larger contributor base for long-term maintenance
pick n8n-helm-chart if
- You want the n8n-helm-chart feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go Template
- You evaluated both and n8n-helm-chart fits your workflow better
About ProxmoxVE
Proxmox VE Helper Scripts One command installations for services, containers, and VMs on Proxmox VE A community project — built on the foundation of @tteck 's original work What is this? Simplify your Proxmox VE setup with community driven automation scripts. Install and configure popular self hosted services with a single command — no manual package hunting, no config file archaeology. Paste a command into your Proxmox shell, answer a few prompts, and your container or VM is up and running. The collection covers hundreds of services across categories like home automation, media servers, networking tools…
read the full ProxmoxVE overview →
About n8n-helm-chart
[!NOTE] The n8n Helm chart is growing in popularity. We're looking for additional conscientious and accurate maintainers and contributors to improve and maintain this chart, governance, development, documentation and CI/CD workflows. If you're interested in making a difference, join the discussion. n8n Helm Chart for Kubernetes n8n is an extendable workflow automation tool. The Helm chart source code location is github.com/8gears/n8n helm chart Requirements Before you start, make sure you have the following tools ready: Helm = 3.8 external Postgres DB or embedded SQLite (SQLite is bundled with n8n) Helmfile…
read the full n8n-helm-chart overview →
More in Productivity & Utilities
Related comparisons
More Automation projects
Compare either of these against the rest of the Automation field.
Frequently asked questions
Is ProxmoxVE or n8n-helm-chart more popular?
ProxmoxVE has 30,010 GitHub stars and n8n-helm-chart has 709. ProxmoxVE has the larger community by that measure.
Are ProxmoxVE and n8n-helm-chart free?
Both are open source. ProxmoxVE is licensed under MIT and n8n-helm-chart under Apache-2.0. Neither carries a licence fee.
What is the difference between ProxmoxVE and n8n-helm-chart?
ProxmoxVE is written in Shell and n8n-helm-chart in Go Template. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, ProxmoxVE or n8n-helm-chart?
Choose ProxmoxVE if you want the larger community (30,010 stars) or its MIT licence terms. Choose n8n-helm-chart if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.