Proxmox VE Wikipedia Article - Please Review

Tmanok

Renowned Member
Hi Everyone,

As Proxmox VE has grown quite substantially since I began using it, I thought I'd blend together my Wikipedia editing with my in-depth knowledge of the software and my general awareness of the company behind it. Having received the Proxmox VE Advanced Certification in the 7.2 era, I had at the time a reasonable understanding of the training and certification process three years ago, and none of that was well documented. My edit works out to roughly a quarter of the article in Wiki-source bytes as it now stands, which as far as I can tell makes it the largest single edit the page has had but not the largest lifetime user contrib to the article, so it seemed worth mentioning here instead of dropping it in and walking away. The largest contributor to the page is MipsHH as far as I can tell, by the way, but he has not edited it in a number of years.

The article had drifted a long way out of date. It still listed 9.0 beta1 as the current preview, gave AMD64 as the only supported platform, described Datacenter Manager as a 0.9 beta, carried a storage list with Sheepdog in it, and claimed a two to four month release cadence that hasn't described the last several releases. Most of the post-2023 development wasn't represented at all. Here's the full changelog (I think):
  • Infobox. x86-64 and Arm64, removed the stale preview fields, updated the interface and language entries.
  • History. Rebuilt from 0.9 in April 2008 through to 9.2 in May 2026, with the 2.0 cluster stack and AGPLv3 relicensing, the 4.0 move from OpenVZ to LXC, and the 5.x replication and Ceph work given their own place. The arm64 build from August 2026 is in there too.
  • Features. Restructured against the current administration guide rather than whatever was true in 2016. Storage back ends now reflect what's actually documented, SDN and the nftables preview are covered, HA includes the 9.0 affinity rules and the 9.2 dynamic load balancer, and 9.1's OCI images for LXC, 8.4's mediated-device live migration, virtiofs and the third-party backup API are all described.
  • VMware migration and adoption. New section, sourced to Ars Technica, The Register, Gartner and Broadcom's and VMware's own material. Proxmox's host counts are in there, attributed as company-reported figures rather than presented as measured market share.
  • Datacenter Manager. Rewritten around stable 1.0 from December 2025 and 1.1 from May 2026, instead of the beta and its missing features.
  • Development and commercial model. AGPLv3, no feature gating between tiers, per-socket subscriptions, and the September 2026 announcements covering 24/7 enterprise support and Proxmox North America.
  • Removed. The Trivia section, the ProxLB paragraph, and the release cadence claim because it was uncited.
Generally, I don't like to remove information from articles, it pains me to do it, but I knew that someone else eventually would- especially after this veteran named Timtrent came through a few years ago and axed what were to my mind sane things to keep on the article such as the built-in well documented features of the product simply because citations hadn't yet been added or it was overly dependent on a single source- which in this case is quite valid as it's an extensive piece of infrastructure software which has a unified administration guide... But anyway, I couldn't see an official source for the release cadence and highly celebrated and experienced editors like Timtrent are simply doing their job.

What I'd like from folks here is corrections. Wikipedia runs on published sources, so I can only use what Proxmox or the press has actually put in writing, but if something in there is wrong or misleading I'd rather hear it from people who use this daily than find out in a revert like MipsHH did with Timtrent. The arm64 hardware support wording and the storage back end list are the two places I'd look hardest. :)

Last thing, some people unfamiliar with Wikipedia editing may be wondering why PVE staff can't update the article- that's a major red flag and their changes will likely be removed if anyone ever discovers their conflicting relationship between their employer and what is meant to be an objective platform for information sharing. However, Proxmox as a company can and should have more interviews with the press if they want their product to be more widely known and if they want more detailed information made accessible via Wikipedia. Professional journalism, research papers, and yes administrative or company website publications, or Proxmox VE Wiki articles can count but their use is not as widely accepted. For a list of sources Wikipedia has actually "rated" for reliability and usability, check this out: https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources They throw a lot of shade on that page, it's pretty juicy for academic writing.

Thanks,


Tmanok / Tmanaok on Wikipedia and Gmail
https://lightyearlabs.ca/
https://en.wikipedia.org/wiki/User:Tmanaok

Article Link for those who missed it above: https://en.wikipedia.org/wiki/Proxmox_Virtual_Environment
 
Last edited:
Great work.

I have just quickly skimmed through the Wikipedia page. I don't see wrong or misleading info in the storage section.

My 2 cent for addition if possible (I am not familiar with contribution to wikipedia):
- Mention to Proxmox Offline Mirror tool:
https://pom.proxmox.com/introduction.html#what-is-proxmox-offline-mirror

- Include a link to the Proxmox wiki page Migrate to Proxmox VE:
https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
Which includes additional useful information regarding storage and Migrating to Proxmox VE in general.

- And maybe worth addition is the company new branch in Canada Proxmox North America Inc:
 
  • Like
Reactions: Tmanok
Last edited:
Thanks Aaron, thanks Longer,

That's exactly the kind of feedback I was hoping for when I posted.

  • PVE Mirror now has its own subsection now under Related Proxmox software, next to PBS, PMG and PDM. I also added a line to the history section for 7.3, since that's where offline mirror support landed on the PVE side and it gives the tool a chronological anchor. Good catch, I'd missed it entirely.
  • Re: PVE Wiki... Wikipedia's external links guideline steers hard away from how-to material: the encyclopedia describes what a thing is, not how to do it, so a migration walkthrough is the kind of link that gets pruned later by an editor less enthusiastic as an end user about the product. The migration material in the article is already carried by the administration guide and the 8.2/8.3 press releases as citations, so nothing against the PVE Wiki, I still personally use it quite a lot but Wikipedia isn't a good place to link them.
  • @aaron Correct the article refers to the citable source which is the website / press release rather than the forum, however, you helped me find an issue with what I had written which is that the support comes out in phases rather than only for a specific support tier. That's now been fixed :)
  • One more thing I found was the NVIDIA collaboration from July, which wasn't covered at all. I tried to be explicit for end readers about how PVE hosts the management services for those deployments, not the accelerated workloads themselves, because while that's intuitive to technical folks I think the wrong impression can be gathered by a layman. The addition of the NVIDIA Mission Control also explains why the Arm64 launch shipped with Grace and Vera as the only officially supported silicon, which previously read as somewhat arbitrary.
  • Second to last fix: The HA arm/disarm feature is described properly now instead of as vague "maintenance controls", kernel 7.0 is in the stack sentence, and Ceph Tentacle 20.2 alongside Squid 19.2 is in the storage section.
  • And finally the last fix: Ceph monitoring is native and new rather than "expanded", and the article now notes that enterprise plans on managed PVE and PBS remotes cover PDM without a separate subscription key. That one struck me as genuinely useful and not obvious from the outside.

Thanks again, so glad for the collaboration and ideas!


Tmanok / Tmanaok / Triston
 
  • Like
Reactions: longer