Closed beta General availability Q1 2027. Request beta access →
IZT Cloud CLOUD FABRIC
See pricing Start free
Comparison

Fabric vs Scale Computing

Scale Computing made edge HCI simple and reliable, and it is the platform we respect most in that segment. It also meters per core, sells a cut-down Standard tier, caps cluster size and ships no tenancy or SDN. Fabric was built for the same edge sites with those four constraints removed.

Comparing Fabric with Scale Computing SC//Platform (HyperCore) (Scale Computing). Updated 2026-09-03. Fabric is in closed beta today. General availability is planned for Q1 2027. Competitor facts are drawn from public documentation and published or verified pricing; corrections welcome.

The short version
  • Scale licenses per core, channel-only, in Standard and Professional tiers; Standard drops replication, snapshot scheduling, GPU and affinity. Fabric has one edition per node class.
  • Scale’s storage is a fixed two-copy mirror with no tiering policy; Fabric storage policies set copies, tiers, failure domain and QoS per disk.
  • Scale has snapshots, replication and a local witness today; Fabric’s are roadmap items. Fabric has multitenancy and per-tenant SDN today; Scale has neither.
Pricing at a glance

One dual-socket server, 32 physical cores, fully loaded with VMs (annual, list unless noted)

Fabric — Medium class
$1,800/ node / yr

Fabric Medium class: $1,800 per node per year; Edge class $500 for ≤8-core boxes, the size Scale most often sells.

Scale Computing
~$6,400 / node / yr

Model: Per physical core, subscription (1/3/5 years), channel-only; Standard vs Professional tiers, Fleet Manager licensed separately per cluster.

Basis: verified 5-year street rate of ~$201/core from reseller catalogs and a transacted public-sector contract, 32 cores, August 2026.

Dimension by dimension

Fabric vs Scale Computing, honestly scored.

Where Scale Computing is ahead we say so. Roadmap items are labelled and count against Fabric until they ship.

7 Fabric 2 Scale Computing 5 Even 14 dimensions · roadmap items count against Fabric until they ship
Fabric compared with Scale Computing, dimension by dimension
DimensionFabricScale ComputingEdge
Licensing model Per physical node by node class (five core bands: ≤8 / 9–16 / 17–32 / 33–64 / 65+), every feature in every class, free unlimited Community edition. No per-core meter, no feature matrix.Per core, subscription, channel-only. Standard is the cut-down tier; Fleet Manager is a separate per-cluster licence.Fabric
What you install One signed firmware image per node plus a control-plane appliance you host; nodes have no inbound ports.HyperCore, a single-image appliance OS with a built-in HTML5 UI — genuinely simple, with management inside the cluster.Even
Storage Distributed block storage pooled across every node, driven by storage policies: ordered device tiers, copies and minimum copies, host- or rack-level failure domains, per-disk IOPS/bandwidth QoS and inline compression with in-place re-pack. No SAN and no storage licence.SCRIBE: a fixed two-copy mirror across the cluster with automatic tiering between flash and disk. No policy per disk, no adjustable replica count or rack domain.Fabric
Networking Per-tenant SDN in the platform: overlay or VLAN-backed virtual networks, dual-stack IPv4/IPv6, built-in DHCP/DNS, micro-segmentation policies, distributed stateless gateways and ARP or BGP announcement of public prefixes. Not a separate SDN licence.VLAN tagging on virtual NICs. No overlay SDN, no tenant DHCP/DNS, no micro-segmentation.Fabric
High availability Acknowledged 10-second heartbeats, a liveness verdict in about 20 seconds, and no restart elsewhere until the failed node is verifiably fenced — powered off through its own BMC and blocked at the storage layer.Automatic VM restart on node failure; a local witness for two-node edge sites.Even
Live migration Live migration; hibernate and resume on any node.Live migration within the cluster.Even
Updates and lifecycle One signed A/B firmware image per node carries the hypervisor, storage, networking and agent. A rolling update evacuates each node by live migration, flips its image slot and rolls back automatically if it does not come up healthy.Rolling, non-disruptive HyperCore updates — one of its best features.Even
Multitenancy Built in. Tenants, quotas, isolated per-tenant networks with their own DHCP/DNS, and a tenant self-service portal with browser consoles — the same product an MSP bills monthly per node.None. One organisation per cluster; role-based users on the same UI.Fabric
Snapshots and DRRoadmap Snapshots and cross-site replication are on the roadmap and will be in every class.Scheduled snapshots and cross-cluster replication built in — but only in the Professional tier.Scale Computing
Cluster size One node to many racks in one fabric; rack-aware placement kicks in automatically at three racks.Eight nodes per cluster; larger estates are many clusters under Fleet Manager.Fabric
Air-gapped operation Designed for it: local sign-in (password, TOTP, passkeys — never an emailed link), a control plane on your own appliance, signed updates imported and verified on site, no phone-home, no kill-switch.Clusters run offline; Fleet Manager is a cloud service.Fabric
Hardware Bring your own commodity x86-64 servers, any drive mix.Scale-supplied appliances or a short list of certified platforms; hardware is part of the deal.Fabric
Fleet managementRoadmap Multi-fabric Global view is planned; today each fabric is managed from its own appliance.Fleet Manager (cloud) for many clusters — mature, separately licensed.Scale Computing
Guest monitoring One-second VM telemetry and guest inventory from the guest agent, in the portal and over Prometheus.AIME autonomous monitoring with guest-level insight.Even
Who should pick which

Choose Fabric if… Choose Scale Computing if…

Fabric is the better fit for

  • Retail, branch and industrial edge that wants per-node pricing on its own hardware
  • Operators who need tenancy or per-tenant networks at the edge
  • Sites that outgrow an eight-node cluster
  • Air-gapped estates that cannot use a cloud fleet manager

Scale Computing is the better fit for

  • Buyers who want hardware and software from one vendor with one support number
  • Sites that need snapshots and replication today
  • Very large multi-cluster fleets managed centrally

Moving from Scale Computing to Fabric

HyperCore exports VMs as standard disk images; Fabric imports them as volumes. Because Fabric runs on commodity servers, the Scale appliances can stay in place until their term ends while new sites deploy on Fabric.

See migration use cases
FAQ

Fabric vs Scale Computing: common questions

Scale licenses per core through resellers; a verified 5-year street rate of about $201 per core makes a 32-core node roughly $6,400 per year. Fabric’s Medium class is $1,800 per node per year, and its Edge class is $500 for boxes of eight cores or fewer.

More comparisons

How Fabric stacks up against the rest.

Fabric vs VMware VMware vSphere and VMware Cloud Foundation (VCF)Fabric vs Proxmox Proxmox Virtual Environment (Proxmox VE)Fabric vs Nutanix Nutanix Cloud Infrastructure (NCI) with the AHV hypervisorFabric vs VergeIO VergeOS by VergeIOFabric vs Harvester Harvester HCI (SUSE Virtualization)Fabric vs Azure Local Microsoft Hyper-V and Azure Local (formerly Azure Stack HCI)Fabric vs XCP-ng XCP-ng with Xen Orchestra (Vates) All comparisons → Methodology and the full list

Try the whole platform free.

Community is unlimited nodes, every feature, forever. Move to a paid class when you want the production update channel and a support contract.