OpenAI’s big investment from AWS comes with something else: new ‘stateful’ architecture for enterprise agents -

The landscape of enterprise artificial intelligence shifted fundamentally today as OpenAI announced $110 billion in new funding from three of tech’s largest firms: $30 billion from SoftBank, $30 billion from Nvidia, and $50 billion from Amazon.

But while the former two players are providing money, OpenAI is going further with Amazon in a new direction, establishing an upcoming fully “Stateful Runtime Environment” on Amazon Web Services (AWS), the world’s most used cloud environment.

This signals OpenAI’s and Amazon’s vision of the next phase of the AI economy — moving from chatbots to autonomous “AI coworkers” known as agents — and that this evolution requires a different architectural foundation than the one that built GPT-4.

For enterprise decision-makers, this announcement isn’t just a headline about massive capital; it is a technical roadmap for where the next generation of agentic intelligence will live and breathe.

And especially for those enterprises currently using AWS, it’s great news, giving them more options with a new runtime environment from OpenAI coming soon (the companies have yet to announce a precise timeline for when it will arrive).

The great divide between ‘stateless’ and ‘stateful’

At the heart of the new OpenAI-Amazon partnership is a technical distinction that will define developer workflows for the next decade: the difference between “stateless” and “stateful” environments.

To date, most developers have interacted with OpenAI through stateless APIs. In a stateless model, every request is an isolated event; the model has no “memory” of previous interactions unless the developer manually feeds the entire conversation history back into the prompt. OpenAI’s prior cloud partner and major investor, Microsoft Azure, remains the exclusive third-party cloud provider for these stateless APIs.

The newly announced Stateful Runtime Environment, by contrast, will be hosted on Amazon Bedrock — a paradigm shift.

This environment allows models to maintain persistent context, memory, and identity. Rather than a series of disconnected calls, the stateful environment enables “AI coworkers” to handle ongoing projects, remember prior work, and move seamlessly across different software tools and data sources.

As OpenAI notes on its website: “Now, instead of manually stitching together disconnected requests to make things work, your agents automatically execute complex steps with ‘working context’ that carries forward memory/history, tool and workflow state, environment use, and identity/permission boundaries.”

For builders of complex agents, this reduces the “plumbing” required to maintain context, as the infrastructure itself now handles the persistent state of the agent.

OpenAI Frontier and the AWS Integration

The vehicle for this stateful intelligence is OpenAI Frontier, an end-to-end platform designed to help enterprises build, deploy, and manage teams of AI agents, launched back in early February 2026.

Frontier is positioned as a solution to the “AI opportunity gap”—the disconnect between model capabilities and the ability of a business to actually put them into production.

Key features of the Frontier platform include:

Shared Business Context: Connecting siloed data from CRMs, ticketing tools, and internal databases into a single semantic layer.
Agent Execution Environment: A dependable space where agents can run code, use computer tools, and solve real-world problems.
Built-in Governance: Every AI agent has a unique identity with explicit permissions and boundaries, allowing for use in regulated environments.

While the Frontier application itself will continue to be hosted on Microsoft Azure, AWS has been named the exclusive third-party cloud distribution provider for the platform.

This means that while the “engine” may sit on Azure, AWS customers will be able to access and manage these agentic workloads directly through Amazon Bedrock, integrated with AWS’s existing infrastructure services.

OpenAI opens the door to enterprises: how to register your interest in its upcoming new Stateful Runtime Environment on AWS

For now, OpenAI has launched a dedicated Enterprise Interest Portal on its website. This serves as the primary intake point for organizations looking to move past isolated pilots and into production-grade agentic workflows.

The portal is a structured “request for access” form where decision-makers provide:

Firmographic Data: Basic details including company size (ranging from startups of 1–50 to large-scale enterprises with 20,000+ employees) and contact information.
Business Needs Assessment: A dedicated field for leadership to outline specific business challenges and requirements for “AI coworkers”.

By submitting this form, enterprises signal their readiness to work directly with OpenAI and AWS teams to implement solutions like multi-system customer support, sales operations, and finance audits that require high-reliability state management.

Community and leadership reactions

The scale of the announcement was mirrored in the public statements from the key players on social media.

Sam Altman, CEO of OpenAI, expressed excitement about the Amazon partnership, specifically highlighting the “stateful runtime environment” and the use of Amazon’s custom Trainium chips.

However, Altman was quick to clarify the boundaries of the deal: “Our stateless API will remain exclusive to Azure, and we will build out much more capacity with them”.

Amazon CEO Andy Jassy emphasized the demand from his own customer base, stating, “We have lots of developers and companies eager to run services powered by OpenAI models on AWS”. He noted that the collaboration would “change what’s possible for customers building AI apps and agents”.

Early adopters have already begun to weigh in on the utility of the Frontier approach. Joe Park, EVP at State Farm, noted that the platform is helping the company accelerate its AI capabilities to “help millions plan ahead, protect what matters most, and recover faster”.

The enterprise decision: where to spend your dollars?

For CTOs and enterprise decision-makers, the OpenAI-Amazon-Microsoft triangle creates a new set of strategic choices. The decision of where to allocate budget now depends heavily on the specific use case:

For High-Volume, Standard Tasks: If your organization relies on standard API calls for content generation, summarization, or simple chat, Microsoft Azure remains the primary destination. These “stateless” calls are exclusive to Azure, even if they originate from an Amazon-linked collaboration.
For Complex, Long-Running Agents: If your goal is to build “AI coworkers” that require deep integration with AWS-hosted data and persistent memory across weeks of work, the AWS Stateful Runtime Environment is the clear choice.
For Custom Infrastructure: OpenAI has committed to consuming 2 gigawatts of AWS Trainium capacity to power Frontier and other advanced workloads. This suggests that enterprises looking for the most cost-efficient way to run OpenAI models at massive scale may find an advantage in the AWS-Trainium ecosystem.

Licensing, revenue and the Microsoft ‘safety net’

Despite the massive infusion of Amazon capital, the legal and financial ties between Microsoft and OpenAI remain remarkably rigid. A joint statement released by both companies clarified that their “commercial and revenue share relationship remains unchanged”.

Crucially, Microsoft continues to maintain its “exclusive license and access to intellectual property across OpenAI models and products”. Furthermore, Microsoft will receive a share of the revenue generated by the OpenAI-Amazon partnership.

This ensures that while OpenAI is diversifying its infrastructure, Microsoft remains the ultimate beneficiary of OpenAI’s commercial success, regardless of which cloud the compute actually runs on.

The definition of Artificial General Intelligence (AGI) also remains a protected term in the Microsoft agreement. The contractual processes for determining when AGI has been reached—and the subsequent impact on commercial licensing—have not been altered by the Amazon deal.

Ultimately, OpenAI is positioning itself as more than a model or tool provider; it is an infrastructure player attempting to straddle the two largest clouds on Earth.

For the user, this means more choice and more specialized environments. For the enterprise, it means that the era of “one-size-fits-all” AI procurement is over.

The choice between Azure and AWS for OpenAI services is now a technical decision about the nature of the work itself: whether your AI needs to simply “think” (stateless) or to “remember and act” (stateful).