Zero-Knowledge Trust Model
All nodes are hardened by default. Fleet handles regional SSH cryptographic key rotation (id_ed25519), network isolation, and ephemeral control plane setup automatically.
The One-Click Fleet Management Engine transforms a collection of isolated, independent Linux hypervisors into a secure, cohesive, and centrally orchestrated Cluster Mesh powered by Ansible under the hood. Instead of manually logging into multiple nodes via separate SSH sessions to provision virtual machines, configure edge proxies, or manage encrypted tunnels, the Fleet Engine treats your entire infrastructure as a single programmable canvas.
Utilizing a secure Hub-and-Spoke topology, a single authorized Controller node commands and maintains state parity across remote worker nodes and guest instances without requiring heavy daemon agents running on host endpoints.
Fleet orchestrates host discovery, peer authentication, file transfers, and remote site synchronization across cluster members through agentless SSH execution paths.
All nodes are hardened by default. Fleet handles regional SSH cryptographic key rotation (id_ed25519), network isolation, and ephemeral control plane setup automatically.
# Initialize cluster on controller
one-click fleet init
# Register a new peer node to the mesh
one-click fleet add <ip> <hostname> [port]
# Verify node connectivity and key rotation state
one-click fleet verify
one-click fleet update-keys
# Sync configurations and perform audit/benchmarks across cluster
one-click fleet update
one-click fleet audit
one-click fleet bench
# Remote file distribution
one-click fleet put <host> <src> <dest>
one-click fleet get <host> <src> <dest>
# Execute targeted raw commands on peer node
one-click fleet raw <host> "<command>"
# Distributed site cloning and recovery
one-click clone-site example.com peer-node
one-click restore-site example.com peer-node
The VPS Engine converts Fleet members into orchestrated KVM virtualization hypervisors. Guests can be provisioned locally or target remote hypervisors across the cluster, immediately attaching to the cluster management plane.
| Flag / Command | Description | Example Scope |
|---|---|---|
--vps create |
Provision KVM Virtual Machine | --target, --name, --image, --cpu, --ram, --disk, --mode |
--vps snapshot |
Create or manage guest snapshots | --target, --name |
--vps migrate |
Live migrate VM between hypervisors | --target, --name |
--vps reinstall |
Re-image operating system | -n <name>, -i <image>, --password <pass> |
--vps [start|stop|delete|patch|backup|edit] |
Standard Lifecycle operations | Hypervisor targeting & lifecycle control |
# Provision a isolated NAT virtual machine on hypervisor1
one-click --vps create --target hypervisor1 --name db1 --image ubuntu24 --cpu 2 --ram 4G --disk 40G --mode nat
# Create point-in-time snapshot
one-click --vps snapshot create --target web1 --name backup_v1
# Live migrate VM across cluster hypervisors
one-click --vps migrate --target web1 --name web-node-02
# Reinstall base operating system image
one-click --vps reinstall -n web-node-02 -i ubuntu24 --password "SecretPass123" -l en_US
The Edge Proxy uses HAProxy running on the hypervisor boundary to securely route inbound public traffic (HTTP, HTTPS, TCP) directly into private, NAT-isolated guest VMs without assigning public IPv4 addresses directly to the guest.
# Expose internal web application on target VM through Edge HAProxy
one-click --proxy --target analytics-vm --website dashboard.example.com --proto https
# Map public listener port to private guest port (TCP forwarding)
one-click --proxy --target web1 --source 22 --port 8822
| Parameter | Type | Description |
|---|---|---|
--target |
String | Destination VM name or ID inside NAT environment |
--website |
Domain | Domain name for Layer-7 routing |
--proto |
Protocol | Supported protocols: http, https, tcp |
--source |
Port | Internal application port running inside guest |
--port |
Port | Public edge listener port on hypervisor |
Fleet automatically builds encrypted WireGuard mesh networks across cluster hypervisors, edge endpoints, and external management clients. It generates cryptographic profiles on demand and manages peer access rules natively.
# Add client configuration profile
one-click --wireguard add-user
# Revoke peer profile
one-click --wireguard delete-user
# Inspect active mesh status and peer endpoints
one-click --wireguard view
Access isolated guest VMs located inside private NAT setups directly without exposing public SSH ports or manually configuring SSH tunnels. Fleet automatically creates transient access bridges via the controller node.
# Connect directly to peer or guest instance by alias/IP
one-click --ssh <peer-name|peer-ip>
The distributed DNS orchestration engine manages BIND or API-backed zone providers across multi-region deployments. It synchronizes zone definitions automatically to prevent resolution drift across geographically distributed cluster members.
When a record, alias, or zone is updated on the Controller node, changes instantly replicate across all peer name servers registered in the Fleet mesh.