Vultr Bare Metal Module

Use Vultr Bare Metal to import dedicated hardware plans, automate physical-server ordering and lifecycle control, and sell reserved-IP capacity without presenting unsupported cloud features.

Reaching the Screen

Go to Products → Hosting Server → Vultr Bare Metal: {admin}/vultrbaremetal

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 Dedicated category and then select Vultr Bare Metal.
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 Bare Metal menu now appears and {admin}/vultrbaremetal becomes available.

What the Module Does

Catalogue and product control

The grid joins Vultr bare-metal specifications and deployable regions to the WISECP product. The public name, automatic or fixed region, category, monthly USD sale price and status are editable. Import adds missing plans, refreshes stored costs and resets a removed pinned region to automatic without changing existing sale prices. New products remain inactive for verification.

Customer service tools

Customers can start, stop and restart hardware, reinstall a supported operating system, open Vultr’s tokenized bare-metal VNC console, set IPv4 reverse DNS, view outbound bandwidth and inspect reserved IPs created through the add-on. The overview includes server identity, hardware, OS, location, allocated CPU/RAM/disk/traffic and real bandwidth. Bare metal has no live guest CPU, RAM or disk usage in this module.

Automation and lifecycle

Generated products receive operating-system, hostname, user-data and SSH-key requirements and optional reserved-IP quota. The module does not claim cloud-only snapshot, backup, block-storage or firewall management for bare metal. Provider server ID is the lifecycle relationship used for service actions and cancellation cleanup.

Before You Configure It

1. Create a Vultr API token in the account that owns the bare-metal capacity and reserved IP resources WISECP will manage; allow the WISECP server through provider-side API restrictions.
2. Enable VultrBareMetal and create an active server record containing that token.
3. Create and enable USD in WISECP. Plan cost, generated sale prices and add-on pricing use USD.
4. Confirm bare-metal availability, account quota, billing capacity and the module license before testing; physical inventory can be region-specific.

Settings and Product Controls

Installation and Operation

Prepare the API token

1. Create a dedicated Vultr token under the account that will own WISECP bare-metal servers.
2. Grant access to bare-metal, region and reserved-IP operations and allow the WISECP server if an API IP allow-list is enabled.
3. Store the token privately; it is an administrator credential and is never required by customers.

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, set margin, stock and cost-sync behavior, choose customer features and decide whether to sell reserved IPs.
2. Use Test Connection directly below the credential field; this diagnostic test is available even when the commercial license is not active.
3. After success, click Save Settings in the window footer. Live bare-metal plans and regions become available.

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 new plans, cost updates or region import.
2. Click Start Import in the window footer. New plans are inactive and margin-priced; cost updates do not overwrite sale prices.
3. Review invalid-region resets, synchronized operating-system choices and rebuilt plan upgrade paths.

Review plans, regions and pricing

1. Check fixed hardware, traffic, deployment availability and USD cost for each row; select public name, category and automatic/fixed region.
2. Set the monthly sale price and keep the product inactive until a real test order is fully cancelled.
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 recalculates all imported plan and reserved-IP prices.

Configure requirements and reserved IPs

1. Review operating-system, hostname, user-data and SSH-key requirements and keep only supported installation choices.
2. If reserved IPs will be sold, enable the order step and define a price and quota that match provider availability.
3. Confirm the generated add-on is attached to the intended bare-metal products; no cloud-only add-ons should be expected.

Verify with an inactive test product

1. Create a controlled service from an inactive plan in a region with confirmed stock and use a supported operating system.
2. Provision it, verify provider server ID/IP, and test power, VNC, reinstall, IPv4 reverse DNS, bandwidth and reserved-IP behavior.
3. Cancel from WISECP and confirm the physical server and module-managed reserved IPs are released before activation.

Maintain availability and lifecycle

1. Import after Vultr changes hardware plans, costs or regional stock; use cost-only updates to preserve curated sale prices.
2. Review fixed regions and hidden-stock behavior because bare-metal capacity can disappear independently by location.
3. Periodically test credentials and cancellation cleanup so scarce billable resources are not left allocated.

Things to Watch

Privileges

Product Operations (PRODUCTS_OPERATION) is required for settings, import and pricing. Customer tools remain limited to the supported features enabled for the module.

Related Screens

• Servers
• Product Groups
• Server Modules