head to head · open source
ProxmoxVE vs cadence
ProxmoxVE has 30,010 GitHub stars, 2,938 forks, 27 open issues and last shipped yesterday. cadence has 9,535 stars, 931 forks, 205 open issues and last shipped 4 days ago. ProxmoxVE leads on adoption by 215% (30,010 vs 9,535 stars). ProxmoxVE is written in Shell under MIT; cadence is written in Go under Apache-2.0. ProxmoxVE has attracted 10% as many forks as stars, cadence 10%. 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 | cadence | |
|---|---|---|
| GitHub stars | ★ 30K | ★ 9.5K |
| License | MIT | Apache-2.0 |
| Written in | Shell | Go |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 2.9K | ⑂ 931 |
| 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 cadence if
- You want the cadence feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and cadence 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 cadence
Cadence Cadence Workflow is an open source platform since 2017 for building and running scalable, fault tolerant, and long running workflows. This repository contains the core orchestration engine and tools including CLI, schema managment, benchmark and canary. Getting Started Cadence backend consists of multiple services, a database (Cassandra/MySQL/PostgreSQL) and optionally Kafka+Elasticsearch. As a user, you need a worker which contains your workflow implementation. Once you have Cadence backend and worker(s) running, you can trigger workflows by using SDKs or via CLI. 1. Start cadence backend components…
read the full cadence 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 cadence more popular?
ProxmoxVE has 30,010 GitHub stars and cadence has 9,535. ProxmoxVE has the larger community by that measure.
Are ProxmoxVE and cadence free?
Both are open source. ProxmoxVE is licensed under MIT and cadence under Apache-2.0. Neither carries a licence fee.
What is the difference between ProxmoxVE and cadence?
ProxmoxVE is written in Shell and cadence in Go. 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 cadence?
Choose ProxmoxVE if you want the larger community (30,010 stars) or its MIT licence terms. Choose cadence if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.