Home Blog Page 2

Google Was Supposed to Lose the AI Race. It Just Hit an All-Time High.

Alphabet logo against a backdrop of rising stock charts and AI infrastructure imagery

Two years ago, the consensus on Wall Street and in Silicon Valley was straightforward: Google was toast. OpenAI had the models. Microsoft had the distribution. ChatGPT had the cultural moment. Alphabet, bloated and slow, was watching its core search business get eaten alive by something it had helped invent.

That story turned out to be wrong. Spectacularly wrong.

Alphabet stock is up approximately 160% over the past year. On May 8, 2026, the company hit an all-time high. For a brief moment in after-hours trading this week, it surpassed Nvidia to become the world’s most valuable company. The company everyone wrote off as the first casualty of the AI revolution is now being described by JPMorgan as its “top overall pick” in all of tech.

So what actually happened?

Google Didn’t Lose the AI Race. It Changed the Game.

The narrative in 2023 was about chatbots and language models. In that frame, Google was behind. Its Bard launch was embarrassing. Its AI Overviews served up misinformation. The company looked like it was playing catch-up on someone else’s terms.

What the narrative missed was that Google was never just competing on models. It was competing on the stack.

Gene Munster, managing partner at Deepwater Asset Management, put it plainly after last week’s Q1 earnings: “Google is one of the two best-positioned AI companies because they own most of the stack. Chips, models, infrastructure and distribution. On top of that, they’re nicely profitable.”

That stack includes Gemini for frontier AI models, custom Tensor Processing Units (TPUs) as an alternative to Nvidia’s GPUs, Google Cloud for enterprise compute, and Google Search, YouTube, and Android as distribution channels that touch billions of users daily. No other company outside of a speculative case for Microsoft can claim all four layers simultaneously.

The Q1 2026 numbers reflect exactly this. Google Cloud revenue surged 63% year over year to $20 billion, crossing that threshold for the first time in the company’s history. Cloud operating income more than doubled. The contracted backlog nearly doubled sequentially to $462 billion, with over half expected to convert to revenue within the next 24 months. Search revenue grew 19%. Net income for the quarter hit $62.6 billion, up 81% year over year.

These are not the numbers of a company that lost.

Also Read: The AI Browser War. Where is Google?

The Tension the Market Is Not Fully Pricing In

Here is where the story gets more interesting than a simple vindication narrative.

A significant portion of that $462 billion cloud backlog traces back to a single customer. Anthropic, the AI company behind the Claude model family, has reportedly committed to spending $200 billion on Google Cloud over five years. If accurate, that commitment represents more than 40% of Alphabet’s entire contracted cloud revenue.

Google is simultaneously one of Anthropic’s largest investors and its largest infrastructure customer. The capital flows in a circle: Google invests in Anthropic, Anthropic uses that capital to pay Google for cloud compute, and Google books it as backlog growth. Analyst Gil Luria at D.A. Davidson described it bluntly: “They did it the same way Oracle did. They told us their backlog roughly doubled without telling us that almost the entire increase came from one deal with Anthropic.”

This is not necessarily a scandal. It may simply be how the AI economy works at scale. But it does mean that Google’s cloud growth story is, in part, a story about the circular economics of AI funding rather than pure organic enterprise demand. If Anthropic stumbles, raises less capital, or shifts infrastructure providers, Google’s backlog takes a meaningful hit.

What This Means for the AI Industry

The broader lesson here is about what the AI race actually rewarded. It did not reward whoever shipped the most impressive demo in 2023. It rewarded whoever controlled the underlying infrastructure at scale, had the balance sheet to sustain a multi-year capital investment cycle, and had existing products through which to distribute AI at zero marginal cost.

Google had all three. The threat from OpenAI, paradoxically, accelerated Google’s internal transformation rather than defeating it. Sundar Pichai noted on the Q1 earnings call that the company’s AI investments and “full-stack approach” are driving performance across every business line, with first-party models now processing more than 16 billion tokens per minute via direct API access, up from 10 billion the previous quarter.

Alphabet is also spending aggressively to protect this position. Full-year 2026 capital expenditure guidance stands at $180 billion to $190 billion, an extraordinary figure that reflects both the scale of infrastructure demand and the company’s confidence in its ability to convert that demand into revenue.

The company that was supposed to be disrupted by AI now sits at the center of the AI economy. The question worth asking is not whether Google won. It is whether that level of stack dominance is good for the industry that feeds off it.

Advertisement

OpenAI GPT-Realtime-2 Brings GPT-5 Reasoning to Voice Agents

OpenAI logo on a dark background with waveform visualization representing real-time voice AI

OpenAI just made its most significant voice AI upgrade since launching the Realtime API. On May 7, 2026, the company released three new audio models through its API: GPT-Realtime-2, GPT-Realtime-Translate, and GPT-Realtime-Whisper. The headline is GPT-Realtime-2, which brings GPT-5-class reasoning into real-time voice conversations for the first time. This is not a consumer product update. It is a developer infrastructure release, and it changes what is now possible to build.

What GPT-Realtime-2 actually does differently

