Proxmox PulseProxmox 24/7 Support: Which Subscription Tier Pays Off
Proxmox enterprise support goes 24/7 on 19 October 2026. Here is the real per-socket cost of each tier and how to pick one without overbuying.
Proxmox Pulse
On this page
The Last Objection Just Got Answered
For years the argument against putting Proxmox VE under something that actually matters went: the software is fine, the price is a gift, but support is Monday to Friday, 07:00 to 17:00, on Austrian public-holiday calendar. If your cluster fell over at 02:00 on a Sunday, you were on your own until Vienna woke up.
On 2 September 2026 Proxmox announced that ends. From 19 October 2026, enterprise support goes 24/7, and the company has stood up Proxmox North America Inc. in Kingston, Ontario to put staff in North American time zones. The stated context: over 2.3 million active Proxmox VE servers worldwide and more than 60,000 enterprises on active support plans.
This changes the buying decision, not the software. Here is what each tier now costs, what it actually gets you, and how to avoid paying for coverage you will never call.
Key Takeaways
- 24/7 goes live 19 October 2026, covering Proxmox VE, Proxmox Backup Server and Proxmox Datacenter Manager.
- Premium gets it on day one. Standard customers are onboarded in a window later in Q4 2026. Basic keeps its published SLA.
- Pricing is per occupied physical CPU socket per year, unchanged: Community €120, Basic €370, Standard €550, Premium €1,100.
- The tiers differ only in support entitlements. Every production tier has identical feature access - there is no crippled edition.
- Proxmox North America handles local sales, contract administration, partner enablement and certified training; existing contracts remain valid with transfers available at 2027 renewal.
The Tiers, With the Numbers That Matter
| Tier | Per socket / year | Tickets | Response target | 24/7 from |
|---|---|---|---|---|
| Community | €120 | none (forum only) | n/a | n/a |
| Basic | €370 | 3 / year | 1 business day | unchanged |
| Standard | €550 | 10 / year | 4 hours* | later in Q4 2026 |
| Premium | €1,100 | unlimited | 2 hours* | 19 October 2026 |
* Today those targets apply during the published window, Monday to Friday 07:00-17:00 CET/CEST on Austrian business days, with a guaranteed first response for critical requests within a business day. The 19 October change is precisely what removes that window for Premium.
Two things people get wrong reading this table.
First: Community is a real tier, not a trial. €120 per socket buys access to the enterprise repository - the more conservative, later-promoted package stream - with no ticket entitlement. For a homelab or a lab cluster where you want the stable packages and do not need anyone to answer, that is often the correct purchase, and it is a fifth the price of Standard.
Second: the ticket counts are the real product. Basic gives you three tickets a year. If you are the kind of shop that opens three tickets in a bad week, Basic is not cheaper than Standard, it is just an invoice with a cliff in it.
Doing the Socket Math Before You Buy
Proxmox bills per occupied physical CPU socket, independent of core count. Count them properly before you price anything:
lscpu | grep -i 'socket\|core(s) per socket\|^cpu(s):'
CPU(s): 64
Core(s) per socket: 32
Socket(s): 2
That node is two subscriptions. A single-socket 64-core EPYC box delivering the same capacity is one.
Worked example - a three-node production cluster, single-socket AMD hosts:
| Tier | Per node | 3-node cluster / year | 3-year |
|---|---|---|---|
| Community | €120 | €360 | €1,080 |
| Basic | €370 | €1,110 | €3,330 |
| Standard | €550 | €1,650 | €4,950 |
| Premium | €1,100 | €3,300 | €9,900 |
The same three nodes with dual sockets double every figure. This is the lever that decides your bill, and it points the opposite way from per-core licensing: consolidating onto fewer, denser single-socket hosts cuts your Proxmox cost while it would raise a per-core one. If you are still holding a VMware quote next to this, our per-core pricing comparison walks the same cluster through both models.
Note that Proxmox expects a uniform level across the cluster. Mixing one Premium node with two Community nodes is not supported and, more practically, makes the conversation awkward the moment an incident spans nodes - which cluster incidents almost always do.
Which Tier Actually Fits
Homelab or lab cluster. No subscription, or Community if you want the enterprise repository. You are not going to open a ticket, and the no-subscription repository has been carrying homelabs for a decade. Budget the €120 per socket if package conservatism matters to you more than the login notice does.
Small business, in-hours operations, someone technical on staff. Basic. Three tickets a year is enough when your failure modes are "we need a second opinion on this upgrade" rather than "production is down." Pair it with a tested restore path - a Proxmox Backup Server you have actually restored from is worth more at 02:00 than any SLA.
Production with an out-of-hours obligation. Standard from 19 October, Premium if the obligation has money attached to it. The question is not whether you can fix things yourself; it is whether you want to be the only person who can, at 03:00, on the night your storage controller does something novel.
Regulated, contractual, or customer-facing SLA. Premium. Unlimited tickets and a two-hour target with round-the-clock coverage is the only tier that maps onto an SLA you have signed with somebody else. This is the tier the announcement exists for - Proxmox COO Tim Marx framed it as removing "one of the last reasons organizations hesitate to put open-source infrastructure at production's core," and that is an accurate read of who was hesitating.
Air-gapped or offline environments. Worth knowing the 24/7 expansion explicitly includes offline updates and key activation, which has historically been the awkward part of running subscribed Proxmox on an isolated network.
Applying a Key, End to End
Buying is the easy part; people still trip on activation because it is per node.
# on each node
pvesubscription set pve4p-0123456789
pvesubscription update --force
pvesubscription get
You want status: active and the correct product level in that last output. Then move the node onto the enterprise package stream. Proxmox VE 9 uses deb822 files on the Debian 13 base:
cat /etc/apt/sources.list.d/pve-enterprise.sources
Types: deb
URIs: https://enterprise.proxmox.com/debian/pve
Suites: trixie
Components: pve-enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Disable the pve-no-subscription component in /etc/apt/sources.list.d/proxmox.sources at the same time so you are not mixing streams, then confirm:
apt update
A 401 Unauthorized against enterprise.proxmox.com after this means the key did not activate on that node - keys are bound per host, so a working key on node one tells you nothing about node three. Check each one.
Getting Value Out of a Ticket
A support entitlement is only worth what you can hand the engineer at the start. This matters more, not less, at 03:00 - the round-the-clock bench does not know your cluster, and every hour they spend asking for context is an hour of your outage.
Proxmox ships a single command that collects the whole picture:
pvereport > /root/pvereport-$(date +%F-%H%M).txt
That captures package versions, storage configuration, network setup, cluster status and guest configs in one file. Generate it on the affected node, not on the healthy one you can still log into comfortably.
Pair it with the logs from the window in question:
journalctl --since '2 hours ago' > /root/journal-$(date +%F-%H%M).txt
ha-manager status
pvecm status
Then write the ticket the way you would want to receive it: what changed most recently, what you already tried, what the actual versus expected behaviour is, and whether the cluster is currently quorate. A ticket that opens with "three-node cluster, node 2 fenced at 02:14 after a corosync ring flap, quorum held, pvereport attached" gets a real answer on the first reply. One that opens with "cluster is broken" spends its first four hours becoming the first ticket.
One entitlement detail worth knowing: the subscription covers Proxmox VE, Proxmox Backup Server and Proxmox Datacenter Manager. If you run PBS on a separate physical box - and you should - that host is its own socket count. Budget for it rather than discovering it at purchase time.
What This Does Not Change
The subscription buys support and a package stream. It does not unlock features - all production tiers have identical feature access, which remains one of the more honest things about the Proxmox commercial model.
It also does not replace your own operational work. Twenty-four-hour vendor support shortens the tail of an incident; it does not shorten the part where you discover your backups were failing silently for six weeks. If you are budgeting for a subscription this quarter, budget the same afternoon for a restore test and a look at the post-upgrade tuning checklist on every node.
And if you are still on the 8.x line, note that it went end of support on 31 August 2026. A support contract on an unsupported release is not a plan - the upgrade to 9.x comes first, then the subscription decision.
Conclusion
The 19 October change is a genuine shift in what you can defend in a procurement meeting: vendor-direct, round-the-clock support for a hypervisor that bills per socket instead of per core. Premium gets it immediately, Standard follows later in Q4, and North American customers now have a local entity to contract with.
Count your occupied sockets, be honest about how many tickets you will actually open, keep the level uniform across the cluster, and verify activation node by node. For most three-node shops the answer lands on Standard - and for the first time, that answer includes somebody picking up on a Sunday.
