dharmafi
8.1K posts
The current AI pricing was always going to go away | Arnon Shimoni, Arnon Shimoni The current AI pricing was always going to go away. It just doesn’t make sense. Microsoft canceled internal Claude Code licenses this week (for whatever reason, even if it’s because they integrated it), Uber blew its entire 2026 AI budget in four months, and GitHub is dropping flat-rate plans across its products. You’ll see the framing “the AI subsidy era is ending” which is a polite way of what everyone’s been doing when they slap AI features into every tier of their product on a bet that inference costs would keep falling. They didn’t and the cost curve is bending the wrong way, and the labs have no choice except to pass that along. Did we collectively forget second order thinking? Each model generation, costs per token did fall in theory, sometimes 10x less but that was for comparable quality… Lots of people extrapolated and built business models on the extrapolation, which… isn’t how you think about it. Second-order thinking anyone? Everyone who deals with road planning knows about is induced demand. Each new capability invents new demand. Highways are the textbook case. Add a lane, you get new commutes. The commutes weren’t there before the lane. AI is the same shape. Cheaper inference doesn’t reduce the bill, it expands what people ask the model to do. Now my reasoning queries take >4 minutes, where the old ones took 2m… Agentic workflows make 50 calls where the old workflow made one. Unit cost falls, units explode, but still the total spend goes up. Anyone selling a flat-rate “AI assistant” assumed user behavior wouldn’t change. It did. It always does. The second is that the supply side stopped cooperating – memory and GPU economics are moving against you. Memory got 4x more expensive. GPUs got >95% more expensive. Frontier training and inference run on Nvidia accelerators paired with high-bandwidth memory. The ceiling isn’t transistors anymore, it’s HBM and the advanced packaging that bonds it to the compute die. That ceiling is one factory deep. TSMC’s CoWoS packaging line is the bottleneck for accelerator supply. SK Hynix dominates HBM, with Samsung lagging and Micron behind that. None of them can add capacity overnight. These are 18-to-36 month commitments, minimum, and they were planned for a world that under-forecast demand by an order of magnitude. So GPU pricing is what scarcity pricing looks like. Top-end accelerators today are roughly 2x more expensive than the previous generation at comparable cluster scale. HBM prices have 4x’d in 18 months. Power and cooling are now real constraints in places nobody used to model power for, which is why every hyperscaler now has a “we’re building a gigawatt campus” story and a nuclear-PPA press release. Anthropic’s CFO testified under oath this March that the company spent $10 billion on compute and made $5 billion in revenue (Ed Zitron has the math). The labs are underwater on inference. They’re raising prices to keep the lights on. Companies that sold flat-rate AI-everywhere products are now sitting on a margin problem they architected themselves into. The bet was that one of these curves would bend in their favor. None of them did, probably none of them will, certainly not on the timeline their pricing assumed. What changes from here The product question shifts. It stops being “where can we add AI?” and starts being “which use cases earn the inference cost they burn?” That’s a harder roadmap to write. It also changes the pricing surface, which is the part most product teams haven’t internalized. Three architectures handle a moving cost. None of them are new. All of them are uncomfortable for sales teams that grew up selling seats. Per-action. Every API call, every generation, every agent step has a price. Revenue scales with cost because they’re indexed to the same underlying event. Twilio has run this since 2008. AWS has run a version of it since 2006. The downside is transparency cuts both ways. Customers see the meter, and they negotiate. The upside is your gross margin doesn’t depend on guessing how hard your power users will hammer the system. Credits. Prepaid buckets. Customer buys 100,000 credits, burns them down on whatever, refills. Credits smooth cash flow and let you mix model costs behind a single unit, which is the only sane way to handle a product that routes between five different inference providers. The trap is breakage. Snowflake credits are infrastructure, customers understand what they’re buying. Gift-card credits are stranded assets, and customers can tell which one they bought. You only get to do the second one once. Hybrid. Base seat with included credits and metered overage. Most enterprise sales motions accept this without flinching, because the seat number still anchors the contract and the meter is the safety valve. It’s the design most AI-native products converge to within their first repricing cycle. Not my favourite, but whatever, it tends to work. The shape isn’t the point by itself, but rather whether the line moves when the cost line moves. Per-seat is the one architecture that pretends costs are fixed. Everything else is some flavor of indexing revenue to the underlying event. The impossible choice If your pricing can move with cost, you get to keep building. You can ship the agentic workflow, the heavier reasoning model, the slow expensive feature for power users, and you have a way to be paid for them. If you’re locked into per-seat (or flat, or whatever) – you pick between two losing options. Eat the margin and watch it compress every quarter your customers’ usage grows. Or strip AI out of your cheaper tiers and watch your activation rate fall off the lower-priced cohorts that used to be your funnel. Both options are visible on the next board deck. Neither one of them looks fun. arnon.dk/the-current-ai…
@code Lines of code: 40M Linux kernel 15M GCC compiler 200K Entire plan9 operating system (kernel, compilers, networking, windowing system, commands)
@code Lines of code: 40M Linux kernel 15M GCC compiler 200K Entire plan9 operating system (kernel, compilers, networking, windowing system, commands)
Hey Andreas 🙋♂️ If someone said to you "you're to design a next generation browser with zero backwards compatibility with the existing web" do you have an idea of what that might look like? Would you take an approach where you basically just ship JavaScript and a canvas and leave everything to libraries? Or do you think you'd hardcode things like HTML, CSS, etc like we have today? Alan Kay famously criticized the design of browsers in his 1997 OOPSLA talk. It seems he hinted at more of the former design. tinlizzie.org/IA/index.php/A…
@LundukeJournal @ladybirdbrowser Browsers are too big for sure, but there’s only so much we can do with the mountain of stuff we get from websites 😅
@LundukeJournal @ladybirdbrowser @awesomekling Our social media should be decentralized and local first, allowing for bespoke clients l on any OS. x.com/dharmatrade/st…
Been grinding away at memory usage in @ladybirdbrowser over the last two weeks. Making some good progress! Here's how we do on my X profile page 1 month ago vs today:
@code 9social : A Social Network for Plan9
@chigrl @DFCgov Just wait until they start attacking the nuclear power plants in UAE... These are the first nuclear power plants in the middle east. They happen to be located conveniently across the Persian Gulf from Iran. CC: @PeterZeihan en.wikipedia.org/wiki/Barakah_n…
@nasqret I started messing around with a very simple simplifier (computer algebra) in Lean recently. github.com/dharmatech/sym…
@code Markdown folding in acme for plan9 This is a stock acme. Everything you see here is done via regular user defined commands.
This is not a joke, I am using now dwm with acme in my main computer. I will either achieve the Nirvana or go fully insane.
