Proxmox VE vs XCP-ng pricing: which subscription model costs less for your hosts
If you are leaving VMware and need to price support for a small or growing cluster, the short answer is this: Proxmox VE charges per CPU socket per year across four support tiers, and every tier ships the same software. Vates VMS charges a flat annual fee for up to three hosts on its Essential and Essential+ plans, and a per-host fee above that. Both platforms run without a paid subscription, so the real question is how much support depth you need to buy. Which model costs less depends on your host count, the number of sockets in each host, and how fast you need a response. The Proxmox VE vs XCP-ng overview page covers the wider comparison, and this section focuses only on the money.
Start by writing down three numbers: hosts today, hosts in 18 months, and sockets per host. Proxmox pricing scales with sockets, so a dual-socket host costs twice as much as a single-socket host at the same tier. Vates pricing scales with hosts, so adding a dense two-socket host costs the same as adding a light one, but the first three hosts sit under one flat fee on Essential or Essential+ and the Pro tier has a three-host minimum. Put both price lists into a spreadsheet for your exact counts. Proxmox lists its tiers in euros, while Vates lists its VMS plans in dollars, so convert both at the same date before comparing. Check the Proxmox VE subscriptions page and Vates pricing and support page for current figures.
Recurring cost is the bigger driver over several years, so ask each vendor for a written quote that states the term, the response times, the ticket allowance, and whether add-ons such as Vates storage products are included or extra. Ask Vates whether XOSTOR is needed for your storage design, because its listed per-host add-on cost would be on top of the base plan. Confirm with Proxmox which tier includes the enterprise repository you need for production hosts. Also budget your own staff time for upgrades and migration work, which neither subscription covers. Treat any cost figure you did not get in writing as unconfirmed until a vendor quote arrives.
How the two subscription models are built
This table breaks each vendor's pricing into unit of charge, tiers, inclusions, free use, repository access, host or socket rules and add-ons, with every price stated in its own currency. Read it as a set of rules to apply to your own host and socket counts, then check the yearly total against the vendor's current pricing page before you decide.
| Pricing part | Proxmox VE | XCP-ng with Vates VMS |
|---|---|---|
| Unit of charge | Per CPU socket per year | Flat plans for up to 3 hosts, or per host per year |
| Published tiers and prices | Community 120 euros, Basic 370 euros, Standard 550 euros, Premium 1,100 euros (each per socket per year) | Essential 2,000 USD and Essential+ 4,000 USD per year (up to 3 hosts); Pro 1,000 USD per host per year; Enterprise 1,800 USD per host per year |
| What each tier includes | Same software features in every tier; tiers differ in support tickets and response time (Community has no tickets; Premium has unlimited tickets with a 2-hour response) | Vates VMS plans bundle commercial support; Enterprise adds 24/7 support. Confirm exact entitlements per plan with Vates |
| Free use | The software can be used without a subscription | XCP-ng hypervisor and Xen Orchestra are open source with no license fees; commercial support is optional |
| Repository access | Enterprise repository needs a valid subscription key and is recommended for production; the no-subscription repository suits testing and non-production use | Repository and update access depends on the plan; confirm with Vates which update channels each plan includes |
| Minimum host or socket rules | Charged per socket, so host count and socket count per host both drive the yearly total; confirm cluster-wide rules with Proxmox | Essential and Essential+ cover up to 3 hosts; Pro requires a 3-host minimum and Enterprise a 4-host minimum |
| Add-ons | Support tiers are the main add-on; storage is built in through Ceph and ZFS | XOSTOR hyperconverged storage at 800 to 1,200 USD per host per year (source: Vates pricing and support page) |
| Recurring or one-time | Recurring yearly subscription per socket | Recurring yearly plan or per-host fee; no one-time license purchase is listed |
What each platform lets you run without paying
Proxmox VE software can be run without a subscription. The platform is licensed under the GNU Affero General Public License, version 3, and every subscription tier includes the same software features. What a subscription changes is support entitlements and access to the enterprise repository, which requires a valid subscription key and is the recommended repository for production. The no-subscription repository is described as suited to testing and non-production use. Before you run production hosts on it, confirm with Proxmox which packages, host updates and Ceph packages the no-subscription repository delivers, and whether your change control accepts that update cadence. Check the Proxmox VE package repositories documentation for the current repository layout.
XCP-ng and Xen Orchestra are described by Vates as open source with no license fees. Vates presents the XCP-ng hypervisor and Xen Orchestra as open-source projects with no limits and no license fees, and says that commercial support subscriptions add SLAs. The cost of the free route is therefore the internal effort of patching, monitoring and troubleshooting without a contracted response time. Ask Vates to state in writing which components are covered by a support subscription and which remain community-supported. Confirm whether the free build gives you the same update channel and LTS track you would receive with paid support, since the XCP-ng 8.3 LTS release is documented as supported until November 30, 2028.
Build the free-versus-paid decision around your production repositories. Pricing comparisons often stop at the license line, but the decision sits in the repository and update path. For each platform, write down the repository your hypervisors would pull from, who applies security updates, how long your staff can wait for a fix without a contracted response, and whether an audit or customer contract requires a supported vendor. That list tells you whether the free option is a complete production choice for your team or only a starting point. Treat any gap you find as a line item to price with the vendor before go-live, not as an assumption.
Which host and socket counts change the yearly total
Proxmox VE bills by CPU socket and XCP-ng's commercial support from Vates bills by host or by flat plan, so the same cluster can land on very different yearly totals. The cards below name the counts and conditions that move each side of the comparison.
Sockets per Proxmox host
Proxmox VE subscriptions are priced per CPU socket per year, so each physical host's socket count is multiplied by the tier price. A dual-socket node costs twice a single-socket node at the same tier, and every node in the cluster needs its own subscription. Check the socket count on every host you plan to run, including spares and hosts reserved for failover, because those are billed too.
Tier choice moves the per-socket total
Proxmox tiers share the same software and differ in support tickets, response time and enterprise repository access. Community is priced at 120 euros per socket per year, Basic at 370 euros, Standard at 550 euros and Premium at 1,100 euros. Multiply each tier by your total socket count to see how fast the bill grows as the cluster expands.
Flat Vates plans for up to three hosts
Vates Essential and Essential+ are flat yearly plans for up to three hosts, so adding a host inside that limit does not raise the subscription price. Essential is listed at $2,000 per year and Essential+ at $4,000 per year. A three-host cluster with dense nodes can cost less here than the same cluster under per-socket billing, but a fourth host moves you out of the flat tier.
Per-host pricing and the Pro minimum
Vates Pro is priced at $1,000 per host per year with a three-host minimum, so a two-host pilot still pays for three hosts. Each host you add beyond that increases the total in a straight line. Confirm with Vates whether a host that is powered off, used only for failover or running only management workloads is counted in the host total.
Enterprise minimum and 24/7 support
Vates Enterprise is priced at $1,800 per host per year with a four-host minimum and includes 24/7 support. Clusters below four hosts pay for four under this plan, and the total rises with every host beyond that. If your team needs round-the-clock response, price Enterprise against Proxmox Premium at the socket count you actually run.
Support response needs in the total
Response time is a cost driver on both sides. Proxmox Basic offers 1 business day response, Standard 4 hours and Premium 2 hours, while Vates SLAs are tied to the plan you buy. Map your incident severity targets to a tier before comparing totals, because a cheaper tier may leave you without the response window your operations team requires.
Add-ons such as XOSTOR per host
Vates sells add-ons on top of the base plan, and XOSTOR hyperconverged storage is priced at $800 to $1,200 per host per year. If you plan to use it, the add-on is charged on every host that participates, so it can outweigh the base plan on a small cluster. Ask Vates which hosts the add-on covers and whether it is priced on the same host count as the base plan.
How the yearly total shifts by cluster shape
For a cluster of up to three hosts, the two models produce very different shapes. Proxmox VE totals scale with CPU sockets, so the yearly figure is the socket count multiplied by the tier price. Vates offers two flat plans that cover up to three hosts, so the total does not change with host count inside that range, while its per-host Pro plan has a three-host minimum. Check the Proxmox VE pricing page and the Vates pricing and support page for current terms.
- Proxmox formula: sockets multiplied by the annual tier price. Illustrative: three single-socket hosts at Community (120 euros per socket) is 360 euros per year, and at Premium (1,100 euros per socket) it is 3,300 euros per year.
- Vates flat plans: Essential at $2,000 per year and Essential+ at $4,000 per year, each for up to 3 hosts.
- Vates Pro: $1,000 per host per year with a 3-host minimum. Illustrative: three hosts is $3,000 per year.
- Currency: Proxmox lists euros and Vates lists dollars, so compare totals in one currency at quote time and confirm the tax treatment.
- Community tier: it carries no support tickets, so it sets a cost floor rather than a support plan.
Confirm with each vendor whether every physical host counts toward the host limit and which currency, tax and renewal terms apply to the quote.
As a cluster grows, the two formulas diverge. Proxmox VE pricing follows sockets, so a dual-socket host costs twice what a single-socket host costs at the same tier. Vates Pro and Enterprise follow hosts, and the flat plans only cover up to three hosts. Storage add-ons also change the total, because Vates sells XOSTOR separately while the Proxmox tiers share one feature set.
- Socket-driven Proxmox: illustrative, six hosts with two sockets each is 12 sockets. At Standard (550 euros per socket), that is 6,600 euros per year.
- Host-driven Vates Pro: illustrative, six hosts at $1,000 per host is $6,000 per year.
- Host-driven Vates Enterprise: $1,800 per host per year with a 4-host minimum. Illustrative, six hosts is $10,800 per year.
- Storage add-on: XOSTOR runs $800 to $1,200 per host per year. Illustrative, six hosts adds $4,800 to $7,200 per year on top of the base plan.
- Storage in the Proxmox price: the supplied pricing states that all tiers include the same software features, so Ceph and ZFS do not appear as a separate line. Confirm this in the written quote.
Ask each vendor to price your exact host and socket counts, including any CPU upgrade plans that would change the socket count.
When the requirement is 24/7 support, the support tier often decides the model before price does. Proxmox Premium includes unlimited tickets and a 2-hour response at 1,100 euros per socket per year, but the supplied pricing does not state whether that response applies around the clock, so confirm it. Vates Enterprise is the plan that lists 24/7 support, at $1,800 per host per year with a 4-host minimum.
- Proxmox Premium: 1,100 euros per socket per year, unlimited tickets and a 2-hour response.
- Vates Enterprise: $1,800 per host per year, 24/7 support and a 4-host minimum.
- Three hosts with 24/7 needs: Enterprise is not available under its minimum. Confirm what Essential, Essential+ and Pro include before assuming any of them meets the requirement.
- Four-host comparison: illustrative, four single-socket hosts on Premium is 4,400 euros per year. Four hosts on Vates Enterprise is $7,200 per year. The two figures are in different currencies, so convert them at quote time.
- Response terms: ask for severity definitions, response times and the support hours in writing, and whether the entitlement is measured in tickets or in incidents.
Before you compare totals, confirm that the support tier you price includes the hours and response times your operations team requires.
Yearly totals are not fixed after signing. Both models recur annually, so each change to host or socket count, tier or add-on changes the next invoice. Proxmox totals move with each socket you add, while Vates totals move with each host and each add-on. The point where a flat plan stops applying is a planning threshold you should price in advance.
- Socket additions: each new socket adds one annual tier price. Illustrative, one added socket on Standard is 550 euros per year.
- Host additions: Vates Pro adds $1,000 per host per year. Enterprise adds $1,800 per host per year once the cluster meets its 4-host minimum.
- Tier changes: moving a node from Basic to Premium changes that node's annual cost. Confirm whether tiers can differ by node in one cluster.
- Add-on growth: if you use XOSTOR, its $800 to $1,200 per host per year also grows with each host.
- Mid-term changes: confirm proration, minimum terms and whether plan changes take effect only at renewal.
Ask each vendor for the annual total at your target host count in year one and in year three, in writing, so the growth path is visible before you commit.
How to build an apples-to-apples yearly quote
This sequence turns two different pricing models, per-socket Proxmox subscriptions and Vates VMS plans sold as flat tiers or per host, into one yearly figure you can defend. Each step produces a line item or written answer that the other vendor's quote can be checked against.
Inventory hosts, sockets and cores per host
Your infrastructure lead lists every host that will run guests, with its CPU socket count, total core count and whether it will join a cluster or pool. Proxmox counts CPU sockets, so a dual-socket server is two units, while Vates Pro and Enterprise count hosts, so the same server is one unit. Confirm with Proxmox whether any host in your plan is a cluster member that needs its own subscription, and confirm with Vates how it treats hosts in a pool. You know this step is done when every host has a row with sockets, cores, cluster membership and planned role, and nobody is working from memory.
Decide the support response you need
Before reading any price, write down how fast you need a vendor response during an incident and how many tickets you expect in a year. Proxmox publishes four subscription tiers that differ in ticket count and response time, from no support tickets on Community to unlimited tickets with a 2-hour response on Premium. Vates ties support level to its plans, with 24/7 support listed on Enterprise. Ask each vendor to state in writing the response time for a critical outage, the channel used and whether named engineers are included. The output is a one-page requirement that both quotes must meet.
Map each host to a Vates plan or per-host tier
Using your host inventory, work out which Vates VMS option fits. Essential and Essential+ are flat yearly prices for up to 3 hosts, so a 3-host estate and a 2-host estate cost the same on those plans. Pro is priced per host with a 3-host minimum, and Enterprise is priced per host with a 4-host minimum and includes 24/7 support. Calculate the Proxmox side the same way, multiplying the per-socket tier by your socket count. Ask Vates whether the plan covers Xen Orchestra and the hypervisor on every host, and whether hosts added during the year are billed pro rata or at renewal. The output is two candidate totals per vendor, one for each plausible tier.
Add storage and migration tooling to both quotes
Price the storage layer you actually plan to use, because the base subscription is only part of the bill. Proxmox supports Ceph and ZFS natively and includes them in the per-socket subscription, though Ceph enterprise packages depend on the subscription level you buy. XCP-ng storage add-ons such as XOSTOR are sold by Vates at $800 to $1,200 per host per year, according to the Vates pricing page, so add that per host where you need it. Also include the migration path: Xen Orchestra's V2V tool needs HTTP access to the ESXi API and uses warm migration, but ESXi 6.x hosts are not supported for V2V in current versions. Note any backup product you will pay for separately. The output is a list of add-ons with a yearly figure or a written confirmation that the item is included.
Convert euro and dollar figures to one currency
Proxmox publishes its subscription prices in euros and Vates publishes its plans in US dollars. Choose one reporting currency, then record the exchange rate on the day you request the quote and again on the day you intend to purchase. Show both rates in the comparison sheet so finance can see how much of any difference comes from currency movement. Ask each vendor whether invoices are issued in a different currency, whether taxes or withholding apply, and whether the price is fixed in the contract currency for the term. The output is a single-currency table with the rate and date stated beside every converted figure.
Request written quotes that state term and renewal rules
Send each vendor the same written scope: host count by socket or by host, support tier, add-ons, currency and start date. Ask them to state the subscription term, whether it is one or more years, how renewal pricing is set, whether the price can change at renewal, and what happens to support and repository access if you lapse. For Proxmox, confirm the subscription is per CPU socket per year and that the software works without it on the no-subscription repository. For Vates, confirm which plan is annual, what the minimum host count is at renewal, and whether support lapses with the plan. The output is two quotes that match on scope, term and renewal, so the yearly totals can be compared line by line.
Compare totals and confirm open items
Place the two written quotes side by side in your single currency and check that every line matches the scope from the earlier steps. Mark any item that one vendor included and the other left out, and get it priced or confirmed in writing. Record the points still open, such as host growth during the year and renewal increases, and assign an owner to each. The output is a signed-off comparison that shows the yearly total for each vendor, the assumptions behind it and the questions still waiting for answers.
What switching later costs beyond the subscription
The yearly subscription is only one line in the total cost of running either platform, and the larger number often sits in the move itself. Before you compare Proxmox per-socket fees with Vates VMS plans, estimate what it would cost to leave the platform you choose. Moving virtual machines between hypervisors means planning downtime windows, retesting guest drivers and application configurations, and in many cases paying an implementation partner or your own engineers to repeat the work. Ask each vendor and partner for the migration path they support, and whether it is documented for your current hypervisor version. For XCP-ng, the most concrete item is V2V in Xen Orchestra, which performs warm migration: it replicates data while the source VM keeps running, then syncs changed blocks after shutdown. The migration documentation says it needs only HTTP access to the ESXi API, which makes network access and a service account with the right rights the first things to confirm. The same documentation states that ESXi 6.x hosts are not supported by current Xen Orchestra versions for V2V, so an older estate may need an intermediate upgrade before any tool can move its VMs. Confirm your ESXi build against the XCP-ng migration documentation before you size the project. Storage choices on the Proxmox side can change hardware spend more than the subscription does. Proxmox VE supports Ceph RBD, CephFS and ZFS, and high availability needs at least three cluster nodes, shared storage for guests, redundant hardware and watchdog-based fencing. If you plan a hyper-converged Ceph design, price the extra disks, network links and memory per node, and confirm the Ceph release your Proxmox version will run. Whichever platform you pick, write the storage and HA requirements into the quote so that a later change of backend does not become an unbudgeted hardware purchase.
Pricing questions buyers ask before choosing
Can Proxmox VE run in production without a subscription?
Yes. The software can run without a subscription, and Proxmox states that on its pricing page. The decision is a policy one. The enterprise repository requires a valid subscription key and is the recommended repository for production, while the no-subscription repository is described as suited to testing and non-production use. Running production on the free repository is therefore a choice you must make, document and defend to your change board. Ask Proxmox how it views that setup for your environment. Subscriptions add support entitlements, from 3 tickets with a 1 business day response at Basic to unlimited tickets with a 2-hour response at Premium, so weigh that against your own in-house capacity.
Does Vates VMS include support for up to three hosts?
The plan name alone does not confirm it. Vates lists Essential at $2,000 per year and Essential+ at $4,000 per year for up to 3 hosts, so these plans are sized by host count, but the price does not settle which support entitlements come with each one. Ask Vates to confirm the support level, response times and ticket limits for each plan in writing before you rely on it. Vates describes XCP-ng and Xen Orchestra as open-source projects with no license fees, and says commercial support subscriptions add SLAs. Enterprise is the plan described with 24/7 support, at $1,800 per host per year with a 4-host minimum. For a three-host cluster, also confirm what changes if you add a fourth host, since the flat plans are written for up to three.
How are CPU sockets counted per host for Proxmox subscriptions?
Proxmox prices subscriptions per CPU socket per year, so the count follows the physical sockets in each host you subscribe. Illustrative example: a three-node cluster where each node has two sockets needs six socket subscriptions. At Basic, priced at 370 euros per socket per year, that comes to 2,220 euros per year for the cluster. At Premium, at 1,100 euros per socket per year, the same six sockets total 6,600 euros. Confirm with Proxmox how multi-socket hosts, test nodes and cold spares are counted before you size the order. For comparison, Vates Pro is priced at $1,000 per host per year with a 3-host minimum. The currencies differ, so convert both quotes to one currency on the quote date and compare the full yearly totals.
What drives the cost and effort of an implementation partner?
The main drivers are the number of hosts and sites, the storage design, the migration workload, and the integrations you need. Storage choice matters: Proxmox VE can use Ceph and ZFS, and Vates sells XOSTOR hyperconverged storage as an add-on at $800 to $1,200 per host per year. Migration volume and source matter too. Xen Orchestra V2V uses warm migration, but current versions do not support ESXi 6.x hosts for V2V. High availability adds design work, since Proxmox HA needs at least three cluster nodes, shared storage for guests and watchdog-based fencing. Implementation is usually a one-time fixed-scope cost, while support, upgrades and testing retainers recur. Ask any partner for a quote built on written scope that lists deliverables, handover documentation and the recurring services you expect after go-live.
Do I need a consultant to run Proxmox VE or XCP-ng?
Neither platform requires a consultant by license, and both are documented publicly. Whether you need outside help depends on your team's skills and the design you choose. Proxmox HA depends on quorum, shared storage and fencing being designed correctly, and a failed design often shows up only during an outage. XCP-ng adds Xen Orchestra and the XAPI toolstack to the skills your team needs. Check upgrade ownership early: Proxmox versions are supported at least as long as the matching Debian release has security support, roughly 3 years, and XCP-ng 8.3 LTS is supported until November 30, 2028. Many teams run in-house, bring in a partner for the design and hardening, and then keep a retainer for upgrades and support. DeployOpen plans, implements, hardens, backs up, upgrades, documents and supports self-hosted platforms in your own infrastructure, and ongoing support is available as retainers.
How long does a quote take depending on written scope?
No quote turnaround is published, so ask for the timeline in writing against your scope. The scope drives the time: host count, sites, storage design, migration volume, identity and monitoring integrations, and whether you want documentation and a handover. A narrow scope with complete inputs can be quoted faster than a broad one with open questions about hardware, networking or data. DeployOpen does not publish a price list. A quote follows from the written scope, and most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. Send your host inventory, current license position, target storage and the migration source to make the first quote as precise as possible.
Do Proxmox subscription tiers unlock different software features?
No. Proxmox states that all subscription tiers include the same software features, so the tiers differ in support entitlements and access to the enterprise repository. Basic is priced at 370 euros per socket per year with 3 tickets and a 1 business day response. Standard is 550 euros with 10 tickets and a 4-hour response. Premium is 1,100 euros with unlimited tickets and a 2-hour response. Community is 120 euros per socket per year with no support tickets. The software itself can be used without a subscription. When comparing options, decide first whether you need faster ticket response and enterprise repository access, then choose the lowest tier that covers that need. Check the current terms on the Proxmox pricing page before purchase.
When pricing should decide between Proxmox VE and XCP-ng
Pricing should decide the choice when the cluster is small, stable and the feature needs are the same on both platforms. A team running a fixed three-host cluster can compare the two directly: Vates VMS Essential is a flat $2,000 per year for up to 3 hosts, while Proxmox VE is priced per CPU socket per year, at 120 euros for Community and 370 euros for Basic. Proxmox Community includes no support tickets, so the real question is whether a production team needs the Basic tier's ticket allowance and the enterprise repository. Confirm the currency, any tax treatment and whether each plan covers the storage and migration work you need before you treat the two totals as equal.
Socket count and host count move the yearly totals in opposite directions, so the break-even point depends on your hardware. Proxmox VE charges per socket, so a host with two sockets pays twice the per-socket rate, and Premium at 1,100 euros per socket per year grows with every CPU you add. Vates bills Pro at $1,000 per host per year with a 3-host minimum and Enterprise at $1,800 per host per year with a 4-host minimum and 24/7 support, so the cost per host stays the same whether a host carries one socket or several. Build a table with your current host count, sockets per host, expected growth over three years and the support response time you need, then request written quotes from both vendors in one currency. The Vates pricing and support page lists the current plan terms you should check against.
Pricing should stop being the deciding factor when storage or Xen tooling drives the design. Proxmox VE supports local ZFS, Ceph RBD and CephFS, and its high availability needs at least three cluster nodes, shared storage for guests and watchdog-based fencing, so the subscription line is only part of the bill. On XCP-ng, shared hyperconverged storage through XOSTOR is a separate Vates add-on at $800 to $1,200 per host per year, which can change the flat-plan comparison quickly. If you depend on Xen Orchestra and its warm V2V migration from ESXi, confirm your ESXi version first, because the XCP-ng migration documentation states that ESXi 6.x hosts are not supported for V2V. The overall comparison on this page sets out support terms and migration paths side by side, so price the storage and migration path before the license line makes the decision for you.
How DeployOpen helps you compare and implement either platform
DeployOpen is a Chainscore Labs company that plans, implements, hardens and supports self-hosted open-source platforms inside your own infrastructure. For a Proxmox VE vs XCP-ng pricing decision, we help you turn subscription tiers and Vates plan terms into a written scope, a host and socket model, and a handover your team can run.
How we scope
- We confirm host count, socket count per node, and cluster growth so the yearly total is modeled against your real hardware.
- We map which features you need, and whether support response times or the enterprise repository matter for your operations.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before any work starts.
How we build
- We build a side-by-side cost model covering licenses, support tiers, add-ons such as XOSTOR, and hardware for each platform.
- We test migration paths from your current hypervisor, including the VMware import method that fits your ESXi version.
- We document the licensing and repository configuration so your team can see exactly what each option includes.
How we hand over
- You receive written documentation of the chosen platform, subscription setup, cluster or pool layout, and backup configuration.
- We provide a runbook covering upgrade windows, support entitlements, and the steps to add hosts or sockets later.
- Handover includes a review session where your engineers run the procedures themselves before the engagement closes.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped in writing separately from the build.
- Retainers can cover recurring tasks such as applying platform updates, reviewing subscription renewals, and checking host counts after changes.
- Your quote follows from the written scope, so ask for a breakdown of one-time and recurring costs before you commit.
