By Guest: Julian Fischer (LinkedIn)
Company: anynines
Show Name: KubeStruck
Topic: Kubernetes
Broadcom’s acquisition of VMware sent shockwaves through enterprise infrastructure teams. License changes. Price increases. Vendor lock-in fears. For organizations that built their platforms on VMware, the question became urgent: what’s the alternative? Julian Fischer, CEO & Founder of anynines, has a direct answer. a9s Cloud Foundry is a battle-tested distribution running hundreds of thousands of application instances globally—and it’s positioned as a drop-in replacement for costly commercial platforms. More importantly, anynines has mastered what many enterprises desperately need: zero-downtime migrations that work across infrastructure layers.
📹 Going on record for 2026? We're recording the TFiR Prediction Series through mid-February. If you have a bold take on where AI Infrastructure, Cloud Native, or Enterprise IT is heading—we want to hear it. [Reserve your slot
The Post-Broadcom Reckoning: Enterprise Platforms Under Pressure
The Broadcom acquisition created an immediate crisis for enterprises relying on VMware infrastructure. Licensing models shifted. Pricing escalated. Customers who once saw VMware as a stable, long-term platform investment suddenly faced uncertainty. The result is a wave of infrastructure teams re-evaluating their entire platform strategy.
This isn’t a theoretical problem. Enterprises with thousands of application instances running on VMware-based platforms need viable alternatives—not experimental projects, but proven, production-hardened solutions that can handle real workloads at scale. Fischer’s positioning of anynines as “the alternative to Broadcom tensor these days” acknowledges this market reality directly.
a9s Cloud Foundry: Proven at Scale Across the Globe
Fischer’s credibility comes from scale. Cloud Foundry is “currently operating hundreds of thousands of application instances across the globe.” This isn’t a startup pitch—it’s operational proof that the platform works at enterprise scale. The distribution has been battle-tested in production environments, managing real workloads with real uptime requirements.
What makes this particularly attractive post-Broadcom is the simplicity of adoption. Fischer describes it plainly: “People can take our distribution, set it up, and basically have their own Cloud Foundry. That’s more or less a drop-in replacement for commercial alternatives.” For infrastructure teams evaluating options, this is critical. A true drop-in replacement means existing applications, configurations, and operational patterns transfer with minimal friction. The learning curve is shallow because the platform is already familiar.
Operational Support and Zero-Downtime Migrations: The Real Differentiator
Beyond the software itself, anynines offers something many open-source alternatives don’t: operational maturity. Fischer highlights two key service offerings—remote operations support and zero-downtime migration expertise. These aren’t commodities.
The zero-downtime migration capability is particularly relevant post-Broadcom. Enterprises don’t have the luxury of taking their platforms offline during transitions. Whether migrating from one Cloud Foundry flavor to another or moving across underlying infrastructure, downtime translates directly into business impact. Fischer notes that anynines has “been doing this from one Cloud Foundry flavor to another” and has extensive experience “doing migrations from one infrastructure to another.”
This operational depth reveals the real value proposition. It’s not just about the software—it’s about having a partner who understands the migration process, can execute it reliably, and can guarantee application availability throughout the transition. For risk-averse enterprise teams, this de-risks a critical operational change.
Infrastructure Flexibility: OpenStack, vSphere, and Beyond
Another layer of anynines’ value proposition is infrastructure flexibility. Fischer explicitly states that anynines is “very strong at running Cloud Foundry on OpenStack” and “strong at running Cloud Foundry on vSphere or on any major cloud provider.” This matters because it decouples Cloud Foundry from infrastructure vendor lock-in.
Post-Broadcom, enterprises want to avoid trading one vendor lock-in for another. anynines’ ability to run across multiple infrastructure layers—whether on-premises vSphere deployments, OpenStack clouds, AWS, Google Cloud, or Azure—means organizations retain control over their infrastructure destiny. If they want to migrate away from VMware infrastructure entirely, they can. If they want to maintain their vSphere investments while replacing the platform layer, they can do that too. This flexibility is genuinely valuable.
For Those Who Don’t Want to Operate: Remote Operations as a Service
Not every enterprise has the internal expertise or desire to operate its own Cloud Foundry distribution. Fischer acknowledges this: “For those who actually don’t want to run it themselves, we have remote operations and operations support alternatives.” This is a critical offering for mid-market organizations that lack large platform operations teams.
Remote operations means enterprises can adopt a proven Cloud Foundry stack without building internal operational expertise. anynines handles the day-to-day management, updates, scaling, and troubleshooting. The enterprise retains control over their applications and data; anynines manages the infrastructure. This model appeals to organizations that want to escape Broadcom pricing without accepting the complexity of self-managed infrastructure.
The Broader Market Shift: Broadcom Drives Open Source Adoption
Fischer’s positioning reflects a broader market trend. Broadcom’s acquisition and subsequent changes have accelerated interest in open source alternatives across the enterprise infrastructure space. Cloud Foundry, long positioned as a commercial platform, is now increasingly seen as a viable alternative to proprietary solutions. Organizations that might have dismissed open source Cloud Foundry five years ago are now seriously evaluating it—not out of ideological preference, but out of practical necessity.
This shift benefits anynines because they’ve been running Cloud Foundry operationally for years. They understand the real-world challenges: how to scale it, how to migrate workloads, how to integrate it with existing enterprise infrastructure. They’re not academics or early-stage startups—they’re practitioners who’ve solved the hard problems at scale.
Why This Matters for Infrastructure Teams Evaluating Post-Broadcom Strategies
For any enterprise infrastructure team facing the post-Broadcom reality, the core decision tree is simple: stay with expensive commercial platforms, adopt Kubernetes wholesale, or find a middle ground that preserves existing investments while avoiding vendor lock-in. a9s Cloud Foundry represents the third option—a proven, operationally mature platform that’s already running hundreds of thousands of applications globally.
The zero-downtime migration capability means the transition doesn’t require a disruptive cutover. The infrastructure flexibility means organizations retain control over their underlying technology stack. The remote operations option means even smaller teams can adopt the platform without building internal operational expertise. For risk-averse enterprise teams, anynines provides a path forward that feels safer than betting entirely on Kubernetes, and far cheaper than staying locked into Broadcom pricing.
Fischer’s framing is direct: anynines isn’t positioning itself as the future of cloud platforms. It’s positioning itself as the practical alternative to expensive vendor lock-in—for organizations that built their platforms on proven technologies and want to keep doing so without paying escalating licensing fees.
