Solution
HPE / SANGFOR
01 | Expansion of Core-Based Billing
04 | Rising Long-Term TCO
05 | Deepening Vendor Lock-In
01 | All-in-One Integrated Architecture
02 | Simple Socket-Based Licensing
03 | Proven Global References
05 | Flexible Scalability

Core Components
Component
Description
aSV (Virtualization)
aSAN (Distributed Storage)
aNET (Virtual Network)
Built-in Security
CDP / DR
KVM-based enterprise-grade hypervisor with core features such as live VM migration, HA,
and snapshots built in
A vSAN alternative that pools node-internal disks into distributed storage,
eliminating the need for separate SAN storage
An NSX alternative providing SDN-based virtual switches/routers/firewalls
with micro-segmentation support
Ransomware protection, antivirus, and anomaly detection built in at the platform level
Integrated backup, replication, and DR based on CDP (Continuous Data Protection)
without separate solutions
Operational Benefits
Phase 0
Current-State Assessment
host specifications, and licensing model
Phase 1
Establishing Co-Existence
Configuration of new HPE-based clusters (virtualization/HCI)
Test migration starting with some non-critical VMs
Phase 2
Gradual Workload Migration
In the order of Dev/Test → internal operations → non-critical services
Operations-team training and runbook establishment
Phase 3
Core Workload Migration
Migration of mission-critical services
Reinforcement of HA and DR design
Phase 4
License Optimization & Stabilization
Assumptions (Example)
Cost Item
VMware (baseline 100)
SANGFOR (example)
Key Difference
Virtualization license
HCI / storage features
Backup / DR setup
Maintenance /
renewal (subscription)
Total (5 years)
45
25
15
15
100
30
Included
Included or 5
5–10
55–65
Effect of moving
from core- to socket-based licensing
Eliminates separate charges
(aSAN built in)
Leverages built-in CDP
Reduced renewal burden
Up to 35–45% savings
Competitive Positioning
Q1. "Isn't VMware the most stable?"
Stability comes from "operational structure," not from "brand"
SimpleKey designs HA/DR/standard-operations criteria at the same level even after the transition
Q2. "Migration is difficult and risky."
That is why SimpleKey designs co-existence → gradual migration rather than 'all-at-once replacement'
Transition risk is eliminated through an operational plan, not technology alone
The key is not the initial cost but the 5-year cumulative cost structure
The gap widens as core-based billing, subscriptions, and bundles accumulate
SANGFOR reduces external costs through built-in features (backup, DR, operations)
SimpleKey sets the goal of the transition as operational simplification, not "adoption"
It lowers operational complexity by including standard processes, monitoring, and an incident-response framework




