OpenAI closes $122 billion round at $852 billion valuation, reports $2 billion monthly revenue

OpenAI has closed a $122 billion funding round at an $852 billion post-money valuation, according to a report on dev.to covering the company's March 31, 2026 announcement. The same announcement, as summarized in the post, says the company now brings in $2 billion in monthly revenue — roughly six times the quarterly pace of $1 billion it reported reaching by the end of 2024.

The scale of the numbers

Annualized, $2 billion a month implies a run rate of about $24 billion. The dev.to author notes that separate reporting put OpenAI at around $20 billion in annualized revenue during 2025, a figure consistent with continued rapid growth into 2026. The source is careful to distinguish revenue from profit, and to point out that neither the round nor the run rate says anything definite about future pricing, performance or product availability.

The announcement apparently offered no historical comparisons for the round size or the valuation, so the dev.to post presents them without prior benchmarks. Even in isolation, though, they combine two things that rarely travel together: evidence of commercial demand, in the revenue figures, and access to enormous capital, in the round itself.

What the money is meant to do

According to the post, OpenAI frames the funding as fuel for growth across consumer, enterprise and developer products, together with the compute and infrastructure needed to serve that demand. The company reportedly describes its compute and infrastructure scale as a strategic moat — a significant point for any organization whose workflows depend on AI services remaining available and capable enough for day-to-day use.

The shift is organizational as well as financial. Reporting from around March 2026 placed OpenAI's headcount at roughly 4,500 people, with further hiring planned during the year. Enterprise revenue is described as a meaningful and growing share of the business, on a path toward parity with consumer revenue by 2026.

What the round does not tell you

The dev.to post stresses that the announcement confirms no specific changes to prices, service levels or product features. Its advice to businesses is to avoid procurement decisions built on assumed discounts or capabilities, and instead to treat the funding as a signal: a large and growing commercial base, backed by a major capital commitment to infrastructure.

The practical suggestions it offers are worth restating. Pick a workflow where outcomes can be measured, decide where human review belongs, identify the data involved, and define the metric that shows whether the system actually helps — for instance, whether AI-assisted drafts cut production time without hurting editorial standards, or whether support summaries raise agent throughput without degrading answer quality. The post also flags risks that come with scale: dependency on a single provider with no fallback process, costs that climb as adoption spreads unmonitored, and the fact that fluent output is not the same as accurate output.

Why it matters

If the figures hold up, they mark a watershed in how the AI industry is financed. A $122 billion round is not a bet on an experiment; it is infrastructure-scale capital for a service that, at roughly $24 billion a year in revenue, already sits underneath a wide range of consumer and business activity. For developers and enterprises building on OpenAI's APIs, the round suggests the company can keep investing in capacity and capability, which matters for reliability and for the pace of product improvement.

The counterweights are concentration and discipline. A single provider with this much capital and revenue momentum will shape the ecosystem around it, from pricing norms to developer tooling, and customers who build deeply on one platform take on operational exposure if that platform changes. The dev.to post's conclusion is a reasonable one: read the news as a market signal about the maturity of AI infrastructure, not as a shortcut to an automation strategy. The return still depends on whether a specific use case delivers a measurable improvement over the process it replaces.