HostHatch

Platform

Products

name: Compute VMs; category: self_managed_full_root_nvme_virtual_machine; current orderability: The current public product catalog links to the active cloud signup/deployment portal and says these VMs can be deployed in 16 edge locations. The production plan objects name 16 locations for every compute size. The authenticated products API exposes live stock booleans but returns HTTP 401 without a customer token, so this record captures current public plan availability rather than claiming an anonymous live-stock snapshot.; service model: No-frills, customer-managed IaaS with full root-level access, provider Linux templates, customer ISO upload, control-panel lifecycle operations and optional networking features.; hardware: AMD EPYC compute on Dell EMC servers, DDR4 RAM and local Samsung enterprise NVMe storage in RAID10; the exact host CPU model is not guaranteed by the public catalog.; plans: name: NVMe 2 GB; monthly usd: 4; vcpu: 1; cpu detail: 1 AMD EPYC core, fair share; memory gib: 2; storage gb: 10; transfer tb: 1, name: NVMe 4 GB; monthly usd: 6; vcpu: 2; cpu detail: 2 AMD EPYC cores, fair share; memory gib: 4; storage gb: 20; transfer tb: 1, name: NVMe 8 GB; monthly usd: 9; vcpu: 2; cpu detail: 2 AMD EPYC cores, fair share; memory gib: 8; storage gb: 35; transfer tb: 2, name: NVMe 12 GB; monthly usd: 12; vcpu: 4; cpu detail: 1 dedicated and 3 fair-shared AMD EPYC cores; memory gib: 12; storage gb: 50; transfer tb: 3, name: NVMe 16 GB; monthly usd: 15; vcpu: 4; cpu detail: 2 dedicated and 2 fair-shared AMD EPYC cores; memory gib: 16; storage gb: 75; transfer tb: 4, name: NVMe 24 GB; monthly usd: 22; vcpu: 6; cpu detail: 2 dedicated and 4 fair-shared AMD EPYC cores; memory gib: 24; storage gb: 100; transfer tb: 6, name: NVMe 32 GB; monthly usd: 29; vcpu: 8; cpu detail: 3 dedicated and 5 fair-shared AMD EPYC cores; memory gib: 32; storage gb: 125; transfer tb: 8, name: NVMe 48 GB; monthly usd: 39; vcpu: 8; cpu detail: 4 dedicated and 4 fair-shared AMD EPYC cores; memory gib: 48; storage gb: 150; transfer tb: 12, name: NVMe 64 GB; monthly usd: 49; vcpu: 12; cpu detail: 6 dedicated and 6 fair-shared AMD EPYC cores; memory gib: 64; storage gb: 200; transfer tb: 15, name: NVMe 96 GB; monthly usd: 69; vcpu: 16; cpu detail: 8 dedicated and 8 fair-shared AMD EPYC cores; memory gib: 96; storage gb: 250; transfer tb: 20; network: The product and feature pages advertise high-speed public/private networking, routed IPv6 and one public IPv4. Included transfer is counted in both directions; Asia-Pacific transfer reductions do not affect this directory's EU/US benchmarks.; location boundary: The production plan objects explicitly include Amsterdam, Stockholm, Vienna, Warsaw, Madrid, Milan, Oslo, London, Zurich, Chicago, Los Angeles, New York and four Asia-Pacific cities. Only the six EU-member-state cities and three US cities are retained here. The older documentation matrix omits Warsaw, Madrid and Milan and includes Seoul, while the production plan objects do the reverse; product-specific production data controls current benchmark attribution., name: Storage VMs; category: self_managed_full_root_high_capacity_hdd_virtual_machine; current orderability: The current public product catalog presents eight fixed monthly storage sizes and links to the active cloud signup/deployment portal.; service model: Customer-managed VM intended for bulk storage and backups, using large enterprise spinning disks rather than the compute range's local NVMe.; plans: name: Storage 1TB; monthly usd: 5; vcpu: 1; memory gib: 1; storage gb: 1000; transfer tb: 2.5, name: Storage 2TB; monthly usd: 9; vcpu: 1; memory gib: 1; storage gb: 2000; transfer tb: 5, name: Storage 3TB; monthly usd: 12; vcpu: 1; memory gib: 2; storage gb: 3000; transfer tb: 7.5, name: Storage 4TB; monthly usd: 16; vcpu: 2; memory gib: 2; storage gb: 4000; transfer tb: 10, name: Storage 5TB; monthly usd: 20; vcpu: 2; memory gib: 2; storage gb: 5000; transfer tb: 12.5, name: Storage 6TB; monthly usd: 24; vcpu: 2; memory gib: 2; storage gb: 6000; transfer tb: 15, name: Storage 8TB; monthly usd: 32; vcpu: 2; memory gib: 2; storage gb: 8000; transfer tb: 20, name: Storage 10TB; monthly usd: 38; vcpu: 2; memory gib: 2; storage gb: 10000; transfer tb: 25; location boundary: The current production plan objects attach all eight storage sizes to Amsterdam, Stockholm, Los Angeles and Chicago. An older documentation matrix and the category copy say eight locations, but the product-specific objects expose only these four; the narrower product-specific matrix controls.

