Platform
Everything LexiVirt does today.
Grouped the way the console is. The number is the release each capability arrived in. The full guide for each, with step-by-step use and its limits, is on lexi-cloud.com/features.
Infrastructure
- Fleet 1.8.1
- Every LexiVirt cluster this console manages, read live from each one: capacity added up, alerts in one feed, and a search that finds a virtual machine without opening each console in turn.
- Clusters 1.7.0
- This console's own cluster: which nodes are in it, what they add up to, and where each virtual machine sits.
- Nodes 1.0
- The machines that run virtual machines, each with a small agent the console talks to over an authenticated channel.
- Virtual machines 1.0
- Create, start, stop, clone and resize KVM guests.
- Containers 1.7.4
- OCI containers beside virtual machines, on whichever runtime a node already has — Podman first because it is daemonless, then Docker.
- GPU 1.7.2
- Discovers the graphics and compute cards on each node and passes a whole card through to one virtual machine.
Storage
- Storage 1.0
- Where a virtual machine's disk lives on each node: the node's own disk, another mounted directory, an NFS export, or an LVM volume group.
- Volumes 1.6
- Disks that belong to no single machine: attach one to several at once for a cluster's quorum disk or shared data.
- Snapshots 1.5
- Point-in-time copies of a virtual machine's disks, taken while it is off, including its firmware variables.
- Backups and recovery points 1.5
- Recovery points on a schedule, kept next to the disks for a fast way back, and backups copied off the node into a deduplicated repository that is checked after every run.
Network
- Networks 1.0
- Bridged and NAT networks on each node, VLAN-tagged segments, and DHCP reservations that pin a guest to an address.
- Overlay networks 1.7.3
- A VXLAN segment that spans nodes, so virtual machines on different hosts share one layer-2 network without touching the physical switches.
- Firewall 1.7.2
- Rules that open and block traffic between virtual machines, compiled to an nftables ruleset and pushed to every node.
- Load balancer 1.7.4
- One address and port spread over several backends, as destination NAT in the kernel's connection tracker.
Operations
- Monitoring 1.4
- CPU, memory and disk per node and per virtual machine, recorded over time, with a capacity runway derived from what was actually measured.
- Alerts 1.4
- What is wrong now, most severe first, with the reason and the fix.
- Tasks 1.3
- Everything slow — clones, image copies, migrations, backups, updates — runs as a task with progress and history, rather than holding a request open.
- High availability 1.7.3
- A virtual machine marked for HA is restarted on another node when its own is lost — after a second node confirms it cannot reach the first, so a console that merely lost its own network does not fail everything over.
- Kubernetes 1.7.5
- Builds a k3s cluster out of virtual machines from a cloud image, and fetches the kubeconfig back for you.
- AI agents 1.8.3
- The console is an MCP server: any Model Context Protocol client can read and operate a cluster with nothing installed on the agent's machine, just a URL and an API key.
- HCI console 1.9.0
- A console for whoever runs the infrastructure rather than the virtual machines, on a port of its own (9440 by default) so it can be firewalled to the management network.
Administration
- Projects 1.6
- Group virtual machines and the people who may touch them, so one team's machines are not another team's to start, stop or delete.
- Tenants 1.9.9
- Customers of the cluster, kept apart: each with its own quota, networks, storage and administrators.
- My tenant 1.9.9
- What a tenant's own accounts see: how much of its quota it uses, the networks, storage and nodes it was given, and — for its tenant administrators — its accounts, which they add, change and remove themselves.
- Users and roles 1.0
- Local accounts in three roles — administrator, operator and viewer — with optional two-factor authentication.
- Security 1.6
- API keys for scripts and agents, each with its own role and revocable on its own, and the recent activity on the installation in one place.
- Audit log 1.2
- Who did what, when, and from where — written per action by the console that performed it.
- Files 1.5
- A shared drive for administrators: upload a file from one machine and download it from another, with nothing but the console sign-in.
- Terminal 1.6
- A shell on the console host, in the browser, as the account the console runs as — not as root, once the console has been moved onto its own unprivileged account.
- Settings 1.4
- Thresholds for alerts, notification delivery, session length, appearance, what each node is told about time and name servers, and what this installation reports about itself.
- Updates 1.2
- One pass updates the console and every node agent it can reach, each reported by name.
- Readiness 1.0
- What stands between this installation and running its first virtual machine: each finding with its severity, why it matters and the command that fixes it.