Hacker News new | past | comments | ask | show | jobs | submit
Switching models is easy as a solo developer. Switching LLM providers as a company is not, once all your employees have it integrated with GitHub, their IDE, etc. I think Anthropic will look a lot more like a cloud provider like AWS or GCP. Same-looking product, very high switching cost that would have to be driven at the CIO-level because of all the integrations that have to be redone, IP concerns etc. And ultimately they are selling compute capacity.

Edit: I should clarify that I don’t think this justifies their valuation. It puts them in competition with much more entrenched players with established customer bases, and who aren’t in massive debt to provide their compute. I’d also like to distinguish between a model provider as someone who provides weights vs a model provider who connects their GPUs and models to your codebase and internal systems - I think the latter is where the sustainable business is.

Incidentally this is why I still feel Google is well-positioned in the long-term AI race. If they can remove their head from their ahh and make a coherent product offering across Workspace, GCP and Gemini, they could become as entrenched as MS.

I would assume AWS is probably the most interested in acquiring Anthropic out of the three major cloud providers.

> Switching LLM providers as a company is not, once all your employees have it integrated with GitHub, their IDE, etc

I don't think this is entirely true. Companies are deploying open-source LLM gateways to be able to do that very easily now. Today, you can switch Claude CLI to any model besides Anthropic via https://github.com/BerriAI/litellm and there are major companies doing that.

This works with your favourite ADEs such as Orca as well so I disagree with this premise. The whole experience of switching is pretty seemless based on personal experience.

We saw this play out in the cloud era, notably with OpenStack. Even through the core abstractions (chat for LLMs, compute and storage for clouds) can be almost perfectly abstracted over, providers will race to add niche, enterprise-y features that are harder and harder to put behind a gateway or proxy. Those features aren't the core value of the platform but they are important enough to create lock in.
loading story #50476208
Agreed, deploying AI gateways has become extremely common in enterprise settings. A lot of admins think they are going to use it for guardrails, but I think the real value is in centralized cost tracking and ability to (relatively) seamlessly aggregate providers.
loading story #50470953
We have like a dozen different LLM tools available to us and it's as easy as clicking on a dropdown to switch in every single one of them, and we have several thousand employees. Self-hosting with the cheaper OSS models is also becoming more and more attractive for larger orgs.
That's just inference. Claude.ai is a platform that enterprise IT teams connect up to all kinds of other applications, and gets use beyond the claude code CLI. Non-developers get used to this functionality - whether it's their form-building stuff, artifacts, slides/presentations, etc... they're building an offering far beyond just inference. I agree the latter is a commodity now, though companies will compete on privacy options (ZDR, guaranteed confidentiality, etc)
loading story #50467495
Similar at my $(dayjob) and can confirm.
Working for a 10k+ corporate and we made it pretty easy to switch to any provider, people here can use Anthropic's, OpenAI's, and our own self-hosted open weight models very easily. It's one drop-down or `/` command away to switch between them.

I think other companies are probably doing the same, the moat of a AWS/GCP/Azure is much deeper with how contrived it is to migrate between them even if you abstract as much as possible with something like Kubernetes.

Interesting, I don’t think that’s incredibly common but that’s certainly not good news for them. And also not great for OpenRouter.
loading story #50469671
loading story #50467545
Openrouter was acquired by stripe, I'm sure they're not worried.
> Switching LLM providers as a company is not, once all your employees have it integrated with GitHub, their IDE, etc

Once the cost reaches a threshold, everything is doable. We ditched Datadog in less than a month. Someone I know had their company ditch slack in a quarter and google cloud usage of 100+ million in two. Everything is doable.

It probably took years to get there. Furthermore, it sounds like an anomaly.

I think when something becomes a management-level item in an org, like AI, it is a hard thing to switch unless it becomes a management-level problem.

Most of the orgs are responsible for this and will do whatever it takes politically or not, to justify the decision unless management overturns it.

loading story #50471070
{"deleted":true,"id":50469701,"parent":50469553,"time":1794499811,"type":"comment"}
> Switching LLM providers as a company is not, once all your employees have it integrated with GitHub, their IDE, etc.

I'm not so sure about this. I guess it depends on how well people did their job there.

Ideally, whatever people built is loosely coupled to that third-party resource, meaning that switching cost will stay low.