Every previous voice model from OpenAI operated in a call-and-response pattern. A user speaks, the model responds, and the cycle resets. GPT-Realtime-2 breaks that pattern. It can hold context, use tools mid-conversation, recover from errors, and handle genuinely complex requests without losing track of where the conversation is going.

Read More: AI Made Cyberattacks Faster Than Patches

The context window has expanded from 32K to 128K tokens, which means a voice agent can now carry much longer conversation histories without losing context. Developers can also tune reasoning effort on a spectrum from minimal to “xhigh,” trading latency for depth depending on the task. The model supports parallel tool calls, meaning it can query multiple systems simultaneously rather than waiting for each step to complete. These are not cosmetic improvements. They are the architectural changes that make voice agents viable for enterprise workflows rather than just demos.

Pricing for GPT-Realtime-2 is $32 per million audio input tokens, with cached input tokens at $0.40 per million, and $64 per million audio output tokens.

The translation and transcription models

GPT-Realtime-Translate handles live multilingual voice products. It accepts speech input in over 70 languages and produces output in 13 languages, managing regional pronunciation, context shifts, and domain-specific vocabulary in real time. This positions it for use cases like cross-border customer support, multilingual sales calls, live event translation, and media localization. Pricing is $0.034 per minute.

GPT-Realtime-Whisper delivers streaming speech-to-text. Unlike traditional transcription that processes audio after the fact, it converts speech to text as the person speaks. Use cases include live captions, healthcare documentation, recruiting calls, and meeting notes workflows. Pricing is $0.017 per minute.

Who is building with it

OpenAI has confirmed several early enterprise deployments. Zillow is using GPT-Realtime-2 for real estate voice agents. Deutsche Telekom is deploying it for multilingual customer support. Priceline is integrating it for travel assistance. Vimeo is using the translation model for live video localization. The customer list signals where the revenue opportunity is: large enterprises with high-volume, voice-heavy workflows that could not previously be automated reliably.

Why this matters beyond the product launch

The voice AI market has been waiting for reasoning to catch up to fluency. Models could sound natural but could not think well. GPT-Realtime-2 is OpenAI’s answer to that gap. By bringing GPT-5-class reasoning into the voice layer, the company is making a clear argument: the same intelligence that drives its text agents should now be accessible through spoken language.

That shift has real implications. Voice interfaces are the most natural human-computer interaction pattern that exists. If the reasoning layer is now strong enough, the adoption ceiling for voice AI in enterprise applications rises significantly. The question is no longer whether voice agents can handle complex tasks. With GPT-Realtime-2, OpenAI is arguing that they can.

Advertisement

AI Made Cyberattacks Faster Than Patches. Mandiant’s Data Proves It.

A digital clock counting down to zero against a dark cybersecurity-themed background, representing the collapsing time window between vulnerability disclosure and exploitation

The assumption that defenders can patch before attackers strike no longer holds. Mandiant’s M-Trends 2026 report, grounded in over 500,000 hours of frontline incident investigations conducted in 2025, puts a number on what many security teams have been feeling: the mean time to exploit a vulnerability has dropped to negative seven days. Attackers are not waiting for patches. They are deploying exploits before patches exist.

That is not a marginal shift. It is a structural reversal of how the entire vulnerability management model was designed to work.

What the Mandiant Report Actually Found

The M-Trends 2026 report, published by Google Cloud’s Mandiant team in March 2026, tracks adversary behavior across real breach investigations, not simulated environments. The findings reveal a threat landscape that has changed faster in the last two years than in the previous decade.

The AI exploit window has gone negative at the macro level, but the specifics inside the report are equally alarming. The median dwell time for cyber espionage groups now sits at 122 days. The window between an initial access event and a ransomware hand-off collapsed from more than eight hours in 2022 to just 22 seconds in 2025. Exploits remained the most common initial infection vector for the sixth consecutive year, accounting for 32% of intrusions.

These numbers describe a threat environment where the standard playbook, detect, notify, patch, verify, has become too slow to be effective.

AI Is the Accelerant

The Mandiant report is careful to note that 2025 was not the year AI directly caused most breaches. The underlying failures remain human and systemic. But AI has compressed the timelines around every stage of the attack lifecycle in ways that compound those failures.

Adversaries are using AI to accelerate reconnaissance, generate convincing phishing content, write functional malicious code, and adapt tactics mid-execution. Mandiant researchers identified malware families that actively query large language models during execution to evade detection. One credential stealer was observed scanning compromised machines for local AI tools and using them to search for configuration files.

The practical result is visible in the data on malicious packages. According to Sonatype’s State of the Software Supply Chain 2026 report, malicious packages in public repositories grew from 55,000 in 2022 to 454,600 in 2025. The sharpest jumps corresponded with GPT-4’s release in 2023 and the agentic coding boom of 2025. AI-generated code is now sophisticated enough to pass static analysis tools and signature scanners that organizations have relied on for years.

The Skills Gap Has Closed on the Wrong Side

One signal that cuts through the noise: attackers no longer need technical expertise at scale. In February 2025, three teenagers with no coding background used an LLM to build a tool that targeted Rakuten Mobile’s system more than 220,000 times. In July 2025, a single actor using agentic AI tools conducted an extortion campaign against 17 organizations over one month, automating code development, data analysis, and ransom communications. In December 2025, another individual used AI coding tools to breach more than 10 Mexican government agencies and exfiltrate over 195 million taxpayer records.

