Main features comparison
General informations comparison
| feature | VMWare ESXi | Elemento AtomOS |
|---|---|---|
| hypervisor level | 1 | 1 |
| underying OS | BSD-liek | RHEL-compliand Linux |
| Virtualizator | vSphere | Linux KVM "vanilla" |
| Management | via vCenter VM | via Electros app |
| Centralized services | Yes, uses server resources to manage services | Not needed using the C4 Protocol, all the management is client-side |
| Clusterization | It depends on the license | Automatic after installation |
Cluster Management
| feature | VMWare | Elemento | hypotetical release | Notes |
|---|---|---|---|---|
| Management Platform | vCenter VM | Electros app | ✅ Done | |
| Storage thin provisioning | Automatically included for qcow2 volumes, not possible with raw disk images | ✅ Done | ||
| VM Live migration | vMotion | Elemento Live Migration | September 2025 | Requires fast network and replicated underlying file system |
| Storage live migration | storage vMotion | Depends on underlying storage | We do not handle storage clustering directly. We suggest to use a distributed FS (like GlusterFS) which does not require to move volumes across machines | |
| Automatic Storage Migration | vSphere HA | Currently VMs and storage do not migrate on host failure | Not in roadmap | Desired, ETA 2026 |
| Resource load balancing | Distributed Resource Scheduler (DRS) | Resources are not automatically migrated based on hosts load since patent makes it not crucial | not in roadmap | no scheduled delopement |
| Hypervisor auto deploy | PXE-based for stateless ESXi hypervisor | PXE-based for stateless AtomOS hypervisor | Desired, ETA 2026 | |
| Host templating | Host profiles | Redundant with other features above | Not in roadmap | |
| CLI and API | Powershell CLI and vSphere rest API | Native for MacOS, Windows, Linux clients | ✅ Done | Leveraging C4 protocol |
Networking & Storage
| feature | VMWare | Elemento | hypotetical release | Notes |
|---|---|---|---|---|
| Network management | Sphere Distributed Switch (VDS) | Manyfold SDN | September 2025 | Allow VM connection both on CSPs and on-prem as if VMs are in the same network (VXLAN tagging for vms still not in roadmap) |
| Multiprotocol storage | iSCSI, NFS, Fibre Channel | Everrything that can be mounted on a POSIX path plus ceph | ✅ |
Security and Isolation
| feature | VMWare | Elemento | hypotetical release | Notes |
|---|---|---|---|---|
| Data encryption | native on VMDK | up to the user for now | Not in roadmap | based on the fact that we support natively all the FS that are POISX mountable we do not have limitation about encryption, but is up to the user to decide, is not included by default |
| Secure boot and TMP integration | Included | included | ✅ | |
| Granular for user permission and access | Role-Based Access Control (RBAC) | Currently improving user access to machines and resources | In developement, ETA December 2025 | Currently is in developement an improved authentication flow, resource access based onto user and organization is desired but currently non in the developement timeline |
| Host resource access | vSphere Trust Authority (vTA) | Resource access wil be user managed, not host managed | Each host manages its resouces fully |
Monitoring & Backup
| feature | VMWare | Elemento | hypotetical release | Notes |
|---|---|---|---|---|
| Log aggregation | vRealize Log Insight | Integration with ELK stack envisioned | Desired, ETA 2026 | |
| VM state (disk, memory, config) checkpoint | VM Snapshot | Already implemented as XML config dump. | ✅ Done | |
| Ghost VM replication | vSphere replication | In roadmap after vMotion introduction | December 2025 | |
| Metrics | Built in | Integrated Telegraf+Influx+Grafana stack with preconfigured dashboards. | ✅ Done | |
| Alarms | Built in alert tool | Desired but not yet implemented | Desired, ETA 2026 |
VM migration types
| type | from -> to | notes |
|---|---|---|
| hypervisor | old system -> AtomOS | consulting offering |
| cold migration | old system -> AtomOS | possible |
| cold migration | AtomOS -> AtomOS | possible |
| live migration | AtomOS -> AtomOS | possible but needs: same architecture, high bandwidth between machines, shared synced storage |
Additional features notes
- NO startup sequence between VMs of the same AtomOS system (useful for domain controller)
- Live migration can be performed between two AtomOS servers with the requirement of: same architecture, high bandwidth between them, shared synced storage
- The underlying infrastructure (VPN, ecc...) between different company locations are managed and created by the customer, if they ask how to create it refer to partners.
No comments to display
No comments to display