After all, it's probably just prompts + an API layer. Unless one micro-optimizes their prompts for claude (which then breaks once a new checkpoint drops, hence is a bad idea regardless), pointing them towards a different API endpoint should be doable.

Currently we are building agentic systems for various business functions like Legal and Finance. How these models perform in those tasks is paramount, and things like cost per run is only a part of the equation. It can become very subjective, and things like brand recognition comes into play. The cost of a counsel or a VP finance overshadows the savings you get by micro-optimizing for a cheaper model. We tend to use the best-in-breed LLM for the various tasks - mainly Claude and Gemini, and sometimes GPT.
loading story #50467111
loading story #50469817
loading story #50468114
loading story #50468151
> I guess it depends on how well people did their job there.

Given that the goal of the whole project is outsourcing the work, what are you expecting here?

Switching LLM providers as a company is not, once all your employees have it integrated with GitHub, their IDE, etc.

Speaking as someone who has been at professionally this since the 1980s, I suggest that while sometimes switching costs and network effects happen "organically," in this century businesses devote enormous amounts of attention to artificially building switching costs.

It's such a dirty practice that we have a four-letter word for it, a "moat." But of course, the moat isn't really to keep competitors out of a market, it's actually to keep customers trapped within it.

I fully expect every one of these AI providers to put as much work into trying to trap their customers within their ecosystem that they do to improve their capabilities.

LLMs make it easier to bypass the moat, too. They can automate migrations, etc. pretty smoothly.

