(translation pending)
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.
Pre-warmed images, parallel bootstrap, no-op cloud-init by default. SSH is ready before Slack finishes loading.
# 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).
| Flavor | vCPU | RAM | Network | Price |
|---|---|---|---|---|
| c5.small | 1 vCPU | 2 GB | 1 Gbps | 1.30 ₽/hr |
| c5.largebest · workhorse | 4 vCPU | 16 GB | 5 Gbps | 5.40 ₽/hr |
| c5.xlarge | 8 vCPU | 32 GB | 10 Gbps | 10.80 ₽/hr |
| m4.compute | 8 vCPU | 32 GB | 10 Gbps | 8.00 ₽/hr |
| m4.memory | 16 vCPU | 128 GB | 25 Gbps | 26.40 ₽/hr |
| r4.4xlarge | 16 vCPU | 256 GB | 25 Gbps | 38.00 ₽/hr |
| g1.gpu | 16 vCPU | 96 GB | 100 Gbps | from 250 ₽/hr (B300 MIG) |
| bare-metal · m6 | 64 vCPU | 512 GB | 2× 100 Gbps | from 28,000 ₽/month |
Prices for compute. Disks, IPv4 and traffic are billed separately — full pricing in /price.
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.
+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).
CPU numbers — SPECrate2017 single-thread, geomean. Network — fabric uplink per rack. Egress — competitors' public pricing for outbound traffic up to 1 TB/month.
Hypervisor-level isolation, encryption by default, 800 Gbps DDoS protection — included for every VM, no upgrades, no extra fees.
Every VM gets its own SR-IOV port on the NIC and NUMA-aware placement. 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.
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. Ready to take part in your audits — checklists, policies, evidence base.
Full list of certificates and attestations (8 of them) — at /infrastructure → compliance. Copies — on request 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.
What we kept (KVM, OVS), what we rewrote (orchestrator, network plane), what we regret (not much).
What broke (network), what got simpler (everything else), before/after numbers.
VPC peering, security groups, SR-IOV firewall. How to keep a flat network under control.
fio, sysbench and real workloads on three disk types. When to pick which.
Production-ready: network, nodes, load balancer, monitoring. For dev/staging/prod.
No portal, no YAML manifests, no container builds. Just handler → deploy.
Let's go →brew install h3llo/tap/cli · or curl get.h3llo.cloud | shh3 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.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.