Historically... this tends to work out. Reminds me of Gmail initially allowing massive inbox. YouTube doing free hosting. All the various untethered LAMP hosting...
If necessary they'll add an anti-abuse policy or whatnot to mitigate the heavy users.
The sophisticated modeling is basically "just get going" with a guesstimate and adjust if needed.
I doubt that pricing structure will sink any ships. It's going to be about utility.
One difference I see: storage capacity and compute performance aren't increasing like they had in the past, so companies can't rely on these costs to dramatically drop in the future to offset bleeding cash initially to gain market share.
[0] https://www.reddit.com/r/LocalLLaMA/comments/1gpr2p4/llms_co...
Companies stopped increasing free storage tiers ~10 years ago or even more, while the cost of storage has dropped significantly in that time period.
Both hard drives and SSDs.
But.. a lot of the other dynamics that make this game winnable still stand. Maybe they will need to go with a meter eventually or some other pricing structure... but it will work out.
Anyway I think that for the average developer (i.e. not enterprise customers) this is easier to reason about, so I am fine with that.
[1] https://www.jetbrains.com/ai-ides/buy/?section=personal&bill...
But yes, there should absolutely be ways to track usage, ideally before the prompt is even submitted for processing (maybe for >N tokens per query, where N can be specified in settings but has a reasonable default).
JetBrains are in a great position to do this though, perhaps the best position. Whereas a tool like Claude Code or Aider can give the LLM grep and little else [1], Junie can give the LLM a kind of textual API to the IDE's own static analysis database. If Claude/GPT want to understand what a function is doing and how it's used, it could issue a tool call that brings up nicely rendered API docs and nothing else, it could issue a tool call to navigate into it and read just the function body and so on. And they can use the IDE to check whether the code complies with the language rules more or less instantly without needing to do a full compile to pick up on hallucinated APIs or syntax errors.
So much potential with this kind of integration, all that stuff is barely the start.
[1] Aider attempts to build a "repo map" using a PageRank over symbols extracted by tree-sitter, but it never worked well for me.