Plans & Addons

Create sellable plans and addons, price by region, and prepare for marketplace listing

A plan is what customers buy: vCPU, RAM, disk, price, and the regions where it is offered. Addons are optional extras (extra IPs, backups, snapshot storage) priced separately but linked to compatible plans.

Manage everything at /infrastructure/plans. The page has three tabs:

Tab	Purpose
Plans	Create and price VM plans from NodeRings templates
Addons	Create backup, snapshot, and additional-IP addons
Price Calculator	Estimate customer cost before publishing (testing only)

After infrastructure and IPAM are ready, create plans and matching addons here. Continue with Preflight Check to validate infrastructure before listing.

Billing models

NodeRings supports two plan billing styles. Which one you offer is your business model:

Model	Billing type	How customers pay
Fixed	Subscription	Upfront monthly flat rate (charged in advance)
Usage-based	Usage	Hourly compute charge (in arrears), with a monthly cap on the base compute price

Fixed plans behave like traditional hosting: the customer pays a set monthly price for the VM size.

Usage-based plans bill for the hours the VM runs. The template includes a suggested hourly rate and a monthly cap so usage cannot exceed a predictable maximum on base compute.

Both models can include Bandwidth Egress Gb as a separate usage line (see below). Addon billing must match the parent plan (fixed addons on fixed plans, usage-based addons on usage plans).

Available plans

NodeRings seeds template plans you copy and price. Plan codes follow TIER-CATEGORY-VCPUsC-RAMGB-DISKGB (for example SC-GC-2C-4G-80 = Shared Compute, General Compute, 2 vCPU, 4 GB RAM, 80 GB disk).

Shared Compute, General Compute (sellable today)

Code	vCPU	RAM	Disk	Fixed billing	Usage-based billing
`SC-GC-1C-1G-20`	1	1 GB	20 GB	Monthly subscription	Hourly usage + monthly cap
`SC-GC-1C-2G-40`	1	2 GB	40 GB	Monthly subscription	Hourly usage + monthly cap
`SC-GC-2C-4G-80`	2	4 GB	80 GB	Monthly subscription	Hourly usage + monthly cap
`SC-GC-4C-8G-160`	4	8 GB	160 GB	Monthly subscription	Hourly usage + monthly cap
`SC-GC-8C-16G-320`	8	16 GB	320 GB	Monthly subscription	Hourly usage + monthly cap

Asset type is VM for all rows above.

Coming soon

Additional seeded families exist in the catalog but are not enabled for marketplace selling yet: Dedicated Compute (DC-*, requires dedicated compute nodes) and Shared Compute, High Frequency (SC-HF-*).

Regions

Plans are per region. Create (or copy) the same template plan in each region where you sell. You can set different prices per region if your costs differ by location.

Addons are organization-wide today. They are not per region, but each addon’s billing type must match the plans it attaches to.

Bandwidth Egress Gb

Every plan template includes a Bandwidth Egress Gb price line in addition to base compute:

Field	Meaning
Free units	GB of egress included per month at no charge (template default is often 1000 GB)
Unit amount	Price per GB after the free tier (for example $0.01/GB)
Min / max charge	Optional floor and ceiling on bandwidth charges for the period
Unlimited	Checkbox to disable overage billing and treat egress as unlimited

Traffic beyond free units is metered and charged at the configured unit rate unless Unlimited is enabled. Bandwidth is usage-based on both fixed and usage-based plans.

VM scheduling & bandwidth limits

Plans can optionally cap how much CPU time and network bandwidth a VM gets on the hypervisor. These are set in the VM Scheduling & Bandwidth section of the create/edit plan dialogs and map directly to Proxmox settings:

Field	Default	What it controls
CPU limit	`0` (unlimited)	Maximum CPU time across all cores (Proxmox `cpulimit=`). `2` caps a VM at two full cores of CPU time even if the plan has more vCPUs
CPU units	`1024`	Fair-share scheduling weight (Proxmox `cpuunits=`). Under contention, a VM with `2048` gets twice the CPU time of one with `1024`
Network rate (MB/s)	Unlimited	Bandwidth cap on the primary NIC (Proxmox `rate=`), in megabytes per second. `12.5` MB/s ≈ 100 Mbit/s

Leave the fields empty to keep defaults. Values are snapshotted onto each VM at creation time: editing the plan later only affects newly created VMs, never running ones. Note that the network rate cap is a hypervisor throughput limit and is independent of Bandwidth Egress Gb billing above.

Addons

Addons extend a plan at checkout. Like plans, they come in fixed and usage-based variants.

Addon billing type must match the plan: fixed-price addons on subscription plans, usage-based addons on usage plans. A mismatch is the most common reason the addons_created preflight check fails. See Preflight Check.

Available addons

Addon code	Type	Fixed billing	Usage-based billing
`DAILY-BACKUP`	Backup	30% of plan base price / month	Per GB snapshot storage / month
`WEEKLY-BACKUP`	Backup	20% of plan base price / month	Per GB snapshot storage / month
`SNAPSHOT-STORAGE`	Snapshot	Not available	Per GB snapshot storage / month
`ADDITIONAL-IP`	Additional IPv4 (same prefix as VM primary)	Monthly flat (prorated on add)	Hourly while attached, with monthly cap

Backup addons on fixed plans use a percentage of the plan base price, not a flat dollar amount. Backup addons on usage plans bill by gigabytes of snapshot storage used.

Additional IP addons on fixed plans are a monthly flat fee (prorated when added mid-period). On usage plans they bill per hour the extra IP is attached, with a monthly cap. Extra addresses are allocated from the VM primary IPv4 prefix; Proxmox firewall is updated via the operator. Customers configure the address inside the guest OS themselves.

Create plans and addons

Create a plan

Open the Plans tab → Create Plan. Pick asset type (VM), billing type (fixed or usage-based), region, and template plan. Set currency, base unit amount, and Bandwidth Egress Gb (free units, unit price, min/max, or unlimited).