Protect the Hypervisor. Identify the VPS.

Frabs Hypervisor is the existing Frabs product for VPS providers. A sensor on each eligible physical hypervisor node observes guest network and resource signals from the host and links them to supported VM or container inventory.

Start Free TrialCompare Licence Pricing

Existing Product · Beta

Frabs Hypervisor continues the current platform. Expanded monitoring shown here is clearly marked as planned.

Compare All Plans

How It Works

The sensor stays on the node

Frabs works at the virtual network boundary. It does not enter guest operating systems, install a VPS agent or inspect guest files. The host's platform inventory provides the workload identity where available.

  1. Install on the physical node

    One Hypervisor licence covers one dedicated or bare-metal hypervisor node and its workloads, not each individual VPS.

  2. Observe host-side signals

    The current sensor reads guest-facing network interfaces and supported host resource metrics. No guest login or customer filesystem access is required.

  3. Attribute through inventory

    Supported platform adapters map interfaces and addresses to a VM or container. Missing or ambiguous mappings must remain unattributed rather than guessed.

  4. Create evidence and apply policy

    Current outbound-abuse and resource-protection paths feed incidents and provider-configured actions. A detection is reported separately from a rule or action confirmed to have stopped it.

Conceptual Protection Path
  1. Physical nodeDedicated or bare-metal hypervisor
  2. Host-side signalsGuest interfaces and platform inventory
  3. Current protectionOutbound abuse and resource detection
  4. Provider responseIncident evidence and configured policy

Illustrates the intended data path. It does not show live telemetry or prove a mitigation outcome.

Current and Planned Protection

What Frabs Hypervisor Covers

The status beside each capability separates the existing beta from the expansion still to be built.

Outbound network abuse
Available in the existing platform: guest-attributed outbound abuse signals, supporting evidence and provider-configured response where the host setup supports it.
In Beta
Resource abuse protection
Available in the existing platform: host-observed resource-abuse detection and supported controls. High resource use by itself is not proof of abuse.
In Beta
Platform discovery and incident evidence
Available through existing adapters for supported KVM, Linux container and Xen environments. Interface and identity coverage depends on the node and platform version; unsupported mappings are not guessed.
In Beta
Inbound attacks and per-VPS network history
Planned expansion includes inbound flood/scan detection and broader per-VPS traffic, protocol, port and connection history where telemetry can attribute it reliably.
Planned
Node and per-VPS resources
Planned expansion includes fuller CPU, memory, disk, network and capacity history, plus noisy-neighbour signals that distinguish high use from harmful node pressure.
Planned
Infrastructure and enforcement health
Planned visibility includes physical interfaces, bridge and storage health, firewall rule state, mitigation expiry, telemetry freshness and failed actions. It must preserve other managers' rules.
Planned
Customer read-only reports
A provider-controlled dashboard and customer access model are future work. No customer-facing Hypervisor protection portal is represented as currently available.
Planned

Installation and Data Boundaries

Physical Hosts Only. No Guest or Customer Content.

All three Frabs plans are installed on eligible dedicated or bare-metal physical servers. Frabs uses permitted host and network metadata for the licensed product.

  • Install on the dedicated or bare-metal physical hypervisor node only; never inside a customer VPS.
  • No guest agents, guest logins, customer file access or inspection of private content.
  • VM and container attribution is limited to identities the installed platform adapter can verify.
  • Existing customer licences, protection settings, thresholds and commercial terms remain unchanged.

Integrations

Existing Virtualisation Support

These existing discovery adapters identify workloads from the physical node. Coverage depends on the host, network topology and platform version.

KVM / QEMUFull virtual machines, read from each VPS's interface on the node.
Linux ContainersLXC, LXD, Incus and OpenVZ, read from each container's veth or venet.
XenXen and XCP-ng guests, read from each guest's vif interface.

Existing Billing, Alert and Support Connectors

WHMCSBillingBlestaBillingHostBillBillingWISECPBillingFOSSBillingBillingPaymenterBillingHostFactBillingBILLmanagerBillingUbersmithBillingCustom BillingBillingSlackAlertsDiscordAlertsMicrosoft TeamsAlertsTelegramAlertsPagerDutyAlertsOpsgenieAlertsWebhookAlertsZendeskHelp DesksFreshdeskHelp DesksSupportPalHelp Desks

Monthly USD Pricing

Licence Pricing, Without Leaving This Page

One licence covers one hypervisor node. All three products install on dedicated or bare-metal physical hardware; none installs inside a VPS.

Frabs Hypervisor

In Beta

For VPS providers and virtualisation infrastructure.
Installed on dedicated or bare-metal hardware.

$17.00/ month

For one eligible hypervisor node. Never install on a VPS.

Sign Up

Existing licence terms stay unchanged.

  • Outbound network abuse detection
  • Resource abuse protection
  • VM and container attribution where supported
  • One node licence covers its VPS workloads

Monthly Rate per Active Licence

The rate for each eligible licence follows its product's four published volume bands.

Frabs Hypervisor monthly retail rates per licence
Active LicencesPer Licence / Month
1$17.00
2–5$15.00
6–19$13.00
20+$11.00

Four tiers only. The 20+ rate is the final tier; no extra discounts are published above it.

Minimum-charge calculations and mixed-product tier counting are not finalized. These upcoming rates do not change an existing subscription. Applicable tax is additional.

The Sign Up button uses the existing registration flow. Existing customer prices, licences, protection settings and beta terms remain unchanged.

Frabs Hypervisor Questions

What does one licence cover?
One eligible dedicated or bare-metal physical server: a standalone server for Server, a hosting server for Host, or a hypervisor node for Hypervisor. A Hypervisor licence covers the node and its supported VPS workloads; it is not charged per individual VPS.
Will my existing licence change?
Your current protection, subscription price, beta expiry and node allowance remain unchanged. Frabs Hypervisor is the continuation of the existing hypervisor-focused product.