The AI exploit window going negative is one dimension of the problem. The other is that the population of people capable of conducting sophisticated attacks is expanding rapidly, because the technical barrier has collapsed.

What Defenders Are Up Against

The Mandiant report notes that 45% of vulnerabilities in systems maintained by large companies with more than 1,000 employees are never remediated. The average time to remediate a high or critical severity vulnerability is 74 days, according to Edgescan’s 2025 Vulnerability Statistics Report. Set those numbers next to a mean time to exploit of negative seven days, and the gap is not a few weeks. It is structural.

Organizations that continue to treat vulnerability management as a patch-and-pray exercise are operating on assumptions the data has invalidated. The speed of AI-assisted attacks has outpaced the speed of human-led defense, and the gap is widening.

The Mandiant report frames one path forward clearly: stop trying to outrun attacks on every front. Eliminate entire categories of vulnerability instead. Reduce the attack surface so that the speed advantage attackers hold applies to a smaller target.

That is a harder strategic shift than it sounds. But the alternative is continuing to defend with a model built for an era when attackers needed weeks to develop an exploit, not days, and sometimes not hours.

Read the full breakdown on analyticsdrift.com for a deeper look at the M-Trends 2026 findings and what they mean for AI-adjacent teams. Read the full breakdown → [URL]

Advertisement

A Startup Just Broke the Transformer Scaling Law

Dense orange quadratic transformer attention grid versus sparse blue linear SSA attention network, illustrating Subquadratic SubQ's efficiency breakthrough

Every major AI model you use today is built on the transformer architecture. And every transformer carries the same structural cost: as context length grows, compute scales quadratically. Double your input, quadruple your cost. This is not a product limitation. It is a fundamental property of how transformers work, and the entire industry has spent years building workarounds rather than fixing the underlying problem.

On May 5, 2026, a startup called Subquadratic claimed to have fixed it.

The company launched SubQ 1M-Preview, the first large language model built on a fully sub-quadratic attention architecture. The Subquadratic SubQ linear scaling LLM runs on a mechanism called SSA, Subquadratic Sparse Attention, and the core claim is that compute now scales linearly with context length. At 1 million tokens, SubQ achieves a 52.2x prefill speedup over standard dense attention and a 62.5x reduction in attention FLOPs compared to standard quadratic attention.

The company raised $29 million in seed funding from investors including Javier Villamizar of Vision Fund, Justin Mateen (co-founder of Tinder), and early backers of Anthropic, OpenAI, Stripe, and Brex. The team of 11 PhD researchers comes from Meta, Google, Oxford, Cambridge, ByteDance, Adobe, and Microsoft.

Also Read: What the $26.6B Nasdaq Listing Means for AI Chips

Why the transformer’s quadratic scaling problem has resisted a fix

In a standard transformer, every token in a prompt compares itself against every other token to determine what to attend to. If you have 1,000 tokens, that is 1,000,000 comparisons. At 10,000 tokens, it is 100,000,000. At 1 million tokens, the compute becomes prohibitive. Cost does not grow with the input. It explodes with it.

This is why most AI workflows are built around workarounds. RAG systems retrieve small chunks of relevant text instead of feeding entire documents. Agentic pipelines break large tasks into smaller model calls, compressing and losing context at every boundary. Developers spend more engineering time on scaffolding, chunking strategies, retrieval pipelines, prompt compression, than on the actual problem they need to solve.

The research community has attempted sub-quadratic attention mechanisms for years. Every prior approach made a tradeoff that the industry considered unacceptable. Fixed-pattern sparse attention reduces compute but routes attention based on position, not content. When the relevant information sits outside the fixed pattern, the model cannot see it. State space models and recurrent architectures achieve linear scaling but compress context into a fixed-capacity state, degrading exact retrieval as sequence length grows. Hybrid architectures retain dense attention layers for retrieval and efficient layers for cost, but the dense layers remain load-bearing. As context grows, their quadratic cost still dominates.

The open problem was precise: build a mechanism that is efficient, content-dependent, and capable of retrieving from arbitrary positions across long context. That is what SSA Subquadratic Sparse Attention is designed to do.

How SSA works

SSA changes how attention work is allocated. Instead of comparing every token against every other token, it uses content-dependent selection. For each query, the model identifies which positions in the sequence actually carry signal and computes attention exactly over those positions, skipping the rest.

Dense attention assumes every pair might matter and evaluates all of them. In practice, the vast majority of pairwise interactions carry negligible signal, but the model still pays the full quadratic cost to compute them. SSA removes that assumption. It does not approximate attention. It restricts attention to the positions that actually matter, based on meaning rather than position.

This gives SSA three properties that matter together: linear scaling in compute and memory, content-dependent routing regardless of where relevant information sits in the sequence, and exact retrieval from arbitrary positions rather than compressed or blurred context.

The speedup compounds as context grows. Measured against FlashAttention on B200s, SSA achieves a 7.2x input processing speedup at 128K tokens, 13.2x at 256K, 23.0x at 512K, and 52.2x at 1 million tokens. The mechanism becomes more advantageous exactly where long-context workloads become most valuable.

