Three ways to reach the API.
- Loopback HTTP
- The default.
kilndlistens on127.0.0.1:8080, and only the host itself can reach it. - Remote HTTPS
- Kiln gets a Let's Encrypt certificate for your domain. The domain has to resolve to the host, with ports 80 and 443 open.
- Remote HTTP
- Off unless the host and the client both opt in. A VPN or tailnet does not remove either opt‑in.
To serve the API over HTTPS, set three variables on the host and log in with the domain.
KILN_TLS_ENABLED=true
KILN_TLS_DOMAIN=kiln.example.com
KILN_ACME_EMAIL=operator@example.com
kiln login --api-url https://kiln.example.com --token <token>
Every request carries a bearer token, whichever way it arrives.
Keep the disk in check.
Root filesystems are sparse files, so a 64G disk takes only the space the guest has written. Cached images and old machine directories are what build up.
Cleanup never touches Docker images, or anything a machine or image still uses.
-
kiln disk usageShows what images, machines and caches take up.
-
kiln cleanup --dry-runLists what a cleanup would delete, and deletes nothing.
-
kiln cleanupDeletes image and machine directories nothing refers to, superseded profile caches and temporary files older than an hour.
Watch the host.
Four commands report on the node and its machines. They are live snapshots, and Kiln keeps no history.
kiln node healthkiln node capacitykiln metrics summarykiln vm metrics dev
Kiln is not released yet.
It is in private development, and there is nothing to download today.
Kiln Console, the iOS companion app, is at its first milestone. It is a read-only dashboard running on sample data.