On this page
#Kalisto documentation
Kalisto is a local-development Kubernetes runtime using k3s on macOS and Linux. These guides are the consolidated product documentation, migrated from the source README and operational guides at revision eb21785.
#Choose a backend
| Host | Backend | Preparation |
|---|---|---|
| Apple silicon, macOS 26+ | Apple containers, the macOS default | Installed Apple container CLI and running service; prepared kernel/init and Ubuntu/k3s OCI node image |
| Intel Macs or older macOS; explicit alternative on supported Macs | Native Lima VZ, Rosetta opt-in | Managed Lima runtime and sanitized VM disk/template |
| Linux | Firecracker, the Linux default | Host Firecracker/KVM and rootless networking prerequisites; explicit or configured kernel/rootfs plus prepared read-only boot assets |
The default never silently falls back to Lima. Existing clusters retain their recorded backend; selecting a different engine does not convert disks or archives. Kalisto runs its own k3s nodes, not Apple's experimental Kubernetes implementation.
#Start here
- Install and start a cluster: obtain a development candidate from the download selector, install the host prerequisites, then prepare and boot.
- Preparation and offline boot: understand reusable profiles, explicit Cilium selection and startup without downloads.
- CLI and cluster lifecycle: inspect resources, use managed kubectl, stop/resume, scale and delete only owned clusters.
- Workloads, add-ons and ingress: apply application manifests and explicitly configure ingress after startup.
#Operational and contributor guides
- Cluster backup and restore: Lima-only cold archives, native age encryption and safe imports. Native restore proof remains pending.
- AI agents and MCP: CLI-first instructions, the existing optional stdio server and complete background-task safety rules.
- Startup budget and live validation: the full three-node functional clock, measured results and authorized CI-only live tests.
- Contributor and artifact tooling: harnesses, versioning, legacy image helpers and substrate probes. These are not binary-install prerequisites.
- Binary releases and verification: four-target candidates, checksums, provenance and explicit publication safeguards.
#Availability and source
Only development candidates are offered here; no stable release is claimed. A compiled package does not establish runtime validation on every architecture. The native Linux Firecracker result was measured on x86_64; native Apple and optional Lima measurements have separate evidence boundaries.
Source is hosted on GitHub. Repository file links in these guides are pinned to the migration revision.