The benchmarks

The Subquadratic SubQ linear scaling LLM published third-party verified results across three benchmarks.

On RULER at 128K tokens, a standard long-context reasoning benchmark covering multi-hop retrieval, aggregation, and variable tracking, SubQ scores 95.0%. Claude Opus 4.6 scores 94.8%. The models are effectively at parity.

On SWE-Bench Verified, which tests real-world software engineering on actual GitHub issues, SubQ scores 81.8%. Claude Opus 4.6 scores 80.8%. Gemini 3.1 Pro scores 80.6%. Claude Opus 4.7 leads the field at 87.6%, but SubQ holds its own against the previous generation of frontier models.

The most revealing result is MRCR v2, the hardest long-context retrieval benchmark. It tests the ability to locate and combine multiple non-adjacent pieces of evidence distributed across a large document, which is the closest proxy to real enterprise workloads. SubQ scores 65.9%. GPT-5.5 scores 74.0%. Claude Opus 4.6 leads at 78.3%. Claude Opus 4.7 and Gemini 3.1 Pro fall below SubQ at 32.2% and 26.3% respectively.

One figure worth tracking: Subquadratic’s research model scores 83 on MRCR v2, a 17-point gap above their production model. The company discloses this openly. A full technical report and model card are forthcoming.

The economics of linear scaling

Subquadratic prices SubQ at one-fifth the cost of leading frontier models. At the 12 million token context window model their research targets, attention compute drops nearly 1,000x compared to standard transformer models.

The implications for enterprise workloads are direct. Reasoning over entire codebases, full contract libraries, months of operational logs, and long-running agent sessions are currently cost-prohibitive or require elaborate scaffolding to manage. If the sub-quadratic attention mechanism AI performs as described at that scale, those workloads become economically viable without workarounds.

The company is offering access through two products. An OpenAI-compatible API for developers and enterprise teams, and SubQ Code, a coding agent that plugs directly into Claude Code, Codex, and Cursor. SubQ Code is designed to handle token-heavy context tasks at a claimed 25% lower cost and 10x faster codebase exploration.

What this means for the industry

The transformer quadratic scaling problem solved by a seed-stage startup carries an uncomfortable implication. Every major lab, OpenAI, Anthropic, Google DeepMind, has known about this ceiling for years. The fact that none of them shipped a production sub-quadratic model is either evidence that the problem is genuinely hard to solve without sacrificing accuracy, or evidence that their existing transformer investments create complicated incentives to replace the architecture.

A $29 million seed company claiming to have done what frontier labs have not demands scrutiny proportional to the claim. The full technical report is still pending. The gap between the research and production MRCR v2 scores is real and worth watching across future evaluations. Peer review has not yet arrived.

What is not in question is the significance of what they are claiming. If the Subquadratic SubQ linear scaling LLM scales as advertised, if 12 million reliable and efficient tokens become a production reality, the entire scaffolding layer of modern AI development becomes unnecessary overhead. The question is not whether the problem is worth solving. It is whether Subquadratic has actually solved it.

Advertisement

Cerebras Systems IPO: What the $26.6B Nasdaq Listing Means for AI Chips

Cerebras Systems WSE-3 wafer-scale chip on a circuit board with Nasdaq IPO ticker CBRS displayed on a screen in the background

Cerebras Systems filed, on 4th May, updated IPO terms with the SEC, targeting up to $3.5 billion in a Nasdaq listing at $115 to $125 per share. At the high end of that range, the Sunnyvale-based AI chipmaker would be valued at $26.6 billion when it prices under the ticker CBRS on May 13. It would be the largest tech IPO of 2026 so far, and the most significant public market test of whether investors are willing to fund a serious Nvidia alternative.

The Cerebras Systems IPO has been a long time coming. The company first attempted to go public in 2024 before withdrawing its paperwork as it pivoted away from selling hardware directly toward running its own cloud infrastructure. That restructuring turned out to be the right call. It returned to file an S-1 in April 2026 with a fundamentally different financial profile: $510 million in Q4 2025 revenue, up 76% year over year, and $87.9 million in net income for the same period.

What the Cerebras Systems IPO Is Actually About

Cerebras is not a GPU company. It builds wafer-scale chips, processors that occupy an entire 300-millimeter silicon wafer rather than the small individual dies that Nvidia stacks and connects in GPU clusters. The flagship WSE-3 is physically 57 times larger than Nvidia’s H100 and carries 2,625 times more memory bandwidth than Nvidia’s B200 package. The architecture is designed to eliminate the latency overhead that comes from coordinating thousands of individual GPUs wired together. For workloads where memory bandwidth is the binding constraint, Cerebras makes a credible performance argument.

Also Read: GalaxEye’s Mission Drishti: World’s First OptoSAR Satellite

That argument has attracted serious validators. The Cerebras OpenAI compute deal, announced in January 2026, commits OpenAI to purchasing 750 megawatts of Cerebras computing capacity through 2028 in a contract valued at over $20 billion. OpenAI also lent the company $1 billion, secured by warrants that could convert into a minority equity stake. Amazon Web Services signed a binding term sheet earlier this year to become the first major hyperscaler to deploy Cerebras chips inside its own data centers. AMD participated in the February 2026 Series H round, which valued the company at $23 billion.

