adrian207 · adrian207 · Oct 24, 2025 · Oct 24, 2025 · Oct 24, 2025
diff --git a/ON_PREMISES_README.md b/ON_PREMISES_README.md
@@ -9,8 +9,10 @@
 
 This branch provides a **complete on-premises deployment** with **NO Azure, AWS, GCP, or any cloud provider**.
 
+**Designed for:** Windows & Linux server migrations (not workstation/user migrations)
+
 ```
-NO CLOUD │ 100% LOCAL │ AIR-GAP READY
+NO CLOUD │ 100% LOCAL │ AIR-GAP READY │ SERVER-FOCUSED
 ```
 
 ---
@@ -41,16 +43,19 @@ NO CLOUD │ 100% LOCAL │ AIR-GAP READY
 
 ---
 
-## 💰 Cost Comparison
+## 💰 Cost Comparison (Server Migration Workload)
 
 | Timeframe | On-Premises | Cloud (Azure) |
 |-----------|-------------|---------------|
-| **Year 1** | $10-50k (hardware) | $6-36k (monthly fees) |
-| **Year 2** | $0 (owned) | $12-72k (total) |
-| **Year 3** | $0 (owned) | $18-108k (total) |
-| **Break-even** | 12-18 months | N/A |
+| **Year 1** | $15-231k (hardware) | $9.6-60k (monthly fees) |
+| **Year 2** | $16.2-237k (power only) | $19.2-120k (total) |
+| **Year 3** | $18.6-243k (total) | $28.8-180k (total) |
+| **Year 5** | $21.2-255k (total) | $48-300k (total) |
+| **Break-even** | 8-18 months | N/A |
+
+**After break-even:** Pure savings, only power/cooling (~$100-500/month)
 
-**After break-even:** Pure savings, only power/cooling costs
+**Key Advantage:** On-premises eliminates cloud bandwidth costs for large file server migrations
 
 ---
 
@@ -78,24 +83,39 @@ NO CLOUD │ 100% LOCAL │ AIR-GAP READY
 
 ---
 
-## 📊 Hardware Requirements
+## 📊 Hardware Requirements (Server Migration Sizing)
 
-### Tier 1 (50-100 users)
+### Tier 1 (10-50 servers)
 ```
-1 server: 24 vCPU, 128 GB RAM, 2 TB SSD
-Cost: ~$10,000
+2 servers (redundancy): 24 vCPU, 128 GB RAM each
+Storage: 2 TB NVMe + 8 TB HDD per server
+Migration Rate: ~5 servers per day
+Cost: ~$15,000
+
+Formula: 30 servers × 100 GB × 2 = 6 TB migration data
 ```
 
-### Tier 2 (500-1,000 users)
+### Tier 2 (50-200 servers)
 ```
-3 servers: 32 vCPU, 256 GB RAM, 12 TB each
-Cost: ~$40,000
+3-4 servers: 40 vCPU, 384 GB RAM each
+Storage: 4 TB NVMe + 20 TB HDD per server
+Migration Rate: ~15-20 servers per day
+Cost: ~$65,000
+
+Formula: 150 servers × 200 GB × 2 = 60 TB migration data
+Recommended: Separate NAS/SAN for file server data
 ```
 
-### Tier 3 (3,000-5,000 users)
+### Tier 3 (200-1,000 servers)
 ```
-6 servers: 48 vCPU, 512 GB RAM, 24 TB each
-Cost: ~$150,000
+6-8 servers: 56 vCPU, 768 GB RAM each
+Storage: 8 TB NVMe + 32 TB SSD per server
+Plus: Dedicated 100-500 TB SAN/Ceph cluster
+Migration Rate: ~50+ servers per day
+Cost: ~$225,000
+
+Formula: 500 servers × 300 GB × 2 = 300 TB migration data
+Network: 40/100 Gbps backend recommended
 ```
 
 ---
@@ -134,21 +154,31 @@ ansible-playbook playbooks/master_migration.yml
 - Air-gapped networks
 - Classified data
 - No cloud allowed
+- **Server consolidation** across agencies
 
 ### Healthcare
 - HIPAA compliance
 - PHI must stay on-site
 - Data sovereignty
+- **Medical records server** migration
 
 ### Financial
 - Regulatory requirements
 - No external data storage
 - Complete control
+- **Trading/database server** migrations
 
 ### Manufacturing
 - OT/ICS environments
 - No internet connectivity
 - Industrial networks
+- **SCADA/MES server** migrations
+
+### Datacenter Consolidation
+- **Multi-site server** migrations
+- **Merger/acquisition** server consolidation
+- Legacy server decommissioning
+- Physical to virtual (P2V) migrations
 
 ---
 
@@ -170,15 +200,17 @@ ansible-playbook playbooks/master_migration.yml
 ## ✅ What's the Same?
 
 Both branches provide:
-- ✅ Same migration automation
-- ✅ Same Ansible playbooks
-- ✅ Same ADMT functions
-- ✅ Same testing framework
-- ✅ Same monitoring dashboards
-- ✅ Same self-healing
-- ✅ Same DR capabilities
-
-**Only difference:** Where it runs (cloud vs on-prem)
+- ✅ Same migration automation (Ansible/AWX)
+- ✅ Same server migration playbooks
+- ✅ Same file server migration (SMS)
+- ✅ Same testing framework (150+ tests)
+- ✅ Same monitoring dashboards (Prometheus/Grafana)
+- ✅ Same self-healing automation
+- ✅ Same DR capabilities (backup/snapshot)
+- ✅ Same database migrations (PostgreSQL, SQL Server, MySQL)
+
+**Key difference:** Where it runs (cloud vs on-prem)  
+**Migration focus:** Servers, databases, and file shares (not end-user workstations)
 
 ---
 
@@ -195,8 +227,11 @@ Both branches provide:
 - [ ] Terraform configs for Proxmox
 - [ ] Terraform configs for Hyper-V
 - [ ] Terraform configs for KVM
-- [ ] K3s deployment automation
-- [ ] On-premises backup scripts
+- [ ] K3s deployment automation (Tier 3)
+- [ ] On-premises backup scripts (ZFS/Veeam/Bacula)
+- [ ] Storage sizing calculator (server-based)
+- [ ] Network design templates
+- [ ] Migration wave planning tools
 
 ---
 
@@ -206,14 +241,17 @@ Both branches provide:
 - ✅ Air-gapped environment required
 - ✅ Data must stay on-site
 - ✅ No cloud allowed (policy/compliance)
-- ✅ Long-term cost savings important
+- ✅ Long-term cost savings important (8-18 month ROI)
 - ✅ Already have hardware/virtualization
+- ✅ Large file server migrations (bandwidth cost avoidance)
+- ✅ Migrating 50+ servers (better economics at scale)
 - ✅ Prefer capex over opex
 
 **Use Cloud (main branch) if:**
-- ✅ Fast deployment needed
+- ✅ Fast deployment needed (minutes vs days)
 - ✅ No hardware available
-- ✅ Temporary project
+- ✅ Temporary project (<12 months)
+- ✅ Small server count (<50 servers)
 - ✅ Prefer opex over capex
 - ✅ Want managed services
 - ✅ Global distribution needed
@@ -222,6 +260,11 @@ Both branches provide:
 
 **Both are valid approaches!** Choose based on your requirements.
 
+**Break-Even Analysis:**
+- **Tier 1 (10-50 servers):** 18 months
+- **Tier 2 (50-200 servers):** 12 months
+- **Tier 3 (200-1,000 servers):** 8-10 months (faster at scale)
+
 ---
 
 **Version:** 1.0