head to head · open source
ProxmoxVE vs loopx
ProxmoxVE has 30,010 GitHub stars, 2,938 forks, 27 open issues and last shipped yesterday. loopx has 6,537 stars, 619 forks, 102 open issues and last shipped yesterday. ProxmoxVE leads on adoption by 359% (30,010 vs 6,537 stars). ProxmoxVE is written in Shell under MIT; loopx is written in Python under Apache-2.0. ProxmoxVE has attracted 10% as many forks as stars, loopx 9%. loopx 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 | loopx | |
|---|---|---|
| GitHub stars | ★ 30K | ★ 6.5K |
| License | MIT | Apache-2.0 |
| Written in | Shell | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 2.9K | ⑂ 619 |
| 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 loopx if
- You want the loopx feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Python
- You evaluated both and loopx 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 loopx
LoopX The open, provider neutral, stateful control plane for long horizon agents. Runs on top of Codex, Claude Code, Cursor, and other agent harnesses. LoopX preserves objectives, gates, todos, evidence, quota, and handoffs across turns; the harness executes bounded work. Public website · Blog · Docs · Developer Book · Try LoopX · See real loops · How it works · 简体中文 Open and provider neutral, LoopX is a lightweight state kernel and local first control plane for loop engineering. It runs on top of different agent harnesses rather than replacing them, providing the long horizon state, semantic decisions about…
read the full loopx 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 loopx more popular?
ProxmoxVE has 30,010 GitHub stars and loopx has 6,537. ProxmoxVE has the larger community by that measure.
Are ProxmoxVE and loopx free?
Both are open source. ProxmoxVE is licensed under MIT and loopx under Apache-2.0. Neither carries a licence fee.
What is the difference between ProxmoxVE and loopx?
ProxmoxVE is written in Shell and loopx in Python. 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 loopx?
Choose ProxmoxVE if you want the larger community (30,010 stars) or its MIT licence terms. Choose loopx if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.