These are not casual endorsements. They represent the three most consequential validators in AI infrastructure: the leading AI lab, the leading cloud provider, and a major semiconductor company. For the AI chip IPO 2026 market, the demand signal is unusually clear. Banks underwriting the deal have already received indications of interest exceeding $10 billion on a $3.5 billion offering, nearly three times oversubscribed before a single share has been priced.

The Risk the Prospectus Makes Clear

The S-1 disclosure that deserves the most attention is customer concentration. G42, an Abu Dhabi-based cloud provider, accounted for 87% of Cerebras revenue in the first half of 2024. The company’s entire bull case rests on successfully completing a customer transition from G42 to OpenAI and cloud hyperscalers. That transition is underway. It is not finished.

The financial entanglement with OpenAI also warrants scrutiny. OpenAI is simultaneously Cerebras’s largest customer, its lender, and a potential future shareholder through warrant conversion. That is a concentration of dependency that public market investors have not fully priced into the headlines. If OpenAI’s own strategic priorities shift, or if its in-house chip development program accelerates, the downstream effect on Cerebras revenue would be material.

CEO Andrew Feldman is not selling any shares in the offering. He will retain 10.3 million shares post-IPO, valued at up to $1.28 billion at the high end of the range. That is a meaningful signal of conviction. It is also worth noting that the wafer-scale chip Nvidia alternative thesis remains unproven at hyperscale deployment, outside of the OpenAI relationship.

What the Cerebras $26 Billion Valuation Implies

The Cerebras CBRS Nasdaq listing is pricing in a future that is directionally clear but not yet operational at scale. At $26.6 billion, investors are paying roughly 52 times trailing revenue on a company whose largest customer also holds warrants and sits on its cap table. By comparison, Nvidia trades at roughly 30 times forward revenue, with a dominant software ecosystem and broad customer diversification.

The gap is not irrational given Cerebras’s growth rate. But it leaves almost no margin for execution risk on the OpenAI transition. If the roadshow closes successfully on May 13, the Cerebras Systems IPO will confirm that public markets are prepared to fund the next layer of AI infrastructure investment, not just the applications built on top of it. If it stumbles at pricing, the implications for the broader AI chip IPO 2026 pipeline, including potential listings from other infrastructure players, will be significant.

The wafer-scale bet is technically sound. The business model transition is in progress. Both of those things can be true at the same time, and neither cancels the other out.

Advertisement

GalaxEye’s Mission Drishti: World’s First OptoSAR Satellite and What It Means for Geospatial AI

GalaxEye Mission Drishti satellite in low Earth orbit above the Indian subcontinent with dual sensor array visible on the spacecraft body, cloud cover and city lights below, rocket trail in the lower frame

On May 3, 2026, a 190-kilogram satellite built by a five-year-old Bengaluru startup lifted off aboard a SpaceX Falcon 9 from Vandenberg Space Force Base in California. When Mission Drishti separated from the rocket and entered low Earth orbit, it became something no satellite in history had been before: the world’s first OptoSAR imaging satellite.

The achievement belongs to GalaxEye Space, founded in 2021 by five IIT Madras alumni who previously competed together in the SpaceX Hyperloop Competition. CEO Suyash Singh and CTO Denil Chawda led the technical development alongside co-founders Kishan Thakkar, Pranit Mehta, and Rakshit Bhatt. Their core question, from day one, was not how to build a cheaper satellite. It was how to build a better one.

What OptoSAR Actually Does

Traditional Earth observation satellites carry one of two sensor types. Optical sensors produce clear, photograph-like imagery in visible and infrared wavelengths but are useless through cloud cover or in darkness. Synthetic aperture radar (SAR) uses microwave radar pulses to image the Earth through any weather condition, day or night, but produces abstract, grainy data that requires significant processing before humans or AI models can interpret it.

GalaxEye built a payload that houses both: an X-band SAR sensor and a seven-band multispectral imager on a single thermally-stable optical bench. Because both sensors are co-located on the same platform, they capture the same ground area in a single pass, producing inherently aligned data. There is no need to fuse images from separate satellites with different orbit times and viewing angles. The result is a dataset the company describes as three times richer in information than a standalone sensor, at 1.8-meter fused resolution.

Onboard AI software handles sub-pixel co-registration and jitter correction in real time, ensuring that radar and optical data are precisely merged before downlink. The system can also translate radar returns into optical-like imagery for faster human interpretation.

The Geospatial AI Training Angle

This is where Mission Drishti’s significance extends well beyond the satellite itself. Training geospatial AI models has always been constrained by data quality. Optical training data is intuitive and label-friendly but incomplete: models trained on optical imagery alone fail the moment conditions change. SAR data is all-weather but notoriously difficult to annotate, slowing dataset creation and increasing costs.

Fused OptoSAR imagery solves both problems simultaneously. Annotators can work from the optical layer while the model learns to associate those labels with the corresponding radar returns. This produces geospatial AI systems with better generalization, faster development cycles, and meaningfully lower labeling costs. Applications in automated target recognition, change detection, flood mapping, crop assessment, and maritime surveillance all benefit directly.

