Haru: keep self-hosted inference up, without idle GPUs.
What Haru does.
Hot failover
Haru runs your GPUs as an Active/Standby pair in two failure domains: different regions, or different clouds. When the active side fails, the standby takes over serving in seconds.
No idle GPUs
A classic hot standby bills you for GPUs that do nothing. On Haru, the standby keeps its inference servers asleep with weights parked in CPU RAM, and uses the freed VRAM to run LoRA training until it is needed.
Verified, not scripted
Failover is a sequence of checked state transitions: stop training, verify the VRAM is free, wake the servers, probe every model, then move routing in one atomic step. A failed step never moves traffic.
Haru Cloud: fully managed fleets.
SoonThe same open-source Haru, operated by Arkor: provisioning, supervision, and failover watched around the clock, without running the control plane yourself.
More from the toolkit.
Get a hosted endpoint, collect traffic, fine-tune, serve your weights.
Learn moreCode-first SDK for fine-tuning open-weight models.
Learn moreLLM code review that catches stale comments and drifted docs.
Learn moreCloud inference and training with the confidentiality of running locally.
Learn more