How kcore approaches virtualization differently. API-first, declarative, automation-friendly.
The decisions that shape kcore
The gRPC API is the primary interface. Every operation — creating VMs, managing storage, configuring networks — goes through the API. The CLI, web UI, and any agent tooling are all API consumers.
You describe the desired state. kcore converges to it. No step-by-step scripts that break when something changes. State reconciliation is built into the core loop.
The base system does not change at runtime. Updates are applied as new system generations. If an update fails, you boot the previous generation. No partial states.
AI agents and automation tools interact with kcore through the same APIs that humans use. The platform is machine-friendly by design — structured inputs, predictable outputs, no GUI-only workflows.
kcore favors straightforward solutions. A small, correct system is better than a large, feature-complete one that's hard to reason about. Complexity is the enemy.
You own your hardware, your data, and your configuration. kcore does not phone home, require a cloud account, or impose licensing restrictions on how you use it.
The host OS is built on NixOS. System updates produce a new generation. If something goes wrong, you boot the previous generation. There is no "partially applied update" state.
Define what you want. kcore makes it happen. Version control your entire infrastructure. Reproduce it on another set of hardware with the same config files.
# infrastructure/vms.tf
resource "kcore_vm" "web" {
count = 3
name = "web-${count.index}"
memory = 4096
vcpu = 2
disk {
size = "50GB"
storage_class = "local-lvm"
}
network {
name = "internal"
}
}
kcore is designed so that automation agents — including AI agents — can interact with the platform through the same interfaces humans use. No special "AI mode." The platform is machine-friendly by default.
An honest look at the current state. kcore is alpha software.
| Capability | kcore (alpha) | Proxmox |
|---|---|---|
| API-first design | ✓ gRPC | REST (secondary to UI) |
| Declarative config | ✓ Native | ✗ Imperative |
| Immutable host OS | ✓ NixOS | ✗ Debian (mutable) |
| Agent-friendly interfaces | ✓ By design | ✗ Not a design goal |
| Production maturity | Alpha | ✓ Battle-tested |
| Community & ecosystem | Early | ✓ Large |
| HA & clustering | In progress | ✓ Mature |
| Web UI | Planned | ✓ Full-featured |
kcore is alpha software and does not yet match Proxmox in feature completeness or stability. This table reflects architectural direction, not current parity.
We're looking for early testers and design partners who want to help build a modern alternative to Proxmox.
Alpha software. For labs, experimentation, and early design partners only.