Also Read: Karpathy Declares Vibe Coding Obsolete

India’s Strategic Context

India’s optical satellites go effectively blind during monsoon season, a period that spans months and covers the most agriculturally and strategically critical regions of the country. That dependence on favorable weather has been a persistent gap in India’s geospatial intelligence capacity. Mission Drishti is the first domestically developed asset to close it from the private sector.

GalaxEye has partnered with NewSpace India Limited (NSIL), the commercial arm of ISRO, for global distribution of its imagery. Prime Minister Narendra Modi called the launch “a major achievement in India’s space journey.” The Indian Ambassador to the United States, Vinay Mohan Kwatra, met the co-founders days before launch and described it as “a proud moment for Indian deep-tech.”

The GalaxEye Mission Drishti OptoSAR satellite was one of 45 payloads on the CAS500-2 rideshare mission, but it was the only one that represented a genuine global first in satellite imaging architecture.

What Comes Next

GalaxEye plans a full OptoSAR constellation by 2028 aimed at providing daily global coverage. A second-generation satellite platform is already in preliminary design, targeting 300-kilogram spacecraft with 0.5-meter resolution. Several subsystems from Mission Drishti are designed to scale to 500-kilogram spacecraft, enabling component reuse across the constellation.

The narrative around India’s private space sector has always been “cheaper, not better.” GalaxEye just broke that framing. This is not a cost-optimized version of something the US or Europe already built. Five IIT Madras alumni spent five years and more than 500 test flights building a genuinely new category of Earth observation hardware, and they did it faster and leaner than any government program could have.

The hard part is done. The next chapter is data services, geospatial AI applications, and scaling the constellation.

Advertisement

Karpathy Declares Vibe Coding Obsolete, Introduces Agentic Engineering at Sequoia AI Ascent 2026

Andrej Karpathy speaking at Sequoia Capital AI Ascent 2026 on Agentic Engineering and Software 3.0

Andrej Karpathy has a habit of naming things before the industry knows it needs a name. In February 2025, he coined “vibe coding,” the practice of building software by describing what you want and accepting what the model produces. One year later, at Sequoia Capital’s AI Ascent 2026 event, he declared it already obsolete.

The replacement: Agentic Engineering.

Karpathy pinpoints December 2025 as the inflection point. In November, he was writing roughly 80% of his own code, using AI for the rest. By December, that ratio had inverted. He was delegating 80% to agents. “I can’t remember the last time I corrected it,” he said during the fireside chat with Sequoia partner Stephanie Zhan. “I just trusted the system more and more.”

This was not a gradual improvement. It was a threshold crossed. Coding agents stopped being helpful autocomplete and started producing large, correct chunks of code that required no correction. His side projects folder exploded.

Software 3.0: The Context Window Is the New Code

To frame the shift, Karpathy extended his Software 1.0 / 2.0 framework into a third era. Software 1.0 is explicit code written by humans. Software 2.0 is programming by training neural networks on data. Software 3.0 is programming through prompts, where the context window becomes the lever and the LLM is the interpreter executing your intent.

“Your programming now turns to prompting,” he said, “and what’s in the context window is your lever over the interpreter that is the LLM.”

The practical implication is radical. Most existing software was built for humans to click through. In Software 3.0, the interface layer becomes irrelevant. Karpathy illustrated this with a personal story: he built an app called MenuGen that OCR’d restaurant menus and generated food images. He later watched someone feed a menu photo directly to Gemini, which overlaid images onto the pixels without any app at all. “This blew my mind,” he said. “That app shouldn’t exist.”

Vibe Coding vs. Agentic Engineering

Karpathy is precise about the distinction. Vibe coding raised the floor. Anyone can now build working software by describing what they want. That democratization is real and valuable. But vibe coding has a failure mode at scale: no oversight, accumulating technical debt, security vulnerabilities introduced silently.

Andrej Karpathy Agentic Engineering is the professional response. “Agentic engineering is about preserving the quality bar of what existed before in professional software,” he said. “You are still responsible for your software just as before.” The human role shifts from writing code to directing agents, reviewing output, catching failure modes, and maintaining architectural judgment. The best agentic engineers will outperform the best traditional engineers by more than 10x, not because they type less, but because they understand more.

Also Read: Sam Altman Wants to Rethink the OS

The Jagged Intelligence Problem

One of Karpathy’s sharpest observations concerns the uneven capability of frontier models. He calls them “jagged entities,” capable of refactoring a 100,000-line codebase or finding zero-day vulnerabilities, yet unable to reason about walking 50 meters to a car wash. The jaggedness comes from where reinforcement learning reward signals have been concentrated: domains with verifiable outputs like math and code.

The implication for builders: if your use case falls within the RL training distribution, agents fly. If not, they struggle. Understanding where your domain sits on that spectrum is now a core engineering skill.

The Irreplaceable Human

Karpathy closed with the line that resonated most: “You can outsource your thinking, but you can’t outsource your understanding.” As agents handle more of the execution, the human bottleneck concentrates in taste, judgment, and the ability to define what is worth building. The engineers who survive this shift are not the ones writing the least code. They are the ones who understand the most about why software matters.

