Hostman

Platform

Products

name: Cloud Servers / VPS / VDS; category: self_managed_full_root_kvm_qemu_cloud_virtual_machine; service model: On-demand VM with root-password or SSH-key access, web console, project organization, lifecycle/reinstall/resize controls, cloud-init and optional networking/data-protection services. Hostman's VPS and VDS landing pages resolve to the same current Cloud Server tariff family rather than separate benchmark products.; resource model: Hostman calls CPU, RAM and NVMe resources guaranteed. Every live tariff object marks is_dedicated_cpu false, so the directory records guaranteed virtual allocation and does not call these dedicated physical cores.; hardware: Current marketing names Intel Xeon Gold and AMD EPYC hosts, enterprise Supermicro/Dell/SuperCloud hardware, NVMe and a 200 Mbit/s port. Live tariff objects advertise 3.3 GHz in Amsterdam, Frankfurt and San Jose and 3.0 GHz in New York; the exact host CPU model is not promised per VM.; plans: name: 1 vCPU / 1 GiB / 25 GB; base private only monthly usd: 2; public ipv4 monthly usd: 2; public server monthly usd: 4; vcpu: 1; memory gib: 1; storage gb: 25; port mbps: 200, name: 1 vCPU / 2 GiB / 40 GB; base private only monthly usd: 3; public ipv4 monthly usd: 2; public server monthly usd: 5; vcpu: 1; memory gib: 2; storage gb: 40; port mbps: 200, name: 2 vCPU / 2 GiB / 60 GB; base private only monthly usd: 4; public ipv4 monthly usd: 2; public server monthly usd: 6; vcpu: 2; memory gib: 2; storage gb: 60; port mbps: 200, name: 2 vCPU / 4 GiB / 80 GB; base private only monthly usd: 6; public ipv4 monthly usd: 2; public server monthly usd: 8; vcpu: 2; memory gib: 4; storage gb: 80; port mbps: 200, name: 4 vCPU / 8 GiB / 160 GB; base private only monthly usd: 15; public ipv4 monthly usd: 2; public server monthly usd: 17; vcpu: 4; memory gib: 8; storage gb: 160; port mbps: 200, name: 8 vCPU / 16 GiB / 320 GB; base private only monthly usd: 35; public ipv4 monthly usd: 2; public server monthly usd: 37; vcpu: 8; memory gib: 16; storage gb: 320; port mbps: 200; billing boundary: Services are pay-as-you-go, billed hourly and charged against account balance daily. Stopped services continue billing until deletion. The public plan cards add one USD 2/month transferable IPv4 to the base VM; directory offers use those complete public-server figures. The monthly labels are comparison estimates for a continuously allocated service, not fixed monthly invoices or documented monthly caps.; traffic: Traffic is marketed as unlimited/unmetered at the selected 200 Mbit/s channel. Current terms reserve the right to restrict an unlimited VM's channel if its use degrades other users.; location boundary: The current server-rendered production catalog has active tariff objects for Amsterdam, Frankfurt, New York and San Jose. Its location dictionary also contains Poland/pl-1, but the production filtered-location list removes Poland because no cloud-server tariff exists. Stale marketing and G2 seller copy naming Poland do not establish current orderability.

Operating systems

provider families: Ubuntu, Debian, CentOS; version boundary: The creation flow lets customers choose a release, but current anonymous documentation does not publish an exact live version matrix; versions are therefore not invented.; custom images: Upload from a computer or URL in ISO, VMDK, VHD, VHDX, VDI, RAW, IMG or QCOW2 format, up to 500 GB. Images require a BIOS-compatible bootloader/SeaBIOS, supported disk layout, root user and qemu-guest-agent for panel operations.; custom image location boundary: The July 2026 image documentation explicitly says server images are available for Amsterdam and Frankfurt. Customer-image availability is not attributed to New York or San Jose despite broader marketing language.; windows and other guests: A provider-supplied Windows catalog is not documented. Customer media can technically carry other systems if it satisfies Hostman's image requirements, but this is not represented as a licensed or supported Windows offer.; reinstall boundary: Reinstall accepts a clean OS, Marketplace image or eligible custom image and erases the server disk; Hostman backups remain in the dashboard.

Virtualization

hypervisor: KVM/QEMU; basis: Current production plan objects use KVM node-configuration identifiers; Hostman's current image requirements specify SeaBIOS, qcow2 and qemu-guest-agent. This is product-specific first-party implementation evidence, rather than a conclusion drawn from a generic VPS explainer.; guest model: Full VM with root access, clean provider images or qualifying customer images and a web console.; nested virtualization: not_found

CPU isolation

directory classification: guaranteed; provider claim: Hostman explicitly calls CPU, RAM and NVMe guaranteed resources and says Turbo Boost remains enabled to deliver the plan's performance level.; dedicated boundary: All 24 live location-plan tariff objects set is_dedicated_cpu to false. Guaranteed therefore means an assured virtual resource allocation, not a dedicated physical core.; frequency: Production tariff data says 3.3 GHz for Amsterdam, Frankfurt and San Jose and 3.0 GHz for New York. Hostman cautions that guest-visible base clock does not reflect Turbo Boost.; processor family: Marketing names Intel Xeon Gold and AMD EPYC; exact host model and overcommit ratio are not disclosed.

