惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
腾讯CDC
IT之家
IT之家
罗磊的独立博客
酷 壳 – CoolShell
酷 壳 – CoolShell
U
Unit 42
爱范儿
爱范儿
博客园 - 聂微东
F
Fortinet All Blogs
V
Visual Studio Blog
Blog — PlanetScale
Blog — PlanetScale
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
L
LangChain Blog
雷峰网
雷峰网
B
Blog RSS Feed
宝玉的分享
宝玉的分享
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Engineering at Meta
Engineering at Meta
H
Hackread – Cybersecurity News, Data Breaches, AI and More

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Anthropic Is Now the Most Valuable AI Startup. Here's the...
Conor Dobbs · 2026-06-12 · via DEV Community

Conor Dobbs

on may 28 anthropic announced a $65 billion series h round at a post-money valuation of about $965 billion, which makes it, on paper, the most valuable ai startup in the world. the round was led by altimeter capital, dragoneer, greenoaks and sequoia, on top of earlier hyperscaler commitments that included around $15 billion with $5 billion of it from amazon. the headline everyone ran with is that anthropic passed openai. that part is true, but the comparison is messier than the headline, and the more interesting story is what is generating the number.

i build small dev tools and write comparison content, and a lot of what i ship runs on top of anthropic's models. so when the company that makes the tools i depend on nearly touches a trillion dollars, i do not read it as a sports score. i read it as a question about whether the thing i am betting on is durable, and what i should do differently because of it. here is the honest version of both.

the number, with the caveats intact

the $965 billion figure is consistent across cnbc, axios, morningstar, al jazeera and euronews, so i trust it. what i would not do is state the gap over openai as a precise fact, because the sources do not agree on openai's number. axios pegged openai's most recent valuation at $730 billion. other outlets put it closer to $850 billion off a record round earlier in the year. either way anthropic is ahead right now, but "ahead by $115 billion" and "ahead by $235 billion" are different sentences, and anyone quoting one as gospel is rounding away the uncertainty. the safe claim is the one i will make: as of late may 2026, anthropic is the most valuably-priced private ai company, and it got there fast. the reporting has it roughly tripling from a $380 billion mark in february.

the part that matters more to me is the revenue. anthropic crossed a $47 billion run-rate earlier in may. that is the line that turns a valuation from a vibe into something with a floor under it. you can argue about whether $965 billion is the right multiple on $47 billion of run-rate revenue, and reasonable people are arguing exactly that. but a $47 billion run-rate is not a story about hype. it is a story about a lot of people paying for something every month.

what is generating it, from where i sit

the reporting attributes a large share of that demand to coding. i cannot give you anthropic's internal revenue breakdown, and i am not going to pretend i can. what i can tell you is what i see at my own small scale, because it lines up. the work that has moved from "interesting demo" to "i pay for this and would be annoyed to lose it" is almost all coding work. claude code sitting in a terminal, reading a real repo, making edits across files, running the tests, is the first version of this category that survived contact with my actual day. the chat-window version was a toy. the agent-in-the-repo version is a tool.

their cfo, krishna rao, framed the raise as helping them "serve the historic demand we are experiencing" and "bring claude to more of the places where work happens." that is corporate-speak, but the second half is the real strategy. the value is not the chat box. it is claude showing up inside the editor, the ci pipeline, the terminal, the places work already happens, so you do not context-switch to use it. that is also, not coincidentally, where the willingness to pay lives. people will expense a tool that closes prs. they will not expense a clever paragraph.

the part the headline skips: this is a platform-dependence story

a valuation headline never says this part out loud. when one company's models become the substrate under a lot of small businesses, including mine, the small businesses are now exposed to that company's roadmap, pricing, and priorities. i felt this directly a few weeks ago when microsoft pulled internal claude code licenses and moved staff to its own tooling. one large customer's procurement decision rippled out as news for everyone building adjacent to the same stack. a $965 billion valuation does not insulate you from that. if anything it raises the stakes, because the pressure to monetize a number that large eventually reaches your invoice.

i am not bearish. i keep building on this stack because right now it is the best version of the tool for the work i do. but i hold it the way you should hold any dependency you do not control. i keep my prompts and my workflows portable enough that the value lives in how i work, not in one vendor's api shape. i pay attention to the providers moving toward open models and cli-first interfaces, because optionality is cheap to maintain and expensive to acquire after you need it. and i treat the model as a component, not a religion.

what i would do with this news

if you are a developer reading the valuation headline, the useful takeaway is not "anthropic won." it is that the coding-agent category is now large enough to fund a near-trillion-dollar company, which means it is not a fad and it is worth getting genuinely good at. the gap i see in practice is not access to the model. everyone has that. the gap is the operating knowledge: how to configure claude code so it reads your codebase instead of guessing, how to structure a claude.md so the agent behaves consistently, when to reach for subagents, how to wire mcp and skills without drowning the context window, and how to review what it produces so you are not shipping the plausible-looking bugs it is happy to write.

that operating knowledge is the actual moat for an individual developer in this cycle, far more than which model is briefly on top. the valuation will move again next quarter. the skill of driving the tool well compounds.

if you want the concrete version of that, the config patterns, the claude.md rules, the subagent and mcp setups, and the review habits, i collected the ones i use into the claude code cookbooks. and if you like these teardowns, i write more of them at tools.thesoundmethod.me.