The profession is being refactored. December 2025 was when it started. Agentic Engineering is what comes next.

Advertisement

Cursor SDK Public Beta, AI Coding Agent CI/CD Pipeline

Cursor SDK TypeScript code on screen with glowing data streams flowing into server infrastructure, dark blue cinematic lighting

Cursor has shipped something quietly significant. On April 28, 2026, the company released the Cursor SDK, a TypeScript API that lets developers programmatically create, run, and manage Cursor’s coding agents from their own code, scripts, CI/CD pipelines, or products. It is available in public beta to all users today. The announcement matters because of what it signals about where Cursor is headed, not just what it does.

From Tool to Platform

Until this week, running a Cursor agent meant opening the Cursor desktop app, CLI, or web interface. The SDK removes that constraint entirely. With npm install @cursor/sdk, any developer can spin up a Cursor agent in a few lines of TypeScript, point it at a repository, and have it start working: summarizing code, fixing bugs, opening pull requests, without a human sitting in front of an editor. The SDK exposes the full Cursor harness: codebase indexing, semantic search, MCP server connections, subagent delegation, and support for every model Cursor supports, including its own Composer 2 model. When running on cloud, each agent gets a dedicated virtual machine with strong sandboxing and a cloned development environment. Agents keep running when a laptop sleeps or a network drops, and can reconnect mid-task. This is infrastructure, not a feature.

What Teams Are Already Building

Cursor’s blog post names Faire, Rippling, Notion, and C3 AI as early adopters. The use cases break down into three patterns. First, engineering teams are wiring agents into CI/CD pipelines to automatically identify the root cause of build failures, summarize changes, and push fixes to pull requests without human intervention. Second, companies are building internal tools, platforms where non-engineers like GTM teams can query product data or spin up prototypes without writing code. Third, and most strategically, some companies are embedding Cursor agents directly inside their own customer-facing products, giving end users an AI coding experience without ever leaving the host application. That third use case is the one to watch. It means Cursor’s intelligence is beginning to show up inside products that have nothing to do with Cursor itself.

The Platform Logic

The shift from tool to platform follows a pattern that has played out before in software. Stripe did not just build a payment product. It built a payment API that let other businesses skip the complexity of financial infrastructure. Twilio did the same for communications. In both cases, the companies that embedded those APIs were not going to rebuild them from scratch. The switching cost became structural. Cursor is running the same play. A team that embeds Cursor agents into their CI/CD pipeline or their internal product has wired Cursor into their engineering workflow at a level that is hard to unwind. The SDK makes Cursor less like a product developers choose each morning and more like infrastructure they depend on continuously. This also reframes Cursor’s valuation. The company is reportedly in talks to raise at a $50 billion valuation, up from $2.5 billion just 15 months ago. Priced as an IDE, even a very good one, that number is aggressive. Priced as the agent runtime layer for the software industry, it becomes more legible.

The Broader Context

The SDK launch comes as the AI coding market is intensifying sharply. Anthropic’s Claude Code, OpenAI’s revamped Codex, and GitHub Copilot are all competing for the same developer workflows. Each has a different architectural bet: Copilot lives inside GitHub’s ecosystem, Claude Code leads on context window depth, and Codex runs as a standalone cloud agent. Cursor’s bet is that none of them will be embedded in other companies’ products at scale, because none of them have made the move Cursor just made. The Cursor SDK is available now at cursor.com, billed on token-based consumption pricing.

Advertisement

Sam Altman Wants to Rethink the OS. OpenAI’s Voice Toolkit Shows What Comes Next.

Sam Altman stands in front of a screen displaying a voice waveform and microphone interface, with the OpenAI logo visible in the background.

On April 26, 2026, OpenAI CEO Sam Altman posted a short note on X that accumulated 1.4 million impressions within 48 hours: “feels like a good time to seriously rethink how operating systems and user interfaces are designed (also the internet; there should be a protocol that is equally usable by people and agents).”

Most people read it as a provocation. It is also a roadmap.

Two days later, OpenAI’s developer account posted a two-minute demo video and a link to a GitHub repo called openai/realtime-voice-component. The demo showed a user playing chess on a webpage using only voice. No clicking. No typing. The user spoke, the app responded, and the game progressed. The tweet pulled 1.3 million views in under 24 hours.

What the Repo Actually Is

The openai/realtime-voice-component is an open-source React toolkit that lets developers build voice-controlled applications using gpt-realtime-1.5, OpenAI’s flagship audio model for voice agents. Rather than building a voice assistant that sits on top of an existing UI, the component is designed to let voice control the state of the application directly. The user speaks a goal. The AI reads the current state of the app. The AI completes the action.

OpenAI describes it as a reference implementation, not a production-ready product. But reference implementations are how platforms begin. The repo is licensed under Apache-2.0, meaning anyone can fork it, extend it, and ship on top of it. That is the point.

Also Read: DeepSeek V4 Runs on Huawei Chips

The Interface Layer Is a Business

Every major computing shift of the last 50 years has been, at its core, a fight over the interface layer. The command line gave way to the graphical desktop. The desktop gave way to the browser. The browser gave way to the mobile app store. Each transition reshuffled which companies controlled how humans accessed software and data. The companies that owned the interface layer captured the most value.

