Editorial scope: An examination of OpenAI’s technology, products, competitive position and economics.
Important: Informational research, not financial advice or an investment recommendation.
OpenAI research: OpenAI — Company Profile · OpenAI — Deep Dive.
OpenAI’s central business challenge is converting an exceptionally large audience into a durable economic platform. ChatGPT attracts users directly. Codex and ChatGPT Work seek to turn that relationship into repeated professional activity. The API supplies intelligence to other companies’ software, while cloud partnerships reach organizations that already buy infrastructure through established procurement channels. Advertising adds another way to monetize people who do not buy a substantial subscription.
These businesses share model research and computing infrastructure, but their economics differ. A subscriber pays for access and capacity; an API customer pays for measured consumption; an enterprise buys a combination of capability, controls and deployment support; an advertiser pays to reach potential customers. OpenAI’s advantage will depend on how effectively those channels reinforce one another, and how much of their revenue remains after inference, infrastructure commitments, distribution and development costs.
The investment in work products is therefore more than a feature expansion. It is an attempt to move from being a destination for answers to becoming an environment in which consequential tasks are completed. That opportunity is large, but it exposes OpenAI to the operational demands of enterprise software and to failures that matter more than an inaccurate paragraph.
1. OpenAI is the company; ChatGPT is an application
OpenAI develops and trains models, obtains compute, establishes deployment policies and commercializes the resulting capabilities. ChatGPT is its customer-facing application and product brand. GPT identifies model families, including the current GPT-6 Astra and GPT-5.6 lineup. Codex is a coding agent product; the OpenAI API is a developer service; Frontier is an enterprise agent platform. Buying ChatGPT does not mean buying unrestricted access to every model or to the separately billed API. Model catalog, ChatGPT subscription terms
OpenAI’s governance also needs precision. Following its October 2025 recapitalization, the nonprofit OpenAI Foundation controls OpenAI Group PBC, the public benefit corporation operating the commercial business. The Foundation can appoint and replace the operating company’s directors. This is neither a conventional wholly investor-controlled technology company nor a nonprofit service with no commercial return requirement. The structure links a mission mandate to a business that must finance expensive research and deployment. OpenAI’s corporate structure
The following layers are an analytical map, rather than disclosed financial reporting segments.
| Layer | What customers encounter | Economic function | Important distinction |
|---|---|---|---|
| Models | GPT reasoning and multimodal capabilities | Set the quality, speed and serving cost of intelligence | A model alone does not include an organization’s data, permissions or workflow. |
| Applications | ChatGPT, ChatGPT Work and Codex | Own the user relationship and repeated work | Several products can share a subscription or enterprise agreement. |
| Developer and enterprise infrastructure | API, Agents SDK and Frontier | Enable other software and deployed business processes | A development framework and a paid managed service are different offerings. |
| Ecosystem and distribution | Plugins, cloud platforms, enterprise deployment partners | Supply integrations and reach buyers | The channel can influence billing, access, customer ownership and margins. |
| Advertising | Sponsored placements and emerging advertiser tools | Monetize attention and commercial intent | Ad revenue is separate from subscription and API consumption. |
The audience is an unusually valuable starting point. On August 31, OpenAI said ChatGPT had more than 1bn weekly active users and its advertising business had reached a $1bn annualized revenue run rate. Those are company disclosures: active users are not paying accounts, and annualized advertising revenue is not a completed year of revenue. The relevant strategic inference is that OpenAI can introduce products to an existing audience without acquiring every new customer through a separate sales process. OpenAI’s August disclosure
Earlier, in February, OpenAI disclosed more than 50m consumer subscribers, more than 9m paying business users and 1.6m weekly Codex users. These dated figures illustrate the different populations involved. They should not be added together, treated as current September counts or multiplied by one headline subscription price to reconstruct revenue: users can overlap, products have different plans, and contractual discounts are not visible. February company disclosure
2. How OpenAI’s models work
Pre-training creates general capability
A language model converts text into tokens, numerical units representing pieces of language, and learns statistical relationships among them. Training repeatedly compares its predictions with training targets and adjusts the model’s weights. At large scale, predicting sequences can produce useful representations of language, code, facts and patterns of reasoning. This is not a conventional database that looks up and reproduces a guaranteed correct record for each question.
The transformer architecture uses attention to relate positions in a sequence, allowing the representation of one token to depend on others. OpenAI’s GPT-4 report describes a transformer-style model trained to predict the next token and subsequently aligned. That establishes the historical technical foundation; it does not disclose the complete architecture of GPT-6 Astra. Exact parameter counts, data mixtures, routing arrangements and full training recipes for the latest flagship are not publicly established in the sources reviewed. They should not be filled in with estimates presented as facts. Transformer research paper, GPT-4 technical report
OpenAI describes three broad sources of development data: publicly available internet material, information obtained through partners, and information provided or generated by users, trainers and researchers. Data preparation, pre-training, post-training and evaluation serve different purposes. A product’s ability to read an uploaded spreadsheet at inference time does not mean that spreadsheet has been incorporated into the base model’s weights. Data-use terms also differ between consumer and business offerings. OpenAI’s model-development explanation
Post-training shapes behavior and reasoning
Pre-training alone does not ensure that a model follows instructions, refuses dangerous requests or expresses uncertainty appropriately. OpenAI’s historical InstructGPT work used supervised demonstrations, human comparisons of answers, a learned reward model and reinforcement learning to favor responses people preferred. This is the widely discussed reinforcement learning from human feedback, or RLHF, pipeline. It is a documented foundation, not a claim that every current model uses that exact unchanged recipe. InstructGPT and RLHF
Reasoning models add another dimension. OpenAI’s o1 research showed performance improving with additional reinforcement learning and with more computation during answering. Training encourages useful intermediate problem-solving behavior, including checking alternatives and recovering from mistakes. More time spent reasoning can improve a difficult answer, but it increases latency and computational work. A longer reasoning trace is not proof of correctness, and a benchmark improvement does not demonstrate equal progress on every professional task. OpenAI’s reasoning research
Anthropic’s Constitutional AI and OpenAI’s deliberative alignment address related problems through different published methods. Constitutional AI uses written principles to guide model critique, revision and AI-generated preference feedback. Deliberative alignment trains reasoning models to apply written safety specifications to a request. Both make normative rules part of training; neither eliminates human choices about those rules or proves that the deployed model always obeys them. Treating this as simply “human feedback versus a constitution” obscures the overlap among supervision, AI feedback and reinforcement learning. Anthropic’s Constitutional AI research, OpenAI’s deliberative alignment research
Inference uses capability already learned
Inference is the work performed when a trained model processes a request. The system assembles instructions, conversation history and relevant material; the model processes that context and generates output. The weights are ordinarily unchanged during this interaction. A saved preference or retrieved company document can influence future answers through product memory or retrieval, without retraining the foundation model.
For reasoning models, generated work includes internal reasoning tokens as well as the visible answer. OpenAI’s API documentation says reasoning tokens occupy context and are billed as output tokens even when they are not exposed to the customer. Consequently, a short final answer can have a substantial bill, and a token limit can be exhausted before a useful final answer appears. Reasoning effort is therefore both a quality control and an economic control. Reasoning and token accounting
Context is working space, not perfect memory
A context window limits how much information a model can work with in a request, including relevant instructions, input and generated tokens. OpenAI’s current API catalog lists a 1.05m-token context window and a 128,000-token maximum output for Astra and the GPT-5.6 models. These API specifications do not imply that every ChatGPT plan exposes the same limits. Long documents still require retrieval, organization and verification; capacity to accept text is not a guarantee of reliably finding every relevant fact. API model specifications, ChatGPT plan comparison
Retrieval selects relevant passages from external information and supplies them as context. Persistent memory stores information outside an individual model call. Summarization and context compaction preserve selected information when a task becomes long. These techniques solve different constraints and can all lose details. For an enterprise, the practical test is whether the system retrieves the right authorized evidence and preserves the conditions attached to it, rather than how many tokens fit in a marketing specification.
Tools and agents turn output into action
A tool call is a structured request for an external operation. The application advertises available tools, the model requests one with arguments, the application executes it, and the result returns to the model. Searching a document store, running code and updating a business record are different permissions, even if the interface presents them in one conversation. A model’s request to use a tool is not itself authorization to perform the action. OpenAI’s function-calling workflow
An agent adds a continuing control loop around model calls: examine the task, choose an action, observe the result, revise the plan and continue until a stopping condition is met. The surrounding software supplies tools, state, budgets, isolation and human approvals. OpenAI’s Agents SDK packages orchestration, handoffs, guardrails, sessions and tracing. Agent capability therefore depends on the model and the environment together; the same weights can produce very different outcomes under different tools and permissions. Agents SDK documentation
The commercial consequence is significant. A single delegated task can involve many model calls, searches and code executions. That creates more opportunities to charge for useful work, but also more compute consumption and more opportunities for compounding mistakes. The relevant unit becomes a completed, accepted task rather than one generated response.
3. The model lineup is also a pricing architecture
OpenAI organizes its current general-purpose API offering around a premium flagship and a range of lower-priced models. The economic purpose is segmentation: customers can reserve expensive reasoning for work where it changes the outcome and use cheaper models for repetitive tasks. Model choice should reflect measured performance on the customer’s own workload, not just the position of a name in the catalog.
| Model | Position in the current lineup | Standard input per 1m tokens | Cached input per 1m tokens | Standard output per 1m tokens |
|---|---|---|---|---|
| GPT-6 Astra | Highest-capability general flagship | $10.00 | $1.00 | $50.00 |
| GPT-5.6 Sol | Complex professional work | $4.00 | $0.40 | $20.00 |
| GPT-5.6 Terra | Balance of capability and cost | $2.00 | $0.20 | $12.00 |
| GPT-5.6 Luna | Cost-sensitive, high-volume work | $0.20 | $0.02 | $1.20 |
Sources for model positioning and prices: model catalog and API pricing. These are standard short-context API rates at the research cutoff. Sol’s listed promotional pricing runs at least through November 21, 2026. Long-context schedules, cache writes, service tiers and tools can change the bill. Batch and Flex offer lower listed token rates, while Fast mode charges more. A cached-input price applies to eligible reuse, not automatically to all repeated-looking material. OpenAI API pricing
The product implication is a portfolio rather than a single universal model. A support operation may route straightforward classification to a low-cost model and escalate ambiguous cases. A software agent may use a stronger model for architecture or difficult debugging. The optimization target should include failures and review: a cheaper call that requires three retries and manual repair can be more expensive than a premium call that succeeds once.
OpenAI also has an open-weight strategy. Its gpt-oss-120b and gpt-oss-20b releases use the Apache 2.0 license and can be deployed by customers themselves. These are separate from the proprietary flagship service. They support experimentation and deployment control, but self-hosting shifts infrastructure and operational costs to the operator; it does not make inference free. Open weights can broaden OpenAI’s developer influence even when they do not produce a direct OpenAI API charge. The gpt-oss release
Multimodal capabilities further widen the addressable work. Image generation, speech and realtime interactions have distinct models and meters; text-token prices cannot be applied mechanically to all of them. OpenAI’s current API schedule, for example, prices GPT-Live sessions by connected time as well as separately billed backend work. The economic opportunity is access to tasks that text alone handles poorly, accompanied by a more complicated serving-cost profile. Multimodal API pricing
4. The product portfolio: who buys what, and why
The portfolio increasingly combines three routes into work: an individual starts using ChatGPT, a developer delegates software tasks to Codex, or an organization deploys AI inside a controlled process. These routes can converge under an enterprise agreement. Product revenue cannot be added up by brand without knowing which activity was included in an existing plan.
Consumer plans establish the direct relationship
| Offering | Customer problem and target user | Pricing model | Distribution | Strategic role |
|---|---|---|---|---|
| ChatGPT Free | Occasional help with questions, writing and everyday tasks | No subscription charge; limits apply; eligible ad-supported experiences | Web and consumer apps | Audience acquisition and habitual use |
| ChatGPT Go | More capacity for price-sensitive regular users | Lower-cost monthly subscription; $8 US launch list price, with localized pricing | Self-service upgrade | Broaden paid adoption below Plus |
| ChatGPT Plus | Research, creation and reasoning for regular users | $20/month, with feature and usage limits | Self-service web and apps | Mainstream recurring consumer revenue |
| ChatGPT Pro | Heavy professional or technical usage | $100/month tier; existing $200/month subscriptions continue, but new purchases and upgrades paused from September 10 | Self-service where available | Capture greater willingness to pay and usage intensity |
Sources: ChatGPT plan comparison, Go’s published US price, Plus pricing, current Pro tiers and purchase pause.
These plans sell access with allowances, not a promise that every workload can run without limits. Pro’s $100 and $200 tiers advertise different usage allocations. The purchase pause matters because a product comparison that simply lists a universally available $200 plan would be misleading at the cutoff. ChatGPT subscriptions also do not include a general API balance. The strategic tension is that users value predictable bills while OpenAI’s cost varies with the amount and complexity of work they request.
Work, coding and the enterprise
| Offering | Customer problem and target user | Pricing model | Distribution | Strategic role |
|---|---|---|---|---|
| ChatGPT Work | Knowledge workers need finished files, analysis and actions across connected tools | Included within eligible ChatGPT plans and allowances; enterprise metering follows the agreement | ChatGPT across supported interfaces | Move usage from isolated questions into repeatable work |
| ChatGPT Business | Teams need shared administration and protected business use | Standard seats $20/user/month annually or $25 monthly; premium seats $100/user/month billed annually or $125/user/month billed monthly | Self-service and business sales | Convert individual adoption into organizational spending |
| ChatGPT Enterprise | Large organizations need identity, governance, deployment and commercial controls | Custom agreements; credit-based or eligible token-based consumption | Direct enterprise sales | Larger accounts, expansion and governed adoption |
| Codex | Developers need help implementing, reviewing and maintaining software | Eligible plan usage; credits or consumption under the relevant account and agreement | ChatGPT, CLI, IDE and cloud workflows | Own a valuable, frequent technical workflow |
| OpenAI Frontier | Enterprises need agents operating across systems with identity, context and evaluation | Sales-led commercial arrangement; no universal public standalone list price identified | Enterprise sales and deployment teams | Embed OpenAI in production business processes |
Sources: ChatGPT Work, business pricing, Enterprise token rate card, Codex, Frontier.
ChatGPT Work brings files, connected services, reusable instructions and task execution into one working environment. A user can request an editable deliverable and continue refining it, rather than copy an answer into another application. Its significance is workflow ownership: if the initial request, evidence, output and subsequent revision remain in ChatGPT, OpenAI participates in more of the task. Connections and scheduled work can make the product useful between individual visits. ChatGPT Work capabilities
Codex addresses a particularly attractive market because software work produces artifacts that can often be checked through execution, tests and review. The product can work with repositories, run tasks in local or cloud environments, and support background development activity. Its value is wider than code completion: debugging, migrations and maintenance can consume meaningful developer time. However, passing tests is an incomplete quality measure; architecture, security and maintainability still require review. Codex product overview
Enterprise customers buy organizational control as well as access to models. Business and Enterprise include protections for business data, while Enterprise adds more extensive identity, retention and governance options. Those capabilities can determine whether a deployment passes procurement at all. The competitive test is therefore not only the model’s answer quality but the time and effort required to make the system usable within an organization’s policies. Business and Enterprise comparison
Frontier moves further into enterprise infrastructure. It combines business context, agent execution, evaluation and permission controls, with deployment expertise delivered through the Enterprise Frontier Program. The upside is integration into operational systems that are expensive to replace. The trade-off is implementation effort: deployments involving several systems and teams can require substantial human engineering and change management before recurring software-like economics emerge. Frontier’s operating model
Developer tools and the ecosystem
| Offering | Customer problem and target user | Commercial model and channel | Strategic role |
|---|---|---|---|
| OpenAI API and Responses API | Software teams need model inference and tools inside their own applications | Direct metered API access; eligible cloud distribution is a separate purchasing route | Monetize intelligence wherever applications are built |
| Agents SDK | Developers need orchestration, state, handoffs and observability | Open-source framework; model, tool and infrastructure usage can still be billable | Reduce integration work and encourage deployment |
| Apps SDK / current plugin tooling | Service providers want ChatGPT to use their tools, information and interfaces | Developer ecosystem; underlying services have their own economics | Make ChatGPT more useful and valuable as a distribution surface |
| Model Context Protocol support | Developers need a common way to expose external tools and data | Open protocol; no general OpenAI protocol toll | Expand connectivity and reduce custom integration friction |
| gpt-oss | Operators want deployable model weights and more infrastructure control | Open-weight distribution; operator pays serving costs | Extend technical influence beyond the hosted API |
Sources: API model and endpoint documentation, Agents SDK, current plugin documentation, gpt-oss.
Product names are changing quickly. The Apps SDK documentation address currently redirects to OpenAI’s plugin documentation, which describes packages combining skills, MCP servers and optional interfaces. The framework, the installed plugin and the third-party service remain distinct. An integration does not imply that OpenAI owns the underlying customer data or receives a standard commission on every transaction. No universal ecosystem take rate is established in the reviewed disclosures. Plugin architecture and publishing documentation
MCP originated at Anthropic as an open connectivity standard and is supported within OpenAI’s developer ecosystem. It is neither a competing foundation model nor an exclusive Anthropic revenue stream. Standardized connectivity can increase demand for agent platforms while making integrations more portable between them. That helps adoption but can weaken the defensibility of any one provider’s connector collection. MCP’s introduction, OpenAI Agents SDK MCP support
Portfolio breadth also requires discipline. Reuters reported in April that OpenAI had shut its Sora video app as it sharpened its focus on coding and business software. That reporting should not be conflated with the lifecycle of every video API endpoint, and the former standalone app should not be presented as an unquestioned current growth pillar. The strategic lesson is that audience excitement alone does not establish attractive product economics. Reuters on product focus
5. Industry products add data, workflow and trust
A sector offering can combine an existing model with specialized retrieval, licensed information, instructions, controls and distribution. It does not necessarily imply that an entirely new foundation model has been trained from scratch. The commercial attraction is higher willingness to pay when an AI system understands the materials and conventions of a valuable professional workflow.
| Offering | Problem and target user | Product and distribution | Pricing approach and strategic role |
|---|---|---|---|
| ChatGPT for Financial Services | Bankers and research teams need supported analysis, models and client materials | ChatGPT Work experience with financial datasets and firm controls; available to eligible institutions through sales | Sales-led terms; increases enterprise value by integrating data and production workflows |
| Astra for Law | Law firms need relevant authority, legal analysis and confidentiality controls | Astra with legal search and instructions; initially selected US firms through Trusted Access in ChatGPT and Codex; API announced as coming soon | Eligible Enterprise token rate card lists distinct Law rates; broader terms depend on access and contract |
| ChatGPT Health | Individuals need help organizing and understanding personal health information | Dedicated consumer experience with additional separation and privacy; US adult rollout announced in July | Embedded product access rather than a separately disclosed universal professional license; strengthens relevance and engagement |
| ChatGPT Edu | Universities need institutionally managed AI for students, faculty and staff | Education offering sold to institutions | Institution-specific commercial terms; develops distribution and long-term familiarity |
| Daybreak and research-oriented models | Security and research specialists need domain capability under additional controls | Restricted programs and eligible enterprise access | Consumption and negotiated access; creates higher-value specialized workloads |
Sources: Financial Services launch, Astra for Law launch, Enterprise specialist rate card, ChatGPT Health, ChatGPT Edu.
Financial Services, introduced September 10, integrates data from providers including Daloopa, PitchBook, LSEG News and Crunchbase, alongside connections to other subscriptions. OpenAI says it hosts and indexes included data and supports granular citations. This is commercially significant because reliable data access and traceability can be more valuable than another increment in general language fluency. It also adds licensing and integration dependencies that a generic chat product does not face. Financial Services design and availability
Astra for Law was announced on the research cutoff date, September 17. Its initial restricted availability and forthcoming API matter: an announcement is not broad commercial deployment. The offering combines Astra with legal retrieval and workflow instructions, while legal software providers can remain the customer-facing application. It positions OpenAI as both a supplier to specialists and a potential direct workflow provider, creating opportunities for partnership alongside channel tension. Astra for Law
Health illustrates a different business objective. A dedicated consumer experience can improve retention and trust even without an independently reported revenue line. OpenAI says Health conversations are excluded from foundation-model training and separated from ordinary chat context. It is designed to support understanding and preparation for care, not diagnose or replace clinicians. Those boundaries are part of the product proposition, rather than evidence that every output is clinically reliable. Health’s purpose and data controls
Across sectors, the strongest potential advantage is the combination of authorized data, task-specific evaluation and integration into repeated work. A generic model can often imitate professional language; a production product must preserve entitlements, surface evidence and fit the customer’s review process. The amount of useful work that survives expert review is the measure that matters commercially.
6. Monetization and cloud distribution
OpenAI has several monetization mechanisms that should be evaluated separately. They are different ways of packaging access to shared capabilities, with different exposure to usage, selling costs and intermediaries.
| Revenue mechanism | What triggers payment | Economic attraction | Principal limitation |
|---|---|---|---|
| Consumer subscriptions | A recurring plan purchase | Predictability, self-service conversion and direct customer relationship | Heavy usage can consume a disproportionate amount of compute. |
| Business seats | Provisioned user access and plan selection | Team expansion and centralized purchasing | Purchased seats do not necessarily become active, renewing users. |
| Enterprise consumption | Credits or tokens under the contract | Revenue can expand with useful work across Chat, Work and Codex | Customers require spend visibility and evidence of value. |
| Direct API | Model tokens and applicable tools or services | Broad developer reach and payment tied to consumption | Price competition, routing and customer concentration |
| Cloud distribution | Usage billed through the cloud arrangement | Existing procurement, infrastructure and governance relationships | Partner economics and less direct control of the customer |
| Advertising | Advertiser spending on eligible placements and campaigns | Monetization of a large audience beyond subscriptions | Trust, relevance and advertiser return must hold together. |
The move toward token-based Enterprise contracts is particularly revealing. OpenAI’s current rate card applies consumption pricing across Chat, Work and Codex for eligible agreements, while other customers remain on credit-based contracts. This makes it possible to expand revenue when an employee delegates more work without selling another seat. It also exposes buyers more directly to the compute intensity of agents. A seat can be a distribution unit while tokens become the marginal billing unit. Enterprise token-based rate card
Azure remains central; distribution is becoming broader
Under the April 27 amended Microsoft agreement, Microsoft remains OpenAI’s primary cloud partner, and products ship first on Azure unless Microsoft cannot and chooses not to support the required capabilities. OpenAI can serve all its products through other cloud providers. Microsoft’s model and product IP license runs through 2032 and is nonexclusive. OpenAI’s revenue-share payments to Microsoft continue through 2030 subject to a total cap; the announcement does not disclose the percentage or cap. Amended Microsoft partnership
Current OpenAI documentation confirms supported models on Amazon Bedrock, including Astra, with availability and features depending on endpoint and region. AWS manages access, routing, billing and operational controls. This is a commercial distribution channel for proprietary OpenAI models, distinct from someone independently hosting open weights on AWS. Compatibility with an API interface does not mean every hosted tool or operational feature is identical across platforms. OpenAI on Amazon Bedrock
The February Amazon partnership also announced a jointly developed Stateful Runtime and substantial Trainium and capacity commitments. These agreements connect financing, infrastructure and go-to-market interests. They should be read by date and scope: an announcement about a particular runtime or enterprise product does not define every subsequent model-distribution arrangement. OpenAI–Amazon partnership
Cloud availability expands the reachable budget, but public retail token prices do not reveal how that budget is divided among model developer, cloud operator and other participants. Nor should announced infrastructure contracts be added indiscriminately to infer OpenAI’s near-term cash obligations: schedules, overlap, contingencies and utilization matter. Distribution is an advantage only if the incremental contribution remains attractive after the channel’s economics.
Advertising changes the revenue mix
OpenAI’s August advertising disclosure described a business operating in more than 40 countries, with self-service buying and increasing use of performance-oriented campaigns. On September 16 it announced testing Sponsored Agents with selected US advertisers, allowing an opted-in conversation with a business in a separate interaction. These are dated product developments, not proof that conversational advertising will achieve search-like margins. Advertising business update, Sponsored Agents announcement
The attraction is commercial intent expressed in natural language: a person seeking a service may be closer to a purchase than someone passively viewing content. The risk is equally direct. If recommendations appear to serve advertisers at the expense of the user, trust in the assistant can weaken. OpenAI’s stated separation of ads from answers is therefore part of the economic architecture, not just presentation. Strong monetization requires measurable advertiser outcomes and continued user confidence.
7. Safety and governance are operating requirements
Model safety involves several different problems: preventing harmful assistance, reducing factual error, preserving confidential information and keeping actions within authorized boundaries. Improving one does not guarantee progress on all the others. A model may refuse an explicitly dangerous request yet still mishandle an ordinary business task, or give a polished answer with an unsupported citation.
OpenAI’s Astra system card makes the stakes concrete. The company classifies Astra at its own “Critical” cybersecurity capability level and says it has added misalignment monitoring to tool-using deployment, at significant compute cost. It also reports limits to monitoring, including reduced visibility into some adversarial behavior, and cautions that an absence of observed failures does not establish reliability across settings. These are company evaluations and disclosures, not a guarantee from an independent regulator. Astra system card
The business implication is that safety is both a product attribute and a cost. Evaluation, monitoring, isolation and incident response consume resources; restricted access may delay revenue. Conversely, a product that cannot meet a customer’s control requirements may never reach production, regardless of its benchmark performance. Safety can support commercial adoption without constituting a permanent technical lead over competitors.
| Failure mode | Why it matters | Control that addresses the specific problem |
|---|---|---|
| Hallucinated facts or citations | Research and decisions can rest on false evidence. | Retrieval, source inspection and task-specific verification |
| Prompt injection in external content | A document or webpage can attempt to redirect an agent. | Treat retrieved material as data; isolate credentials and restrict tool privileges. |
| Unauthorized action | A plausible plan can change records or systems beyond the request. | Scoped permissions, approval boundaries, logs and recoverable actions |
| Long-task drift | Earlier constraints can be lost as a task grows. | Explicit task state, checkpoints and review of the final artifact |
| Sensitive-data leakage | Tools and logs can spread information beyond intended recipients. | Entitlement-aware access, retention controls and connector review |
| Reward or evaluation gaming | A system can optimize a proxy without achieving the intended task. | Outcome checks, varied evaluations and monitoring beyond a single score |
This table is an operational assessment of the risks described by the model and tool architecture, rather than a claim that any control eliminates a failure mode. The objective is to constrain the consequences of errors while measuring whether the system is useful enough to justify deployment.
Privacy policies also need to be read precisely. OpenAI’s API data controls distinguish training use, abuse monitoring and application-state retention. API data is not used for training by default, but that does not mean no data is retained. Standard monitoring and product-specific storage can apply; zero-retention eligibility depends on the endpoint and configuration. Data passed to a third-party MCP server becomes subject to that service’s policies. API data controls
Consumer controls differ. OpenAI says ordinary ChatGPT conversations may be used to improve models unless the user opts out, while business offerings have different defaults. The right enterprise diligence question is therefore what happens to each data flow—model request, saved file, tool call, log and output—under the actual contract and settings. A broad claim that “the AI is private” is insufficient. Consumer data-use explanation, business commitments
8. Competition: the contest is moving into workflows
OpenAI, Anthropic and Google are converging on a similar destination: models that reason over information and perform work through tools. Their starting assets differ. OpenAI has a large direct audience and a broad application portfolio. Anthropic has a focused Claude platform with a substantial coding proposition. Google combines models with productivity distribution and infrastructure. Mistral emphasizes an alternative agent platform and deployment control. Those differences can matter more than a transient lead on one benchmark.
| Company | Product strategy | Coding and agents | Enterprise advantage | Pressure on OpenAI |
|---|---|---|---|---|
| OpenAI | Extend ChatGPT into work, development and third-party applications | Codex, Work, Responses API, Agents SDK and Frontier | Direct familiarity plus enterprise products and cloud channels | Must translate breadth into reliable, profitable usage. |
| Anthropic | Build Claude into a connected professional platform | Claude Code and a broader tool-using Claude ecosystem | Coding workflows and distribution across major clouds | Competes for developers, model spend and enterprise trust. |
| Connect Gemini to business information, applications and cloud infrastructure | Gemini Enterprise agents and workflow-building tools | Workspace relationships, Google Cloud and purpose-built TPUs | Can combine distribution and infrastructure with model capability. | |
| Mistral | Offer work and coding agents with flexible deployment | Vibe and Vibe for code | On-premises, private-cloud and customization options | Challenges the assumption that valuable work must use a proprietary hosted flagship. |
Sources: OpenAI’s business platform, Claude Code, Anthropic cloud partnerships, Gemini Enterprise, Google TPUs, Mistral Vibe.
Coding is a contest for the development workflow
Claude Code and Codex both offer execution-oriented workflows across repositories and developer tools. Their commercial value depends on accepted changes, review time and operational reliability. A benchmark conducted with one harness, token budget and retry policy cannot establish which product is best for every company. Evaluation should hold those conditions reasonably constant and include representative repositories, security requirements and maintainability, rather than compare headline scores from different launch materials. Claude Code’s workflow, Codex’s workflow
The durable prize is familiarity with how a development organization operates: its instructions, tools, checks and recurring maintenance tasks. That can create switching costs even when the underlying model changes. However, developers are technically capable buyers, and standardized interfaces and portable repositories make experimentation with alternatives relatively easy. Strong usage does not automatically become exclusive loyalty.
Enterprise adoption rewards integration and distribution
Google’s Gemini Enterprise connects business systems, supplies agents and supports custom workflows. Google also designs TPUs for training and inference. The combination creates a structural challenge for an independent model company: it competes against a provider with both application relationships and infrastructure capabilities. It does not prove that Google has lower realized cost for every task, since utilization, model efficiency and service quality still matter. Gemini Enterprise, Google’s TPU platform
Anthropic’s cloud reach similarly weakens the idea that OpenAI alone can reach enterprise buyers through established platforms. Mistral’s private and on-premises deployment options address buyers who prioritize control and customization. OpenAI must therefore win on the overall deployment outcome: quality, latency, cost, data access, governance and user adoption together. Its consumer brand can open a door; it cannot substitute for evidence that a business process works. Anthropic’s distribution, Mistral’s deployment choices
Safety differentiation must be demonstrated
Anthropic’s Constitutional AI research and OpenAI’s deliberative alignment represent distinct contributions, but both companies now have broader safety systems than a single training method. Buyers should compare behavior under relevant stress tests, transparency about limitations and the controls available in their deployment. A reputation for safety can earn initial consideration; sustained differentiation requires reliable operations and credible incident handling. The same principle applies to claims of superior reasoning: the commercial evidence is better outcomes under realistic constraints.
9. Unit economics, financing and dependencies
OpenAI’s public prices tell us what a customer can be charged, not what OpenAI spends serving that customer. Its gross margin depends on accelerator and memory costs, utilization, throughput, caching, reasoning intensity, monitoring, networking and commercial arrangements. Training, research staff, sales and other costs then sit beyond the direct economics of serving a particular request. A positive contribution on inference does not establish company-level profitability.
A task-cost illustration
Consider an illustrative API workload totaling 100,000 uncached input tokens and 10,000 billable output tokens across its calls, with standard short-context pricing and no tool fees. Applying the rates above gives the following customer charges. The output assumption includes billable reasoning; it is not merely the number of words in the final deliverable.
| Model | Input charge | Output charge | Total illustrative charge |
|---|---|---|---|
| GPT-6 Astra | $1.00 | $0.50 | $1.50 |
| GPT-5.6 Sol | $0.40 | $0.20 | $0.60 |
| GPT-5.6 Terra | $0.20 | $0.12 | $0.32 |
| GPT-5.6 Luna | $0.02 | $0.012 | $0.032 |
Author’s calculations from published rates. These are customer token bills, not estimated OpenAI costs or a claim that all four models complete the same task equally well.
Agent economics become more demanding when attempts fail. If a workflow’s model and tool costs average $0.60 per attempt and only 75% of attempts yield an accepted result, the modeled expenditure per accepted result is $0.80 before human review, assuming the same cost and acceptance mix persists. Ten minutes of expert review can exceed that compute bill by a large multiple. Improving acceptance and reducing review effort may matter more than lowering the price of one token.
For subscriptions, the challenge is pooling heterogeneous users. A lightly used subscription and a heavily used agent subscription can produce the same revenue with very different serving costs. Allowances, model routing, caching and premium tiers help manage this variance. For consumption contracts, the opposite challenge appears: the provider is paid for additional usage, but customers will restrict spending if task value is unclear. Expensive activity is not automatically valuable activity.
Revenue growth does not settle the profitability question
Reuters reported in June, citing The Information’s account of shareholder documents, that OpenAI generated $5.7bn in revenue and burned $3.7bn of cash in the first quarter of 2026. Reuters said it could not independently verify that report. Cash burn is not the same measure as operating loss, and these figures do not disclose product-level margins. Reuters on reported first-quarter results
The analytical implication is that scale and funding requirements can grow together. Revenue run rates, financing valuations and announced compute commitments measure different things. None supplies a complete reconciliation of cash generation, capital expenditure, contractual purchases and working capital. Without audited segment disclosures, confident estimates of a precise ChatGPT, Codex or API margin would overstate what the public evidence supports.
Infrastructure is a major dependency. In April, OpenAI said it had surpassed its target of securing 10GW of US infrastructure capacity and described GPT-5.5 training at the Abilene site on Oracle Cloud Infrastructure using NVIDIA systems. Secured capacity should not be read as an equal quantity of fully commissioned, continuously utilized capacity. Power, construction, interconnection and equipment delivery determine when contracted resources become productive. OpenAI’s infrastructure update
| Dependency or risk | Economic transmission | What would show improvement |
|---|---|---|
| Compute availability and utilization | Shortages constrain usage; underused commitments burden economics. | Reliable capacity delivery, throughput and utilization disclosure |
| External financing | Research and infrastructure can require capital before cash returns arrive. | Improving cash conversion and less dependence on new financing |
| Microsoft and other partners | Licenses, revenue sharing and cloud contracts influence value capture. | Diversified demand with favorable incremental contribution |
| Model commoditization | Customers route tasks to cheaper substitutes when quality is sufficient. | Retention based on workflow value and measurable outcomes |
| Agent reliability and safety | Incidents create remediation expense, interrupted use and lost trust. | Lower consequential failure rates in representative production tasks |
| Data rights and licensed content | Access terms and disputes can increase costs or restrict products. | Sustainable licensing arrangements and clear provenance |
| Enterprise implementation | Custom deployment work can delay adoption and dilute margins. | Shorter deployments and repeatable implementations |
| Product and ecosystem conflict | OpenAI may compete with companies that also buy its API. | Healthy partner economics and a growing third-party application base |
The risks reinforce one another. Aggressive agent adoption can increase revenue and compute consumption simultaneously. A supply commitment can support growth while increasing exposure to demand forecasting. Direct applications can improve customer ownership while alarming developers who depend on the platform. OpenAI’s task is to manage these interactions, not simply maximize one adoption or benchmark metric.
10. The moat and the next phase of growth
OpenAI’s most credible moat is a combination of distribution, frontier research capability, developer adoption, infrastructure access and accumulated workflow integration. None is sufficient alone. A popular interface can lose users if its capabilities lag. A leading model can be replaced in an application if it is too expensive or unreliable. Infrastructure access supports scale, but it also creates financial exposure. The advantage is strongest when the components jointly improve the customer’s outcome.
Workflow integration is likely to be more durable than a short-lived benchmark lead. Users who have configured tools, reusable instructions, projects and review processes incur a real switching cost. Enterprises that have approved access controls and embedded an agent into operations have additional reasons to stay. These advantages should not be exaggerated into an exclusive data flywheel: business data is not automatically available for general model training, and open connectivity standards can make parts of the workflow portable.
The following ranking is an assessment of likely growth contribution, not a disclosed company forecast.
| Priority | Growth candidate | Why it can expand | Evidence needed to validate the thesis |
|---|---|---|---|
| 1 | Codex and professional coding usage | Frequent tasks, measurable artifacts and meaningful customer budgets | Accepted work, retention and revenue growth after usage costs |
| 2 | ChatGPT Work within Business and Enterprise | Existing users can delegate more complete tasks; consumption can grow beyond seat count | Active adoption, renewals and reduced review or completion time |
| 3 | API and cloud-distributed agents | OpenAI can monetize applications it does not need to build or sell itself | Durable production consumption and competitive contribution margins |
| 4 | Financial Services, legal and other specialized workflows | Data, controls and domain integration can support higher customer value | Paid deployment, expert acceptance and repeatable implementation |
| 5 | Advertising | Monetizes a large audience with commercial intent | Incremental advertiser return without weakening user trust |
| Longer horizon | Frontier and deeper process automation | Integration into core systems can create larger, longer-lived contracts. | Production scale, deployment efficiency and defensible operating economics |
The first three are complementary. Codex supplies a concentrated professional use case; Work generalizes delegation across knowledge work; the API and cloud channels put the same capabilities inside other products. Industry offerings can add value where generic models lack reliable context. Advertising funds another part of the audience, with a distinct trust and monetization challenge.
OpenAI’s September release of enterprise usage and outcome analytics is relevant to this transition. The company is giving administrators more tools to relate consumption to activity and results. That is useful infrastructure for renewal conversations, although vendor dashboards and activity counts cannot by themselves prove an economic return. Customers must connect those measures to their own quality, cost and business outcomes. OpenAI’s enterprise measurement update
The decisive question is whether OpenAI becomes the place where useful work reliably gets completed at an attractive total cost. Its audience and technical capability give it a strong starting position. Durable value will come from retaining customers after the initial experimentation, improving the economics of each accepted task and financing infrastructure without allowing commitments to outrun productive demand. That is a more demanding test than model leadership alone, and a more useful way to judge the company’s next phase.
Source approach: This article prioritizes original research, current product documentation, pricing pages, system cards and company agreements. Company adoption and safety claims are attributed; Reuters reporting is identified separately. Product availability and commercial terms can change after the research cutoff. Comparisons, risk assessments and growth priorities are the author’s analysis, not audited segment disclosures or company guidance.