kFleet fits if…
- Your estate uses several container engines.
- You do not want to migrate every host to one runtime.
- You want operations, security and networking closer together.
kFleet use case
Operate Docker, Podman, LXC and Incus together
A mixed estate should not force a team to maintain one console and one access model for each container engine.
The short answer
kFleet connects Docker, Podman, LXC, LXD, Incus and machinectl through one console. Containers can be inventoried, started, stopped and inspected with their logs while their configuration remains versioned.
Unify without migrating everything
Existing engines stay in place. kFleet adds a cross-platform view and can install Docker, Podman, LXC and Incus on supported hosts.
- Multi-host, multi-engine inventory
- Lifecycle and log access
- Versioned configuration and shared permissions
Connect containers to infrastructure
Containers join the same topology as machines, Kubernetes, firewall rules, DNS and certificates.
Is it the right tool for you?
Limits to know
- kFleet does not replace engine-specific advanced features.
- For multi-node application orchestration, Kubernetes remains the specialised engine.