Engineering

Ankra's own platform now runs in Helsinki. The timeline, the bill, the benchmark numbers, and the places UpCloud let us down, from the team that did the move.

We ran the same k6, iperf3 and fio suite on EKS, GKE and Hetzner and lined the results up against UpCloud, OVH and DigitalOcean. The cheapest node in the test won more than it had any right to.

Two identical cloud VMs measured 2.8x apart on CPU; one failed etcd's fsync bar. A 15-minute in-cluster benchmark suite catches this before production does.

We ran the same k6, iperf3 and fio suite on identical Kubernetes clusters on UpCloud, OVH and DigitalOcean. The spec sheets matched; the numbers did not.

The 'never run a database on Kubernetes' rule predates CSI and operators. What production Postgres takes in 2026, and when managed still wins.

A new name, a new engine, and the biggest release we have ever shipped: the Go rewrite, an AI that owns the incident loop, passkey security, European multi-cloud, and Ankra on your phone.

New Ankra clusters no longer run ArgoCD. Here is the engineering story of the native deployment engine: why we built it, how the reconcile loop works, what the migration does to your live resources (nothing), and what we have not finished yet.