Plans & WHMCS products

A plan carries a RAM tier, a maxmemory ceiling, and a deployment model (shared or dedicated). Each plan links to a WHMCS product. Replace the seeded examples with your own catalog before you sell anything.

1. How plans map to products

Plans are managed under Addons → ImpulseValkey → Plans & Products. Each plan defines a RAM tier, a maxmemory ceiling, a deployment model, and pricing, and links to a WHMCS product. The deployment-model flag on the plan is what decides how a service is provisioned when a customer orders it:

Model	What it provisions	Provisioning
Dedicated	One Ubuntu 24.04 VPS per customer service, running a native valkey-server under systemd. Full VPS isolation.	Asynchronous — the order queues and a background cron builds and bootstraps the VPS.
Shared	One isolated valkey@svc_N instance (its own systemd unit, TLS port, password, and maxmemory) on an operator-run shared pool box.	Synchronous — the tenant is created over the pool box’s Admin Proxy and is usable the moment the order completes.

2. The seeded example plans

The module seeds a set of example plans on install. Every one is labelled “Example - configure before selling” and carries placeholder names, memory ceilings, and placeholder prices:

Seeded plan	Model	RAM	maxmemory	vCPU
Micro Cache	Shared	64 MB	64 MB	1
Mini Cache	Shared	256 MB	256 MB	1
Cache	Dedicated	512 MB	384 MB	1
Cache Plus	Dedicated	1024 MB	768 MB	1
Pro Cache	Dedicated	2048 MB	1536 MB	2
Business Cache	Dedicated	4096 MB	3072 MB	2

Do not publish the seeded plans as-is

Their names, memory ceilings, and prices (monthly placeholders from $5 to $85, no annual price) are placeholders intended to be replaced. Set your own tiers, ceilings, prices, and provider sizing first. A plan whose name still carries the Example label can’t be synced to WHMCS and can’t provision.

3. Configure a plan you’ll sell

Edit each plan you intend to sell and set:

• a real name,
• the RAM tier and maxmemory ceiling,
• the deployment model (shared or dedicated),
• the provider sizing (which VPS size a dedicated plan builds), and
• pricing.

Then deactivate or hide any example plans you are not selling so they don’t appear on order forms.

4. Link a WHMCS product

Sync each plan to WHMCS from the plan editor with Save & Sync Product (or Sync / Sync All on the plan list). Sync creates the plan’s WHMCS product — named ImpulseValkey plus the plan name, in a Cache product group — or updates the one it already linked. It sets the product’s module to ImpulseValkey (impulsevalkey) with the plan selected, writes the plan’s monthly and annual prices for every currency, and hides and retires the product while the plan is inactive.

To attach a product you created yourself instead:

1. Set the product’s module to ImpulseValkey (impulsevalkey).
2. Pick the matching plan in the product’s Plan config option dropdown.

Only sellable plans appear

The product’s Plan dropdown only lists plans that are active, linked to a WHMCS product, and able to provision — so sync a plan to a product before it becomes selectable.

5. Confirm the sync, then test an order

Run Diagnostics → Health Checks → WHMCS Product Sync to confirm every synced plan still points at an existing WHMCS product using the module. Then place a test order:

• A dedicated order provisions asynchronously via the provisioning cron (every 2 minutes).
• A shared order provisions synchronously and is usable immediately.

Open the service in the client area to reveal the connection string and connect a client.

Plan-change boundaries

A plan change within the same deployment model applies the new plan’s maxmemory ceiling to the running instance. On a dedicated service the server itself is not resized, and the change also rotates the cache password — the previous one keeps working for the rotation grace window. Moving a service between shared and dedicated is not an in-place change: the module refuses it, and WHMCS records the module’s error. That’s a migration: order the new plan and move the data across.

Changing a plan’s maxmemory later doesn’t touch services already on it: the save notice says how many live services still run the old limit, and the plan editor’s Live Services — Out-of-Sync Limits panel applies the new one.