Frazer
Start building
Serversfrazer.ai

Real servers, not virtual ones.
Every part inspected and on record.

Frazer runs your clusters, VMs and devboxes on physical machines with local NVMe and a private network between them. Each server is inventoried down to its disks, TPM and firmware, tested before it takes work, and watched every 30 seconds after.

Add a serverRead the docs
The hardware of one server, as Frazer inventoried itproduct UI, demo organization
01 · Inside a serverFig. 1

Every part has a job.
Here is what Frazer uses it for.

Fig. 1A server that hosts VMs, seen from above
02 · Requirements

What a server needs.
By the role it plays.

A dedicated node is a whole server for one cluster. A host runs the VMs of many clusters and devboxes in your organization. The agent checks each line and fills in the site’s checklist.

Minimum requirements by role
RequirementDedicated nodeHost for VMsGPU server
CPUx86-64-v2, 8 coresx86-64-v3, VT-x or AMD-V and an IOMMU, 32 cores or moreAs a host, plus Above-4G decoding
Memory32 GB (16 GB for a trial)128 GB or moreAt least twice the total GPU memory
Disks240 GB or more SSD to boot; NVMe for dataTwo mirrored boot disks, plus NVMe for VM disksNVMe scratch
Network1 GbE; 10 or 25 GbE recommendedTwo 10 or 25 GbE ports, bonded, with VLAN taggingInfiniBand or RoCE for multi-node training
BMCOptionalStrongly recommendedStrongly recommended
TPM 2.0 and UEFI Secure BootRecommendedRecommended; required on Frazer serversRecommended
EgressTCP 443 and UDP 51820 (or 443 only), NTP, DNSThe same, plus L2 between hostsThe same
03 · ChecksFig. 2

Tested before work.
Watched while it works.

Fig. 2From accepted to available, and what happens when a check fails
04 · What you get

Machines you can name.
Sizes you can trust.

  • Physical cores, counted honestly

    Fees and capacity count physical cores. Hyperthreads never count.

  • Memory never overcommitted

    VMs get the memory they ask for. CPU overcommit is stated on each size, never hidden.

  • Local NVMe

    VM disks and local volumes on the server’s own NVMe, encrypted with a per-server key.

  • A private network

    Servers in a site talk over private L2: vRack, vSwitch or your own switches.

  • Identity in the TPM

    The machine key is made on the server and sealed in TPM 2.0 when there is one. It never leaves.

  • Firmware on a baseline

    Firmware is read at inspection and compared with a baseline; an update is a typed operation.

  • Ubuntu 26.04 and Kubernetes

    The host OS Frazer installs on servers you bring, updated in your maintenance window.

  • Frazer OS

    Immutable, A/B updates and measured boot, on servers from Frazer and servers with a BMC. One build as ISO, USB image, iPXE and qcow2.

05 · Controls

Your server, your window.
No shell unless you open one.

Who may do what

Servers admin
Adds servers and sets pools, labels and the maintenance window.
Org admin
Confirms a wipe, a reinstall, a firmware update or a BMC action.
Org admin, per server
Turns on a remote shell for a set time, recorded, with you notified. It is off by default.
Frazer
Reads inventory, health and metrics; installs and upgrades in your window; never reads workload data.

What is logged

  • Inventory at inspection, then read again every day
  • Burn-in results, kept on the server’s page
  • Every condition change and every repair step
  • Every typed operation, with its approval and its result

At the cap

  • Critical condition: the server leaves the schedulable set until it recovers
  • Silent agent: lost after 5 minutes, failed after 24 hours
  • Repairs: one server, or 10 %, per pool at a time
  • Reboots: in your maintenance window, rate-limited per pool
06 · Pricing

Per physical core.
Hyperthreads never count.

A server you bring pays a management fee per physical core while it is accepted, with a floor and a ceiling per server. GPUs pay per GPU. Inspection, burn-in and health checks are included.

See every price
CPU$1.50 per physical core / month · min $15, max $150 per server · first server ≤ 16 cores free
GPUs$49 per data-center GPU / month · $19 workstation GPU
IncludedInspection, burn-in, health checks, wipe certificates
Questions

Real hardware, answered.

Which CPUs work?

x86-64. A dedicated node needs x86-64-v2 with 8 cores. A server that hosts VMs needs x86-64-v3 with VT-x or AMD-V, an IOMMU and 32 cores or more.

Do I need a BMC?

No. It is optional for a dedicated node and strongly recommended for a server that hosts VMs. With a BMC, a Site Gateway in your site lets Frazer install the server, set its firmware and power-cycle it with nobody on site.

Why real hardware and not cloud VMs?

Because you know what you get: local NVMe instead of a virtual disk of unknown speed, a private network between servers, memory that is never overcommitted, and a fee per physical core of a machine you can name.

What does burn-in test?

CPU, memory, disk and network under stress, with a benchmark score. GPU servers add GPU diagnostics, a GPU stress test, NCCL and InfiniBand bandwidth tests. It is mandatory on Frazer servers and optional on yours.

Are my disks encrypted?

Every data disk Frazer formats uses LUKS2, with a per-server key sealed to the TPM and kept in your infrastructure project’s Frazer Secrets namespace. A wipe destroys the key first.

Can I use my GPUs?

Yes. Frazer detects them at inspection (model, NVLink, PCIe topology, IOMMU groups, ECC, MIG support) and passes them whole into VMs. MIG and time-slicing stay inside one project’s VM.

More in Servers

Bring real servers.
We check every part.

Add a serverRead the docs