System requirements¶
Keel runs as a single virtual machine (or a set of them for High Availability).
Minimum per node¶
| Resource | Minimum | Notes |
|---|---|---|
| vCPU | 4 | More improves ingest + query throughput and local-LLM speed. |
| RAM | 8 GB | 16 GB+ recommended for heavier ingest or a local model. |
| OS disk | ~40 GB | The appliance system disk (provided by the image). |
| Log-storage disk | sized to retention | A second virtual disk for the log store; size it to your daily volume × retention. |
| Hypervisor | VMware, Hyper-V, KVM/Proxmox, OpenStack, OpenShift Virtualization, or compatible | Must import OVA/VHDX/QCOW2 and attach a second disk. |
CPU note: the appliance requires an x86-64-v2 capable CPU. On some hypervisors set the VM CPU type to host (or a model that exposes x86-64-v2) rather than a minimal generic type.
Two disks¶
Keel uses two disks: 1. OS disk — the system, swapped wholesale on upgrades. 2. Log-storage disk — your logs and configuration data; persists across upgrades.
Attach the second disk before first boot (or add it later from Settings → Storage).
Sizing the log-storage disk¶
A rough guide: daily_GB × hot_retention_days, plus headroom. If you enable an S3-compatible
cold tier, the local disk only needs to hold the hot window; older data tiers to object
storage. See storage.
Network¶
- One network interface (DHCP by default; set a static IP after first boot).
- Inbound: only the ingest/dashboard ports you enable.
- Outbound (optional): the license portal (
*.infranexis.com:443) for connected mode and updates, and your LLM endpoint if hosted. Air-gapped needs neither.
For High Availability¶
Run 3 nodes (recommended for quorum) on the same network, plus a free IP for the floating VIP. See high-availability.