>And open almost always wins when it comes to infrastructure adoption.
They lost me here. Too many counterexamples exist for me to even continue.
>And open almost always wins when it comes to infrastructure adoption.
They lost me here. Too many counterexamples exist for me to even continue.
Kubernetes vs AWS?
openstack vs aws/azure/gcp/... would make more sense.
> Kubernetes vs AWS?
How is this even a direct comparison? Most companies I know of which use Kubernetes are using it on a cloud provider. Even if it's kubernetes on EC2 rather than hosted e.g. EKS, those companies are also happy to use lock-in services like RDS and S3.
Kubernetes vs EKS?
Here is a counterexample to whatever counterexample you have in mind -
Most popular models on OpenRouter right now: https://openrouter.ai/models?categories=programming&order=mo...
Top 7 are all open models.
There very little reason to use OpenRouter to access closed models, instead of just using the provider directly.
One big reason I can think of is to avoid vendor lock-in. This is why most enterprises use a multi-cloud setup, despite the increased complexity.
If you're only using the frontier providers, it's nearly trivial to support switching between the 2-3 of them that exist without using OpenRouter.
If you are ALSO routing to open-weights models on OpenRouter, then sure. But what we've come back to is that almost everyone using OpenRouter is someone who wants to use open-weights models, and some of them also want to use closed models, so of course open models take all the top spots.
Most enterprises are multi-cloud in that they have multiple direct contracts with different cloud providers.
>This is why most enterprises use a multi-cloud setup
Going to have to say citation needed on this, if you're suggesting most enterprises have infra-as-code that would allow them to switch their entire infra between vendors within a month.
Interesting you'd find that on a site called __open__ router.