amicu vs SkyPilot
SkyPilot is a broad system for running AI workloads (clusters, jobs and services) across many clouds, Kubernetes and Slurm. amicu is narrower: a declarative CLI that deploys vLLM or llama.cpp servers from HCL with a plan you review, recorded state and pre-flight checks. If you need training, batch jobs or the widest choice of infrastructure, SkyPilot covers far more ground today. If you want a reviewable, Terraform-style workflow for open-weight model endpoints on your machine or on GPU providers such as Modal and RunPod, amicu is built for that.
Side by side
Sources for the SkyPilot column: SkyPilot overview, SkyPilot installation. Details can change; check the official documentation.
When to choose SkyPilot
- You need training, fine-tuning or batch jobs alongside serving.
- You want to spread work across many clouds, Kubernetes clusters or Slurm.
- You need capabilities amicu does not have, such as multi-cloud failover.
When to choose amicu
- You only need open-weight LLM endpoints and want a plan-and-apply workflow for them.
- You want policy checks (residency, provider allowlists) before anything starts and an endpoint auth check after deploy.
- You want one small CLI whose state records how to stop each deployment, so destroy knows what to stop.
Questions
- Does amicu replace SkyPilot?
- No. SkyPilot covers a much wider range of AI workloads and infrastructure. amicu focuses on declaratively deploying LLM servers.
- Which providers does amicu support compared with SkyPilot?
- amicu runs on this machine and deploys to Modal and RunPod today. Hetzner, OVHcloud, Scaleway and SSH hosts are in preview, and AWS, Azure, GCP and Nebius are planned. SkyPilot lists many more clouds, plus Kubernetes and Slurm.
- Can I use both?
- Yes. They are independent tools. Use SkyPilot for jobs and clusters and amicu where you want a declarative LLM deployment.