The current interface layer, the app grid on your phone, the browser tab, the operating system underneath it all, was designed for humans who click and tap. It was not designed for AI agents operating on your behalf. An AI navigating a traditional app is working inside an interface built for fingers and eyes, not for machine reasoning. The ceiling on what it can do is set by the constraints of a paradigm it did not create.

Investor Chamath Palihapitiya, responding to the broader conversation this week, framed the shift this way: “The past 50 years of computing was about inventing form factors to interact with information. AI is about interacting with knowledge. It is completely different. Agents and models are there to do the dirty work. We need a new layer, more executive function, less tactical tools.”

What Comes After the Click

Sam Altman’s note pointed at something specific: the internet needs a protocol equally usable by people and agents. That does not exist yet. The web was built for human eyes and human hands. Menus, buttons, forms, navigation flows, all of it assumes a human on one end. An agent trying to navigate that infrastructure is doing so through workarounds.

The OpenAI real-time voice component is one small piece of what a different kind of interface could look like. Voice in, action out. The AI sees the state of the application. The AI completes the task. The user never touches a button.

Whether this specific toolkit becomes the foundation for something larger is not the point. The point is that the question Sam Altman raised on April 26 is now being answered in code, in public, with an open-source license. Developers can start building the answer today.

The interface layer of computing is not a permanent infrastructure. It is an assumption. That assumption is being questioned at the highest levels of the AI industry, and the tools to replace it are already shipping.

Advertisement

Microsoft Ends Exclusive OpenAI Deal: What the Renegotiation Might Really Signal

**Featured image alt text:** Satya Nadella and Sam Altman standing apart in a modern corporate setting, representing the renegotiated Microsoft OpenAI partnership.

On April 27, 2026, Microsoft and OpenAI jointly announced an amended partnership that ends Microsoft’s exclusive right to sell OpenAI’s models and products. OpenAI can now serve customers across any cloud provider. The AGI clause, a provision that would have allowed OpenAI to exit financial obligations if it declared artificial general intelligence achieved, has been removed. The deal was seven years in the making and took one afternoon to restructure.

The headlines have largely framed this as OpenAI breaking free. The reality may be more layered.

Force One: OpenAI’s Commercial Constraint

An internal memo from OpenAI, reported by CNBC earlier this month, described the Microsoft partnership as foundational but acknowledged it had “limited” the company’s ability to meet enterprise customers where they are. Analyst Gil Luria of D.A. Davidson noted that AWS and Google Cloud enterprise customers had been restricted in their ability to integrate OpenAI products because of the exclusivity arrangement. With OpenAI targeting a Q4 2026 IPO at a potential valuation approaching $1 trillion, removing that commercial ceiling appears to have been a priority. Investor prospectuses also struggle with open-ended revenue sharing tied to a subjective milestone like AGI, and cleaning that up ahead of a public listing is straightforward IPO hygiene.

Force Two: Microsoft’s Regulatory Exposure

Exclusivity is a double-edged asset. Reports indicate that regulators in the US, UK, and Europe had begun examining whether Microsoft’s exclusive arrangement gave it an unfair structural advantage in cloud and enterprise AI markets. By agreeing to end exclusivity, Microsoft may have reduced its antitrust surface area at a moment when scrutiny of large technology partnerships is unusually high. This is not a concession that cost Microsoft nothing, but it may have been a concession that cost less than the alternative.

Force Three: The Amazon Forcing Function

In February 2026, OpenAI announced a deal with Amazon: up to $50 billion in investment, with AWS designated as the exclusive third-party cloud distribution provider for OpenAI’s enterprise platform Frontier. That announcement landed while Microsoft’s exclusivity was still nominally in place. Microsoft publicly refuted the terms. The Financial Times reported that legal action was under consideration. Monday’s renegotiation resolves that standoff directly. By ending exclusivity, OpenAI gains the contractual freedom to honor the Amazon commitment without risking litigation.

What Microsoft Kept

It would be a misreading to view this as Microsoft walking away empty-handed. The company retains a 27% equity stake in OpenAI, valued at approximately $135 billion as of late 2025. It holds a non-exclusive IP license through 2032. It receives a guaranteed 20% revenue share from OpenAI through 2030. A $250 billion Azure purchase commitment from OpenAI, confirmed in both companies’ official announcements, remains intact. Azure retains first-ship rights on OpenAI products unless Microsoft chooses not to support them.

The Shift Worth Watching

What has genuinely changed is the structural relationship. The original Microsoft-OpenAI deal was built for a moment when OpenAI needed Microsoft more than Microsoft needed OpenAI. That moment has passed. OpenAI now has Amazon, Google, and a path to public markets. Microsoft’s leverage, while still substantial, appears to rest more on equity and commercial agreements than on contractual control.

It seems like the balance of power has shifted, though by how much remains to be seen. OpenAI’s IPO, expected later this year, will be the first real test of whether the company can sustain its growth and enterprise positioning without the structure Microsoft once provided. Until then, both companies are calling this a simplification. That is probably accurate. What drove the simplification is where the more interesting story lives.

Advertisement