(Since we're talking about moats and cyber-feudalism, where does siege warfare come in?)

loading story #50469773
they haven't really done that so far. no offense but LLMs didn't exist in the 80. or 90. or 6y ago. and I'm just as old as you.
loading story #50470348
I think you'd be surprised. I've seen orgs entirely switch fundamental tech choices to save 10%.

Once they realise that you can use Deepseek / GLM for 10% of the cost these labs are done.

Exactly, model itself is commodity, and integration is also not a moat because AI can code integrations with a prompt.
My company switched from direct access with providers to AWS Bedrock. Now we just pick which model we want from the list exposed by Bedrock. We can also leverage tools like T3 which allow hand off from one model to another.
Are you using AWS AI-DLC?
One thing that makes easier to switch with LLMs as opposed to other tech is the text-in text-out nature of the LLMs. All specs and data are in text files mostly in natural language which is patent free. This makes it harder to lock in content.

As you have written, the agentic harness is a slightly different matter with plugins and features. But the core tech makes replicating software a lot easier so you can in principle use an agent to make it easier to switch from its own harness. There are caveats to this since in practice the quality and feature sets of harnesses are not the same. But in my opinion, it is far easier to switch agents than switching other tech that came before them that used proprietary formats and apis to lock you in.

Model switching behavior is going to be far more complicated.

First, everyone and their mom is selling AI now. It is being bundled in nearly every product. Buy CRM to run your company - they will upsell you their bespoke AI - mostly RAG/chatbot using the data inside the platform. This is an important area because today lot of companies are trying to build their own AI bespoke workflows. But companies like SAP, Oracle will spend money on improving this aspect. And people who buy/use AI for this purpose don't care if the underlying AI is Claude or not.

Then there are cloud providers. You can get Claude, OpenAI from AWS Bedrock etc. They will take the heavy lifting of changing integrations, IP concerns etc to keep people on their platform. With time expect them to make it even easier, not harder to switch models. Also, they will push for open source models because it will be more profitable.

Lastly buying from direct providers. This is here the lock in comes in. But I believe fewer and fewer enterprise will buy directly - many preferring to buy against their cloud commitments.

It's trivial to switch. The company I work for has 1k employees has already switched like 3 times in the last two years.
Are they really switching when so many docs, diagrams and info is stored inside Claude Design, Whiteboard and meetings?
loading story #50469230
loading story #50469945
loading story #50468491
This is the logic behind B2B SaaS's revenue multiples, and yet AI itself is causing those multiples to rerate based on a change in expectations about the durability of an entrenched SaaS provider.
Given how unreliable these models still are and how fast everything changes i suspect switching is not that painful even for larger orgs
| Switching LLM providers as a company is not

I really think you overestimate the level of lock in here. If a companies tells the devs to use X because it cost 1/10 of the price they will just have to suck it up and switch.

I didn't particular want to work on a "all in agentic project" but that the nature of being employed.

The same LLM we use day to day will make it trivial to switch out providers in our infrastructure.

My F500 company switched ~10k employees of Claude to copilot in 30 days. Google did similar between Jetstream and Claude. The moat just isn’t there right now
Copilot lets you use Claude models though.
loading story #50469816
With some gateway inbetween managing the model responses, MCP and skills (see https://modelcontextprotocol.io/seps/2640-skills-extension) this becomes very easy
I think the future will be a lot different they we expect, AI is going to be the infrastructure layer while there will be toolings for each processes, so switching between model is a built-in feature, i.e. the tools will inject specific prompt or context based on the models, and all these are designed by people selling the tools, hence, a moat?
Let's say that the face for largest foundation model slows down enough to make the companies cloud-like, instead of whatever they are mow. Imagine the free credits that OpenAI would consider giving you as long as they are spent on migration out of Anthropic. They could even classify conversations by themselves.
VS code or other ides with multiple providers makes it pretty easy.

Also for larger companies like Amazon the danger is they replace Anthropic completely with self-hosted models.

for us (200+ people) switching was a single prompt
This is why you recommend tools like OpenCode or OpenClaw that commoditize that layer.

I am really surprised that companies who are worried about AI spend don't try that route.

Depending on how the company leverages them, it's super easy.

For us it's as easy as clicking a dropdown. The copilot vs code extension allows for this ez pz, the same is true for companies that implement an AI gateway for other tooling.

Integrations with Github and IDE are nothing. It's like changing your email software.
When was the last time your company changed email provider?
loading story #50468104
loading story #50467059
Totally agree with your Google thesis. I would never count them out. I say that as someone that uses Claude (and a little chatgpt), but not Google's AI at the moment.
With ad money Google never had to learn how to ship a product that makes money. An obvious place they fail is that when something breaks there's no one to talk to to fix it.
{"deleted":true,"id":50466910,"parent":50466721,"time":1794490709,"type":"comment"}
Switching LLM providers as a company is even easier than a solo developer, most large companies I know are using AWS Bedrock and selecting another model is basically just a checkbox for them
As far as I know, our corporate has deals with all of them: Anthropic, OpenAI and GitHub Copilot.

They stroke a great discount deal with all, so different teams/departments have different provider, and those using Copilot are even free to switch between models as they please (although with lower usage limits).

You could make the argument that it's not worth switching SAAS providers for enterprises when the costs were like 10 dollars a month per developer and switchign would require 1 team to work for half a year... but with AI providers it's more like paying 1000 dollars a month per developer vs paying 200 dollars if you strike a good deal with different provider and swtiching costs are more like 4 to 8 hours of work for each developer.

I guess what I’m saying is that means AWS is their provider then
loading story #50466790
Or LiteLLM and switching providers is just super easy.
nah it's pretty easy.

it's easier than changing okta

it's easier than changing google docs and even Gmail

it's easier than migrating cloud

etc.

and we're talking several magnitudes easier too!

What?

Have you used Copilot at a company?

I can literally change my model in 3 seconds.

The moat is as shallow as it gets. Investing in a single LLM provider at the moment would be a mistake.

I've observed that there are some companies and some folks that are very fanatical about a specific provider. "Only Claude" is very common. "Only GPT" less common, but still see it.

A lot of the non-technical and semi-technical folks are only comfortable using a specific client like the Claude desktop app. A lot of teams wrote skills and eval'd/benchmarked their skills specific to a model family and harness.

The "I can use any model, any harness" or "I only use a meta harness" (Orca, Paseo, Herdr, etc.) crew is relatively small IRL. Most people are still single-session, single platform user mode.

Most orgs have an enterprise contract with a single provider so all of their internal assets are built for the provider. It goes beyond skills, but also the telemetry, enterprise policies, and managed configuration.

loading story #50467688
loading story #50469069
loading story #50467647
loading story #50468040
Actually LLMs themselves make changing LLM provider or harness a non-issue, in my experience.
A gateway like GoModel can make switching transparent, along with the many other benefits you get with a gateway.
It’s literally a menu in Copilot.

The model is just some REST endpoint you switch out even in a lot of enterprise setups.

It’s weird that people don’t seem to get this. LLMs are the most easily switched-out technology I’ve ever used as an engineer. The input is literally just free-form text.
loading story #50467783
loading story #50470040
If only there was a tool that could automate the switch/transition from one LLM to another...
{"dead":true,"deleted":true,"id":50470442,"parent":50466721,"time":1794502753,"type":"comment"}