c5.small
Minimal flavor for a bastion, sidecar or dev environment.
vCPU1
RAM2 GB
Network1 Gbps
Price1.30 ₽/hr
Compute, networking and storage, rewritten after 2020. KVM/QEMU 9 on EPYC and Xeon Platinum, EVPN-VXLAN spine-leaf on Arista, NVMe Gen5 with replicated storage. No Keystone glitches, no Neutron bottlenecks, no Heat surprises.
EPYC · Xeon Platinum · NVMe Gen5 · live migration · per-second billing
OpenStack clouds are assembled from 2010-era parts. The result is a layer of duct tape: Keystone breaks, Neutron is slow, Heat doesn't work. We kept only what was good (KVM/QEMU, OVS) — and rewrote the rest.
Via our CLI or Terraform — pick whichever fits. No web-only, no 'click the button'. VM ready in 11 seconds either way.
# spin up a VM with one command
$ h3 vm create my-app \
--flavor=c5.large \
--image=ubuntu-22.04 \
--region=msk-1 \
--network=default
→ Creating VM (4 vCPU · 16 GB · 100 GB NVMe)
→ Allocating SDN port (vxlan-vni 8421)
→ Bootstrap cloud-init (no-op default)
✓ VM ready in 11 seconds
$ ssh root@95.183.21.44
Welcome to Ubuntu 22.04 (5.15.0-h3llo)
root@my-app:~#terraform {
required_providers {
h3llo = { source = "h3llo/h3llo", version = "~> 0.4" }
}
}
resource "h3llo_vm" "app" {
name = "my-app"
flavor = "c5.large"
image = "ubuntu-22.04"
region = "msk-1"
network {
name = "default"
public_ip = true
}
disk {
size_gb = 100
type = "nvme-replicated"
}
}Prices are per-second pay-as-you-go. Reserved (1 year) — −30%, dedicated host — separate. You can switch between flavors live (no downtime). Disks, IPv4 and traffic are billed separately — full pricing in /price.
Minimal flavor for a bastion, sidecar or dev environment.
The typical pick for web, API and Kubernetes nodes. Our most popular flavor.
When c5.large is bottlenecked on CPU or network. Same generation, more throughput.
Compute-optimized flavor — higher clock, less RAM per core.
Memory-optimized — for in-memory caches and analytics databases.
Max RAM/core. For large Postgres, ClickHouse, Redis clusters.
GPU flavor on B300 MIG partitions for inference and fine-tuning.
A whole physical server. For compliance and HPC clusters.
Not "modern infrastructure" from marketing brochures. Real numbers on hardware, network and traffic — compared with typical clouds on Xeon gen 2/3 and 25G uplinks. CPU — SPECrate2017 single-thread, geomean. Network — fabric uplink per rack. Egress — competitors' public pricing for outbound traffic up to 1 TB/month.
+52% IPC on SPECrate2017, +63% memory bandwidth. Your DB on DDR5-NVMe-NVLink — not on 7-year-old 2018 hardware.
16× more uplink per rack, p99 ≤ 50 µs between VMs in the same AZ. DPDK fast path, SR-IOV, RDMA — no bottlenecks in the network plane.
Up to 100,000 ₽/year in savings on a typical SaaS stack. Beyond 1 TB — 1.50 ₽/GB (6× cheaper than AWS egress).
c5.large is the typical pick. SDN with private VPC, public IP, security groups. Auto-healing, snapshot in 4 seconds.
r4 for in-memory + NVMe Replicated disk. 3× replication, auto-failover ≤ 60 sec, snapshot to S3.
c5.small + dedicated public IP. SR-IOV port for line-rate firewall. Audit log to S3 by default.
Bare-metal m6 for a cluster or dedicated host. 100 Gbps RDMA network, NUMA-aware scheduler.
Hypervisor-level isolation, encryption by default, 800 Gbps DDoS protection — included for every VM, no upgrades, no extra fees. The full list of certificates and attestations (8 of them) — at /infrastructure, copies under NDA.
Every VM gets its own SR-IOV port on the NIC and NUMA-aware placement. KVM/QEMU 9, NUMA pinning. No noisy neighbors, no shared disk queue.
Disks — LUKS on NVMe self-encrypting drives. Traffic inside the VPC and outbound — TLS 1.3. Keys — in our KMS (HSM-backed) or in yours. AES-256 at-rest.
L3/L4 protection at the network edge — on for every VM by default, no extra cost. The "you're under attack" scenario is closed by automation in tens of seconds.
FZ-152, FZ-242 (data in-country), FSTEC (K2), PCI DSS 4.0, ISO 27001/27017, GOST R 57580. 8 certifications — ready to take part in your audits, copies under NDA.
Pay-as-you-go for dev and variable load. Reserved for production (−30%). Dedicated host for compliance and regulated markets.
Real benchmarks, migrations, architecture deep dives. No fluff, no marketing.
Cloud-init, health checks, disk replication, snapshots, audit logs — what you must check. ~15 min.
→Guide · 32 pph3llo IaaS control-plane architecture: what we kept (KVM, OVS), what we rewrote, what we regret. ~30 min.
→Case · HyperionHyperion AI: 240 VMs from Mirantis to h3llo. What broke (network), what got simpler, before/after numbers. ~22 min.
→Guide · 20 ppSegmentation and zero-trust on IaaS: VPC peering, security groups, SR-IOV firewall. How to keep a flat network under control. ~25 min.
→Benchmark · 2025Storage benchmark: IOPS, latency, MTBF. fio, sysbench and real workloads on three disk types. ~12 min.
→Templates · GitHubReady modules: VPC, VM-pool, LB, snapshots. Production-ready for dev/staging/prod. 5 modules.
→No portal, no YAML manifests, no container builds. Just handler → deploy.
`brew install h3llo/tap/cli` · or `curl get.h3llo.cloud | sh`.
`h3 vm create my-app --flavor=c5.large` · 11 seconds to SSH-ready.
`h3 vm ssh my-app` or direct SSH to the public IP. No bastion setup.
A ready `h3llo_vm` provider. From the outside — your usual Terraform flow.
No Keystone glitches, no Neutron bottlenecks. KVM/QEMU 9, EVPN-VXLAN spine-leaf, NVMe Gen5. Per-second billing, live migration, FZ-152 compliant.