Features

• App installation cloud server methods: Provider OS images, Marketplace assemblies, eligible custom images, root-level manual installation and root-run cloud-init scripts.; marketplace: Hostman advertises 24 ready-made assemblies; current first-party examples include LAMP, Docker, GitLab, WordPress, Supabase, n8n and Grafana.; app platform: A related PaaS deploys frontend, backend, Dockerfile, Docker Compose and public Docker Hub image workloads onto Hostman cloud resources with build logs, Nginx/SSL and optional autodeploy.; boundary: App Platform is represented as an integration adjacent to the root VM product, not as a root-access benchmark offer.
  ✓
• Templates & images images: Provider OS and Marketplace images plus custom-media upload. Free reusable/downloadable QCOW2 server images survive VM deletion, but current image creation and use are explicitly limited to Amsterdam and Frankfurt.; backups: Manual backups and schedules of daily, weekly or monthly frequency with configurable retention, priced at USD 0.07 per provisioned disk GB. Backup storage remains billable until deleted and panel backups do not protect against every hardware/software failure.; snapshot: One snapshot per server, automatically deleted after seven days and itself deleted after restore. A snapshot blocks several plan/disk/backup operations while present.; clone and reinstall: Server cloning, clean reinstall, Marketplace reinstall and eligible custom-image reinstall are documented.; cloud init: Cloud-config or shell user-data can run at create, reinstall or a clean reboot.
  ✓
• Network orchestration public network: Optional external IPv4, transferable between services within the same region and retained after service deletion until explicitly deleted. The default plan card includes one USD 2/month address; accounts may request up to 10 new addresses per day.; ipv6: not_applicable — Hostman's January 2026 first-party tutorial explicitly says it does not currently provide IPv6 addresses for cloud servers.; private networking: Same-region VPCs with customer-selected RFC1918 ranges and manual private addresses. Servers can move among VPCs with a reboot and documented 5–10 minute downtime; public IPv4 may change.; nat: Free VPC routing rules support private-only, outgoing-only via NAT, or incoming-and-outgoing modes. NAT requires a billable public IPv4 on the gateway.; port and traffic: 200 Mbit/s plan channel with unmetered traffic, subject to the current fair-use/degradation clause in the Terms.; ddos: Product pages advertise infrastructure DDoS protection; the legal SLA excludes DDoS force-majeure downtime from compensation.; reverse dns: not_found; automation: Control panel, public API and official Terraform provider. Terraform covers cloud servers, storage, databases, Kubernetes, firewalls and VPC networking, with data sources for images, presets and configuration options.
  ✓
• Firewall type: Provider network firewall as a service, configured in the dashboard without guest-OS changes.; scope: Separate inbound and outbound rule sets; a group can span virtual servers, databases and load balancers across regions and availability zones.; limits: Up to 50 rule groups, 100 rules per traffic direction in each group and 200 attached services per group.; default behavior: With no rules, the firewall is not applied and all traffic is allowed.; automation: Covered by the official Terraform provider.
  ✓
• Load balancer service: Managed regional load balancer with one- or two-node configurations, public IPv4 and same-region private network. Third-party backends may be entered by IP.; protocols: HTTP, HTTP2, HTTPS, TCP; algorithms: round robin, least connections; health and transport: Configurable health checks, thresholds, Proxy Protocol, backend keep-alive, SSL handling and maintenance windows.; high availability: The two-node configuration includes a replica for fault tolerance.; price boundary: A current anonymous load-balancer price was not located, so no add-on price is asserted.
  ✓
• DNS management authoritative dns: Existing domains can use Hostman nameservers and have records added, edited and deleted in the dashboard. Hostman does not currently sell domain registrations.; record types: A, AAAA, CNAME, MX, TXT, SRV; zone import: Bulk .zone import supports the listed record types plus $ORIGIN and $TTL directives; unsupported record types/directives are ignored.; service binding: A/host targets can select a service on the Hostman account or a manually entered IP.; reverse dns: not_found; dnssec: not_found
  ✓
• Git integrations account integrations: GitHub, GitLab, Bitbucket; capabilities: OAuth/account connection, repository selection, branch/commit selection, build logs and automatic rebuild/deploy on new commits.; url connection: Public or credentialed private Git URLs, including Gitea, self-hosted GitLab and GitHub Enterprise, can be connected without granting an entire account; URL-connected repositories require manual deployment after changes.; deployment types: Framework buildpacks, Dockerfile and Docker Compose.; documentation conflict: A current FAQ says self-hosted repositories are unsupported, while the dedicated current connection guide explicitly supports externally reachable self-hosted Git URLs. The more specific workflow is retained and the lack of autodeploy is disclosed.
  ✓
• Container registry provider: Docker Hub; workflow: App Platform directly deploys an image name plus tag or digest, provisions a dedicated Hostman cloud server, configures a reverse proxy and exposes ports 80/443.; authentication: No linked Docker Hub account or authentication is used.; limitation: Only public Docker Hub images are supported; private images and other registry-provider integrations were not found.
  ✓