
The Everything Feed - All Packet Pushers Pods TCG071: Cloud Cloning and Portability – Why Multi-Cloud Freedom Still Requires Translation (Sponsored)
7 snips
Mar 18, 2026 Sharad Kumar, co-founder and CEO of FluidCloud, builds tools to make multi-cloud portability and VMware exits easier. He talks about cloning existing clouds into Terraform/state, translating networking and IAM across providers, and creating landing zones and continuous governance. The conversation highlights why true multi-cloud needs architectural translation, not just unified syntax.
AI Snips
Chapters
Transcript
Episode notes
Founders Built FluidCloud From Their Own Migration Nightmare
- Sharad Kumar and Harshit Omar started FluidCloud after their previous company's acquisition left them spending eight months moving accounts between AWS environments.
- That migration pain sparked a project to automate moves, which evolved into a product addressing broader cloud-to-cloud and VMware portability.
Terraform Is A Common Language Not A Cross Cloud Architecture
- Terraform provides a unified syntax but not a unified architecture because each cloud provider's Terraform provider maps to unique APIs and constructs.
- FluidCloud's thesis was to keep customers' existing Terraform workflows while generating provider-specific Terraform and state for target clouds automatically.
Scan VMware First Then Choose Your Target Cloud
- Scan and discover your VMware environment first to get compatibility scores and an infrastructure blueprint before choosing a target cloud.
- Use those compatibility reports to avoid low-success migrations and to generate an advanced landing zone with translated networking and firewall rules.
