Project ideas from Hacker News discussions.

VMware migration reduces Tottenham Hotspur's licensing fees by 85 percent

📝 Discussion Summary (Click to expand)

1. Broadcom’s short‑term profit‑maximizing strategy for VMware
Commenters repeatedly argue that Broadcom plans to extract as much cash as possible from VMware before letting it decline, using steep price hikes and minimal support.
- “Broadcom has absolutely zero interest in the long‑term future of VMware. Their only goal is to squeeze as much money out of it as possible before it goes bust.” – crote
- “Unlike Hock Tan, you forgot to raise the prices 5‑10×. Then your 0.1% of customers generating 20% of your revenue turn into 0.1% of your customers generating the same amount of revenue as 100% of customers were before with lower operating costs and thus higher margins.” – quickthrowman

2. Real‑world migrations away from VMware (e.g., Tottenham Hotspur, Tesco)
Several users cite concrete cases where organizations replaced VMware with HPE or other platforms, highlighting large licensing savings and debates over control versus cloud reliance.
- “Tottenham Hotspur (…) has saved over 85 percent in licensing fees by replacing (…) VMware instance with Hewlett‑Packard Enterprise’s VME.” – gchamonlive
- “Tottenham Hotspur Stadium has 20,000 network access points, 1,849 IPTV screens, and 519 CCTV screens… running their own servers seems both more reliable and cheaper than renting.” – Symbiote

3. Enterprise lock‑in, migration difficulty, and evaluation of alternatives
The discussion stresses that many large organizations feel trapped by VMware’s depth of integration, lack of migration expertise, and perceived risk, even while considering alternatives like Proxmox, HPE GreenLake, SUSE, or Azure Local.
- “They tend to be large complex enterprises outside tech. They don’t have the people (from the cto/cio down) to execute a migration well.” – lokar
- “At my $dayjob we use Proxmox and it's good enough. I think Proxmox would be good enough for most orgs.” – INTPenis
- “Tesco claimed Broadcom hiked its VMware prices by about 175 percent in UK court filings.” – celsoazevedo


🚀 Project Ideas

Generating project ideas…

VMware Exit Planner SaaS

Summary

  • Automatically discovers VMware inventory, maps workload dependencies, and compares licensing costs against open‑source alternatives (Proxmox, oVirt, OpenStack).
  • Generates a step‑by‑step migration roadmap with ROI estimates, reducing migration risk and uncertainty.
  • Core value: Gives enterprises a clear, data‑driven path to cut VMware spend without guesswork.

Details

Key Value
Target Audience Mid‑large enterprises running VMware looking to reduce costs and evaluate alternatives.
Core Feature Automated discovery, dependency graph, cost‑comparison engine, migration plan generation.
Tech Stack Python backend, Neo4j for dependency graphing, GraphQL API, AWS Lambda/Kubernetes for scanning, VMware vSphere SDK, Grafana for reporting UI.
Difficulty Medium
Monetization Revenue-ready: SaaS subscription tiered by number of hosts or VMs (e.g., $5 per VM/month).

Notes

  • HN commenters complain enterprises lack the people to execute migrations well: “They don’t have the people (from the cto/cio down) to execute a migration well.” This tool gives them a concrete plan.
  • Provides practical utility by turning fear of migration into a quantifiable project, likely sparking discussion on alternative hypervisors and cost‑savings strategies.

VMware API Compatibility Layer for KVM

Summary

  • Exposes VMware vSphere SOAP/REST API endpoints but translates calls to libvirt/KVM backend, letting existing VMware‑based automation (PowerCLI, Ansible, Terraform) run unchanged on open‑source hypervisors.
  • Eliminates retooling costs and retraining friction during a hypervisor switch.
  • Core value: Enables a smooth, low‑risk transition by preserving current toolchains.

Details

Key Value
Target Audience DevOps and IT ops teams that want to keep existing VMware automation while migrating to KVM‑based platforms (Proxmox, oVirt, etc.).
Core Feature API translation proxy (vSphere API ⇄ libvirt) with near‑feature‑parity for common operations (VM provisioning, snapshots, networking, storage).
Tech Stack Go or Java proxy server, uses VMware SOAP SDK to parse requests, libvirt‑go/libvirt‑python bindings for backend, optionally deployed as a sidecar container; OpenAPI spec for REST translation.
Difficulty High
Monetization Revenue-ready: Enterprise support subscription per managed host (e.g., $20/host/month) with optional paid feature packs (advanced networking, storage plugins).

Notes

  • Users note Proxmox is “good enough for most orgs” but miss VMware tooling: “At my $dayjob we use Proxmox and it's good enough…”. This layer lets them keep Proxmox while retaining familiar workflows.
  • Sparks discussion on API compatibility vs. feature parity, and could become a cornerstone open‑source project with a commercial support model.

Managed VMware Exit Service (MaaS)

Summary

  • End‑to‑end managed service that handles discovery, migration planning, execution, validation, and cutover for enterprises lacking internal expertise.
  • Provides guaranteed downtime windows and post‑migration optimization, delivering clear cost savings.
  • Core value: Turnkey “VMware exit” for risk‑averse, large non‑tech organizations.

Details

Key Value
Target Audience Large non‑tech enterprises (retail, finance, government) with significant VMware footprints but limited migration skills.
Core Feature Professional services team + automated runbooks (using the Exit Planner SaaS internally) to perform full‑lifecycle migration to alternative hypervisors.
Tech Stack Orchestration via Cloudify or Temporal, Ansible/Terraform/Playbooks for VM conversion, Packer for image building, the VMware Exit Planner for analytics, monitoring via Prometheus/Grafana.
Difficulty High
Monetization Revenue-ready: Fixed‑price project fee based on VM count (e.g., $150 per VM) plus a success fee (e.g., 15% of verified first‑year savings).

Notes

  • HN highlights the talent gap: “They tend to be large complex enterprises outside tech. They don’t have the people (from the cto/cio down) to execute a migration well.” A managed service directly addresses this.
  • Offers practical utility by removing the barrier of expertise, likely generating discussion on outsourcing vs. in‑house migration and the viability of “exit‑as‑a‑service” models.

Read Later