Vultr Module

Use the Vultr module to convert the live cloud catalogue into sellable products, provision instances with optional paid resources, and give customers safe server, network and storage controls.

Reaching the Screen

Go to Products → Hosting Server → Vultr: {admin}/vultr

Activate the Module Menu

1. Open Products → Hosting Server and click Add New Server below the page title. On a narrow screen, first open Show Options to reach this button.
2. Under Server Automation Module, choose the Virtualization category and then select Vultr.
3. Under Connection Details, enter vultr.com in Address, root in Username, and your Vultr API key in API Key.
4. Click Test Connection. After the test succeeds, check the server name and required capacity fields, then click Add New Server at the bottom of the page.
5. The record is created as active. The Products → Hosting Server → Vultr menu now appears and {admin}/vultr becomes available.

What the Module Does

Catalogue and product control

Each catalogue row combines Vultr hardware, transfer, regional availability and cost with its WISECP product. The administrator controls public name, automatic or pinned region, category, monthly USD sale price and active status. Import adds missing plans, updates stored costs and reconciles regions; it does not replace an existing sale price during cost-only synchronization. New plans are inactive until reviewed.

Customer service tools

Enabled customers can start, stop or restart an instance, reinstall its operating system, open Vultr’s tokenized web console, create/restore/delete snapshots and restore automated backups. Network tools include allow-list firewall rules, reverse DNS, bandwidth and the list of add-on-provisioned reserved IPs. Storage tools mount public ISOs and manage purchased block storage. The overview shows real outbound bandwidth and allocated CPU, RAM, disk and transfer; Vultr exposes no live guest CPU, RAM or disk gauge here.

Automation and lifecycle

Product generation synchronizes operating-system choices, creates hostname, user-data and SSH-key requirements, attaches enabled add-ons and wires plan upgrades. Add-on lifecycle can enable automated backups or DDoS protection and provision block storage, snapshot quota and reserved IP quota. The instance ID links the WISECP service to provider operations, including cancellation cleanup of module-managed billable resources.

Before You Configure It

1. Create a Vultr API token for the provider account or sub-account whose instances, regions, firewall, storage and IP resources WISECP will manage. Keep it server-side and secret.
2. Enable the Vultr server module and create an active server record that will hold the API token.
3. Create and enable USD in WISECP; provider costs and generated prices are USD and import is blocked without it.
4. Confirm the license plus provider quota and billing capacity for an actual test instance and every optional resource you will test.

Settings and Product Controls

Installation and Operation

Prepare the API token

1. Create a dedicated Vultr API token in the account that owns the resources WISECP must manage.
2. Apply any provider-side IP restrictions so the WISECP server can use it, and grant access to every enabled instance, firewall, storage and network operation.
3. Store the token securely; customers never need or receive it.

Connect and test the module

1. On the module page, click the gear-shaped Settings button in the top action bar directly below the page title; on a narrow screen, reveal this bar with Show Options first. In the Module Settings window, enter the token and choose margin, stock behavior, cost synchronization, checkout add-ons and customer features.
2. Use Test Connection directly below the credential field; it can test the typed token before save and is intentionally available without a module license.
3. After the connection succeeds, click Save Settings in the window footer. The page loads live plans and regions.

Import and reconcile plans

1. In the top action bar below the page title, click the cloud-download Import from API button. In the window, select at least one of new plans, cost updates or region import.
2. Click Start Import in the window footer. Missing plans are created inactive with margin-based pricing; cost refresh changes stored cost only.
3. Review the result: invalid pinned regions return to automatic, operating-system choices are synchronized for new products and compatible upgrade paths are rebuilt.

Review regions, products and prices

1. Check plan hardware, transfer, stock and USD cost; choose the public name, fixed/automatic region and category.
2. Set the monthly USD sale price and keep the product inactive until provisioning and cancellation pass.
3. Save rows. If bulk repricing is required, enter the rate in Profit Rate (%) on the right side of the top action bar and click Update Prices; this reprices every imported plan and generated add-on from current cost.

Configure requirements and add-ons

1. Review generated operating-system, hostname, user-data and SSH-key requirements and remove choices that are unsuitable for sale.
2. Enable only backup, DDoS, block-storage, snapshot and reserved-IP options supported by your catalogue; set their prices and quotas.
3. Confirm the selected add-ons are attached to the intended products so ordering and later service tools enforce the purchased limits.

Verify with an inactive test product

1. Create a controlled service from an inactive product using a supported region and operating system; include each paid extra that must be tested.
2. Provision it and confirm instance ID, IP and status; then test power, console, reinstall, snapshot/backup, firewall, reverse DNS and storage tools you enabled.
3. Cancel through WISECP and verify the instance and module-managed extras disappear from Vultr before publishing the product.

Maintain catalogue and lifecycle

1. Import after provider plan, regional availability or cost changes; prefer cost-only synchronization when sale prices are manually curated.
2. Review hidden stock, automatic-region fallbacks and add-on quotas after every catalogue change.
3. Periodically retest a provision/cancel cycle and rotate the token without leaving the server record disconnected.

Things to Watch

Privileges

Product Operations (PRODUCTS_OPERATION) is required for configuration, import and pricing. Customer tools are governed by the module feature switches and purchased add-on quotas.

Related Screens

• Servers
• Product Groups
• Server Modules