Operating systems

current public statement: Pre-built cloud templates for major Linux distributions plus customer ISO upload.; documented api example images: AlmaLinux 8, Ubuntu 22.04, CentOS 7, CentOS Stream 8, Debian 11, Debian 10, Ubuntu 20.04, Ubuntu 18.04; newer documented guest families: Debian 12 and newer, Ubuntu 22.04 and newer, RHEL-compatible CentOS or AlmaLinux 9; catalog boundary: The exact current product image array is returned only by the authenticated products API. The list above is the official API example, not represented as an exhaustive July 2026 live catalog. Current networking documentation demonstrates newer supported guest families but does not say every mentioned release is a deployment template.; custom iso: Peregrine exposes customer ISO upload, mount/unmount and installation workflows.; windows: No current bundled Windows image or license was found; a customer-supplied ISO is not treated as a provider-supported Windows catalog.

Virtualization

platform: Full-control virtual machines with root access, provider images, custom ISO upload, console and lifecycle/network management through HostHatch's Peregrine portal.; hypervisor: not_found; hypervisor boundary: No current first-party product, documentation, portal or legal source inspected names KVM, QEMU, VMware, Hyper-V or another hypervisor. Full VM behavior is verified, but the hypervisor is not inferred from VirtIO-like functionality or third-party listings.; nested virtualization: not_found

CPU isolation

compute 2 to 8 gib: All advertised cores are explicitly fair share; directory classification shared.; compute 12 to 96 gib: Each plan explicitly mixes a stated number of dedicated cores with fair-shared cores. The directory uses guaranteed as the closest non-overclaiming classification because dedicated would falsely describe the plan's full advertised vCPU count; the exact dedicated/shared split is preserved plan by plan.; storage vm: The public storage plan objects state only vCPU counts and do not disclose contention, reservation or dedicated-core semantics; directory classification not_found.; processor: AMD EPYC for compute. The API documentation example calls the smallest plan's core AMD EPYC Milan, while the current public product catalog promises only the broader EPYC family.

Features

• App installation method: Manual installation with full root access on provider Linux templates or a customer-uploaded ISO.; one click application catalog: not_found; control panel or managed stack: not_found; boundary: References to running Kubernetes clusters or load balancers describe software the customer can operate inside VMs; they are not one-click or provider-managed integrations.
  ✓
• Templates & images provider images: Major Linux distribution templates; the official API example enumerates documented image identifiers.; custom media: Customer ISO upload and server image mount/unmount are exposed in Peregrine.; snapshots: Live portal controls capture, restore, delete and deploy a server from a snapshot. Snapshots survive deletion of the source VM.; snapshot limitations: The portal labels snapshots beta and available only in select locations. Self-service restore is limited to the capture location; cross-location restore requires support.; automated backup boundary: The public features page still labels daily/weekly/monthly backups an upcoming feature with a May 2023 ETA and a proposed 20% VM-price charge. No current portal entitlement or product-specific backup option was verified, so automated backup is not represented as currently offered.
  ✓
• Network orchestration public network: One public IPv4 is described by the API deployment model; public links are advertised at 40 GbE in most documented in-scope facilities and 100 GbE in Los Angeles, without a per-VM throughput guarantee.; ipv6: Optional statically configured routed /64 per VM. Provider templates use cloud-init when IPv6 is selected at creation; later enablement or ISO installs require manual guest configuration.; private networking: Optional second interface among the customer's VMs in the same location, isolated with a unique VLAN/VXLAN, unlimited/unmetered on the private link, customer-addressed and supporting MTU 9000. At least two active same-location VMs are required.; bgp byoip: Support-enabled BGP/BYOIP is documented as under active development and not available in every location; customers must arrange enablement with support.; address management: Portal lifecycle controls include IPv4/IPv6 details, reverse DNS, bandwidth usage and one-off extra-bandwidth invoices. Additional IPv4 is an API product feature, but its current anonymous price and quota are not published.; automation: Peregrine portal and REST API. Public API access is currently limited to selected users and requires a bearer token; documented operations include product discovery, deploy, power state, upgrade, cancel and SSH keys.; bandwidth policy: Inbound and outbound traffic both count. Counters reset on the first day of each calendar month. The terms say excess causes a 5 Mbit/s rate limit and support-sold additional transfer costs USD 4/TB; the current portal also exposes a generated one-off bandwidth invoice without publishing its anonymous step prices.
  ✓
• Firewall
  —
• Load balancer
  —
• DNS management scope: Reverse DNS only.; reverse dns: Peregrine exposes self-service PTR editing for eligible IPv4 addresses and IPv6 addresses/subnets.; authoritative forward dns: not_found; limitations: No customer authoritative-zone service, record catalog, DNSSEC workflow or public DNS API was found.
  ✓
• Git integrations
  —
• Container registry
  —