AI Trends25 min

OpenAI "The Deployment Company" Launches $4B Joint Venture — The Enterprise AI Deployment War Has Begun

OpenAI launched a $4B joint venture with 19 investors including SoftBank and Brookfield. COO Brad Lightcap leads enterprise sales, securing direct access to 2,000+ portfolio companies to control the AI deployment channel.

On this page (14)

May 2026 · AI News

OpenAI "The Deployment Company" Launches $4B Joint Venture — The Enterprise AI Deployment War Has Begun

On May 4, 2026, OpenAI created a new company. The name is 'The Deployment Company.' It is a joint venture established with $4 billion raised from 19 investors including SoftBank, Brookfield, and TPG. The company's valuation was set at $10 billion.

This is not a simple fundraise. OpenAI built a separate sales organization dedicated to selling and deploying AI models directly to enterprises. Until now, OpenAI built the technology. Microsoft Azure and partner firms handled actual enterprise adoption. This is a declaration to take direct control of that middle layer.

On the same day, Anthropic also announced a joint venture. It is a $1.5 billion deal with Blackstone and Goldman Sachs. Two companies publicly revealed identical strategies on the same day. 2026 became the year not of the AI model war, but the AI deployment channel war.

Key Summary

  • OpenAI launched 'The Deployment Company' on May 4, 2026 — a joint venture dedicated to AI model sales and deployment
  • $4B raised from 19 PE and investment firms, JV valued at $10B
  • OpenAI retains majority stake and operational control, remainder split among 19 investors
  • COO Brad Lightcap moved to JV CEO, overseeing enterprise software sales
  • Securing access to 2,000+ portfolio companies of partner investors is the key
  • Anthropic·Blackstone·Goldman $1.5B JV also announced on the same date (May 4)
  • Full-scale mid-market competition begins against Microsoft Agent 365 and Google Gemini Enterprise

Table of Contents

  1. The Deployment Company Is a Sales Specialist
  2. Understanding the JV Structure First
  3. What $4B and 19 Investors Mean
  4. Why COO Brad Lightcap Made the Move
  5. Why 2,000 Portfolio Companies Are the Key
  6. Anthropic Also Launched a JV on the Same Day
  7. Difference from Microsoft Agent 365 and Google Gemini
  8. The Consulting Industry Is Shaking
  9. What Happens to the Azure Relationship
  10. OpenAI Enterprise API — Real Adoption Scenarios
  11. How to Switch from Azure OpenAI to a Direct Contract
  12. Which Companies Should Use This JV
  13. The AI Deployment Channel War Has Begun
  14. Frequently Asked Questions

The Deployment Company Is a Sales Specialist

The name says it all. 'The Deployment Company' — a company that specializes in deployment. It is not an organization that builds models. It is an organization that embeds those models into enterprises. This is the first time OpenAI has separated technology development from sales.

Until now, OpenAI's enterprise sales ran on two tracks. One was the direct ChatGPT Enterprise sales team. The other was the Microsoft channel through Azure OpenAI. Both had limits. The direct sales team was small in scale. The Azure channel was tied to Microsoft infrastructure. The Deployment Company is the third path.

Brad Lightcap described this as "accelerating enterprise AI adoption." Enterprises want to adopt AI but do not know where to start. Lowering that barrier to entry is the company's role. It covers the entire process from software licensing to implementation support.

OpenAI's previous enterprise strategy was reactive — waiting for companies to come to them and then signing contracts. The Deployment Company is the opposite. It reaches out first through PE networks and creates the contracts. The sales approach itself has changed.

Understanding the JV Structure First

A JV (Joint Venture) is a separate legal entity created by two or more companies pooling capital and resources. It is like two banks jointly establishing a separate shared payment infrastructure company. The Deployment Company is structured so that OpenAI holds a majority stake while 19 investors split the remainder.

The majority stake matters. OpenAI can determine strategic direction unilaterally. Investors are not in a position to intervene in management. Their role is to provide capital and portfolio access. Management involvement is limited.

The revenue structure runs on two axes: license sales and implementation support fees. Software is sold on a monthly subscription like SaaS, with additional fees charged for adoption support projects. From OpenAI's perspective, direct service revenue is created beyond API revenue.

The reason PE investors are putting up money is also clear. If AI is embedded in portfolio companies first, those companies increase in value. Return on investment improves. OpenAI gets a sales channel; PE firms get portfolio value appreciation. The interests align well.

What $4B and 19 Investors Mean

TPG, Brookfield, Advent International, Bain Capital, SoftBank, Dragoneer, and 19 others participated. This should not be viewed purely as a fundraise. The portfolio companies these investors hold are the real objective.

PE firms typically hold tens to hundreds of companies in their portfolio. Add up the partners and the number exceeds 2,000. Translated into sales language: OpenAI secured thousands of verified sales channels at once. Not cold outreach — trust-based sales through existing investor relationships.

$4B was raised at a $10B valuation. That means 40% of the equity went to outside investors. OpenAI kept the majority while simultaneously getting capital and channels. A capital-efficient deal. As The Deployment Company grows past $10B, OpenAI's equity value rises with it.

SoftBank has already invested billions in OpenAI. Participating in this JV is an additional bet. SoftBank's portfolio spans Japanese, Asian, Middle Eastern, and Latin American companies. This signals that The Deployment Company's geographic reach may be broader than expected.

Why COO Brad Lightcap Made the Move

OpenAI COO Brad Lightcap moved to lead The Deployment Company. COO is the role that oversees all internal company operations. Leaving that seat to move into an enterprise sales organization makes the JV's importance unmistakable.

Lightcap is the person who first designed OpenAI's enterprise business. He is the key figure who brought ChatGPT Enterprise to market and built the API partnership with Microsoft. His leadership of the JV means OpenAI's core revenue strategy is now concentrated here.

It is rare for a COO-level person to move from a technology company into a sales organization. Even rarer in AI companies with strong developer cultures. OpenAI broke that convention. If model development is Sam Altman's war, enterprise sales became Lightcap's war.

What Brad Lightcap's Move Means

The move from COO to JV CEO is not a demotion. It is placing the most trusted person on the front line at the moment when OpenAI's revenue center of gravity shifts from APIs to direct enterprise contracts. Industry analysts read this as a "vanguard deployment." This JV is OpenAI's next growth engine.

Why 2,000 Portfolio Companies Are the Key

Standard B2B AI sales is slow. Signing a contract with a single large enterprise takes six months to a year. The approval chain is long and security reviews are required. AI adoption takes even longer. Including technology validation, data governance, and employee training, full adoption can take two years.

The Deployment Company bypasses this bottleneck through investor relationships. When Brookfield recommends OpenAI adoption to a portfolio company, decisions come faster. The relationship between an investor and an investee is different from the relationship between a salesperson and a potential customer. Trust is already established. It is a recommendation that borders on compulsory.

This structure has been validated before. Oracle and SAP accelerated ERP adoption through PE partnerships. Salesforce expanded CRM penetration speed through investor networks including Bain Capital. AI follows the same pattern. The Deployment Company applies an already-proven enterprise software sales formula to AI.

It is not just about the numbers. PE portfolio companies are mostly mid-size to large enterprises. Companies that want to adopt AI but lack the internal technical capability to do so. Below the Fortune 500 that Microsoft and Google focus on, the mid-market that has not yet adopted AI is concentrated here. That is The Deployment Company's real target segment.

Anthropic Also Launched a JV on the Same Day

On May 4, 2026, Anthropic also announced a joint venture with Blackstone and Goldman Sachs. The scale is $1.5 billion. Two companies publicly revealed identical strategies on the same day. The timing is too precise to be a coincidence. Market preemption races erupted simultaneously.

The two JV structures are similar. The AI company retains a majority stake while PE investors provide portfolio access. The differences are scale and industry focus. The OpenAI JV is $4B and targets all industries. The Anthropic JV is $1.5B and focuses on finance and real estate. Blackstone manages over $1 trillion in real estate assets — the world's largest PE firm.

Goldman Sachs's participation is also worth noting. In banking, AI use must prioritize regulatory compliance. The fact that Claude emphasizes safety through Constitutional AI works in its favor in a financially regulated environment. That is why Anthropic is targeting the financial sector first.

The two strategies directly collide in overlapping customer segments. Large financial sector enterprises are targets for both the OpenAI JV and the Anthropic JV. Which model is safer and more regulation-compliant becomes the selection criterion. Competition in the financial AI market will intensify in the second half of 2026.

OpenAI JV vs Anthropic JV Comparison

Item OpenAI JV Anthropic JV
JV Name The Deployment Company Undisclosed
Funding Size $4B $1.5B
Valuation $10B Undisclosed
Key Investors SoftBank, Brookfield, TPG, Bain Capital, and 19 others Blackstone, Goldman Sachs
Portfolio Access 2,000+ (all industries) Finance & real estate focused
JV CEO Brad Lightcap (Former COO) Undisclosed
AI Company Stake Majority + operational control retained Majority presumed retained
Announcement Date May 4, 2026 May 4, 2026

Difference from Microsoft Agent 365 and Google Gemini

Microsoft officially launched Agent 365 in April 2026. It builds on 300 million M365 subscribers. Copilot was integrated into Word, Excel, and Teams. AI is sold through the existing channel without a separate JV. Sales costs are almost zero. It is a model of layering AI on top of existing renewal contracts.

Google bundles Gemini Enterprise with Workspace. AI attaches to Google Meet, Docs, and Gmail. Again, existing channels are used. Both companies' strength is their existing customer base. The structure is not about finding new customers but about selling more to customers already in hand.

The customers The Deployment Company targets are different. Enterprises unsatisfied with existing Microsoft and Google products. Mid-market companies that have not yet adopted AI. PE portfolio companies are heavily represented here. Companies whose annual contract size is mid-range or below and get pushed down the priority list of Microsoft's enterprise sales team.

Customization depth is also different. Microsoft Copilot operates within the bounds of M365. The Deployment Company provides consulting-level support that redesigns entire business workflows with AI. The difference between a standardized product and a tailored service.

Enterprise AI Deployment Channel Comparison (2026)

Item OpenAI JV Microsoft Agent 365 Google Gemini Enterprise
Sales Channel Direct PE network access Existing M365 subscription renewal Workspace bundle sales
Primary AI Model GPT-4o, o3 series GPT-4o (via Azure) Gemini 2.5 Pro
Primary Target Non-adopting mid-market & enterprises Existing Microsoft customers Existing Google Workspace customers
Customization High (dedicated support) Medium (within M365 scope) Medium (within Workspace scope)
Adoption Entry Point Access through investor relationships Added at existing contract renewal Added at existing contract renewal
Minimum Contract Size Large scale (undisclosed) From $30/user/month From $20/user/month

The Consulting Industry Is Shaking

McKinsey, Accenture, and Deloitte have been generating significant revenue from AI adoption projects. Enterprises adopting AI need strategy development, system implementation, and employee training. Projects run tens of millions of dollars each. The AI boom created a golden era for consulting firms.

If The Deployment Company handles implementation directly, the story changes. If Lightcap expands beyond 'software sales' to owning 'the entire deployment,' consulting firms become subcontractors. Strategy consulting survives, but implementation revenue disappears. That is 60 to 70 percent of total AI project revenue.

In the short term, coexistence holds. When The Deployment Company wins a contract, implementation goes to partner consulting firms. But if OpenAI moves toward building its own implementation team, the structure changes. The middleman role disappears.

Consulting firms have already moved to preempt this. Accenture struck a $3B partnership with OpenAI. McKinsey also announced a strategic partnership. The strategy is to claim the partner position before becoming a subcontractor. Even so, it is hard to stop the shift of implementation leadership to AI companies.

OpenAI Official Announcement Quote

"The Deployment Company will help accelerate the adoption of AI across the enterprise. Brad Lightcap will lead the company, bringing his experience building OpenAI's commercial operations."

— OpenAI Official Blog, May 4, 2026

What Happens to the Azure Relationship

Microsoft has invested over $13B in OpenAI. Azure OpenAI is the primary channel through which enterprises use GPT models via API. A significant portion of OpenAI's current revenue runs through Azure. That partnership is maintained. The Deployment Company does not nullify that contract.

The Deployment Company is a direct sales channel that bypasses Azure. From Microsoft's perspective, a former partner is turning into a direct competitor. However, a fully adversarial collision involves complex legal entanglements. How Microsoft responds is the biggest storyline to watch in the second half of 2026.

Short-term coexistence is the likely scenario. Azure targets large enterprises with dedicated technical teams — companies that handle APIs directly and manage their own infrastructure. The Deployment Company goes after mid-market companies that want fast adoption over deep technical internalization. The customer segments do not overlap immediately.

Long-term conflict is inevitable. Once mid-market companies adopt AI, they eventually grow into large enterprises. At that point, a fork emerges — Azure or a direct OpenAI contract. This is the first move in OpenAI's process of gaining independence from Microsoft. Microsoft knows this too.

OpenAI Enterprise API — Real Adoption Scenarios

When contracting through The Deployment Company, what actually changes? The core is organization-level API access. Team-level usage management, audit logs, and access controls are set up at once. The structure is entirely different from individual API keys. It meets the enterprise standards security teams require.

With an enterprise contract, OpenAI assigns a dedicated organization ID. Including this ID in API calls enables usage tracking and billing at the organizational level. Department-level cost allocation is also possible. Below is a basic curl example for checking organization settings and creating separate department-level projects.

# Check organization-level settings
curl https://api.openai.com/v1/organization/settings \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "OpenAI-Organization: org-XXXXXXXXXX" | jq '.'

# Create separate project by department (Finance team example)
curl -X POST https://api.openai.com/v1/organization/projects \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "OpenAI-Organization: org-XXXXXXXXXX" \
  -H "Content-Type: application/json" \
  -d '{"name": "finance-ai-prod", "description": "Finance team AI automation project"}'

# Response example: {"id": "proj-XXXXXXXXXX", "name": "finance-ai-prod", "status": "active"}

Both the Python SDK and TypeScript SDK accept an organization ID as a parameter. Changes from existing API key-based code are minimal. Below is a Python example for batch AI readiness assessment of PE portfolio companies. It is a pattern similar to what The Deployment Company actually implements.

from openai import OpenAI
from typing import TypedDict
import json

client = OpenAI(
    api_key="sk-...",
    organization="org-XXXXXXXXXX",
    project="proj-XXXXXXXXXX" # Enterprise project isolation
)

class CompanyProfile(TypedDict):
    name: str
    sector: str
    revenue: str
    headcount: int

def assess_ai_readiness(company: CompanyProfile) -> dict:
    """Batch AI readiness assessment for PE portfolio companies"""
    response = client.chat.completions.create(
        model="gpt-4o",
        messages=[
            {"role": "system", "content": "You are an enterprise AI adoption consultant. Analyze the company profile and assess AI adoption priority and estimated ROI."},
            {"role": "user", "content": f"Company profile:\n{json.dumps(company, ensure_ascii=False, indent=2)}"}
        ],
        temperature=0.3,
        max_tokens=800,
        response_format={"type": "json_object"}
    )
    return json.loads(response.choices[0].message.content)

portfolio = [
    {"name": "ACME Manufacturing", "sector": "Manufacturing", "revenue": "$500M", "headcount": 2000},
    {"name": "FinCorp Analytics", "sector": "Finance", "revenue": "$200M", "headcount": 500},
]
results = [assess_ai_readiness(c) for c in portfolio]

The Agents API allows complex business workflows to be automated with AI agents. An agent is an AI program that performs multi-step tasks — an assistant that handles multiple steps on its own from a single instruction. Contract review, financial data analysis, and customer response automation are the main examples. This is the type of workflow The Deployment Company proposes first to portfolio companies.

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.OPENAI_API_KEY,
  organization: process.env.OPENAI_ORG_ID,
  project: process.env.OPENAI_PROJECT_ID,
});

// Contract review agent — legal team AI assistant
async function reviewContract(contractText: string): Promise<{
  risks: string[];
  summary: string;
  recommendation: "approve" | "review" | "reject";
}> {
  const thread = await client.beta.threads.create();
  await client.beta.threads.messages.create(thread.id, {
    role: "user",
    content: `Review the following contract and analyze the risks.\n\n${contractText}`,
  });
  const run = await client.beta.threads.runs.createAndPoll(thread.id, {
    assistant_id: process.env.LEGAL_ASSISTANT_ID!,
    instructions: "Identify contract risks based on legal team standards. Respond in JSON format.",
    response_format: { type: "json_object" },
  });
  if (run.status !== "completed") throw new Error(`Agent run failed: ${run.status}`);
  const messages = await client.beta.threads.messages.list(thread.id);
  const last = messages.data[0].content[0];
  if (last.type !== "text") throw new Error("Response is not text type");
  return JSON.parse(last.text.value);
}

// Result: { risks: ["..."], summary: "...", recommendation: "review" }
const result = await reviewContract(contractContent);
console.log(`Recommendation: ${result.recommendation}, Risks: ${result.risks.length}`);

How to Switch from Azure OpenAI to a Direct Contract

If you are currently using Azure OpenAI, calculate migration costs first. Code changes are not large. Replace the Azure-specific endpoint with the OpenAI standard endpoint. The SDK interface is nearly identical. The technical migration itself can be completed in a day or two.

Data residency is the key consideration. Azure OpenAI processes data in specific regions. In Europe, the EU region can be specified; in the US, the US region. With a direct OpenAI contract, data passes through OpenAI infrastructure. European and financial sector enterprises must conduct GDPR and financial regulation compliance reviews first.

The cost structure also changes. Azure charges per token with Azure infrastructure costs on top. A direct contract allows volume discount negotiation. The larger the annual usage, the more favorable the direct contract. Direct contract evaluation becomes meaningful at a monthly scale of $100K or more.

Azure OpenAI → OpenAI Direct Contract Migration Checklist

  • ① API Endpoint Replacement{resource}.openai.azure.comapi.openai.com
  • ② Organization ID Setup — Add OpenAI-Organization to API call headers
  • ③ Data Residency Review — Legal review for GDPR and financial regulation compliance first
  • ④ Billing Structure Renegotiation — Confirm volume-based discount rates and agree on contract terms
  • ⑤ Security Team Audit Log Review — Verify organization-level log format changes
  • ⑥ Department-Level Project Separation — Set up cost attribution under organization ID subprojects

The migration itself takes a few days. The review takes longer. The legal and security team approval cycle determines the actual migration timeline. In regulated industries, this can take six months. Preparing the technical side first while running the legal review in parallel is the faster approach.

Azure OpenAI vs OpenAI Direct Contract: Pros and Cons

Azure OpenAI

Pros

  • Can use existing Azure credits
  • Clear data residency (EU/US)
  • Easy integration with Azure infrastructure
  • Start immediately without separate negotiation

Cons

  • Azure margin adds cost
  • New model release delays (Azure deployment cycle)
  • Customization constraints

OpenAI Direct Contract

Pros

  • Volume discount negotiation available
  • Immediate access to latest models
  • Dedicated technical support (large contracts)
  • High customization flexibility

Cons

  • Unclear data residency
  • High minimum contract size (estimated)
  • Requires separate infrastructure setup

Which Companies Should Use This JV

If you are already on Microsoft 365 and adopting AI for the first time, adding Copilot is the fastest path. It activates with a single checkbox on your existing account. Company-wide deployment is possible without a dedicated technical team. If AI is at the "let's just try it" stage, Microsoft has the lowest entry barrier.

For Google Workspace-based organizations, Gemini Enterprise is the natural fit. AI attaches to Docs, Sheets, and Meet. AI can be added without changing existing workflows. If you want to start fast within the Google ecosystem, this is the realistic choice.

If neither platform is in use, or if a business-specific AI is needed, The Deployment Company becomes an option. For PE portfolio companies, investors come to you first with a proposal. For companies in regulated industries, Anthropic JV (Blackstone network) is also worth evaluating alongside this one.

Running multiple channels in parallel is also a strategy. Boost employee productivity with Microsoft Copilot while automating core business workflows with a direct OpenAI contract. Think of them as layers, not competitors. In practice, large enterprises often run both channels simultaneously.

AI Deployment Channel Selection Guide by Situation

Situation Recommended Channel Reason
Existing Microsoft 365 customer Add Microsoft Copilot Activate existing account, minimal entry barrier
Google Workspace based Gemini Enterprise Integrates with existing Docs·Sheets·Meet
PE portfolio company The Deployment Company Direct access through investor, dedicated support
Finance & real estate regulated industry Anthropic JV (Blackstone channel) Safety emphasized via Constitutional AI
Non-adopting mid-market, customization needed The Deployment Company Beyond standard product limits, dedicated implementation support
Large-scale API usage, company with tech team Azure OpenAI or direct contract Volume negotiation or existing Azure infrastructure

The Deployment Company: Pros and Cons of Adoption

Pros

  • Fast contract cycle based on PE investor relationships
  • Dedicated onboarding support team assigned (differentiated from standard API contracts)
  • Custom implementation support for business workflows
  • Volume-based price negotiation available
  • Immediate access to latest OpenAI models

Cons

  • Opaque pricing — individual negotiation structure
  • Early stage operations — unproven track record
  • Separate review needed for data residency compliance
  • Mid-size to large enterprise focused, not SMBs
  • Access path unclear for non-PE portfolio companies

The AI Deployment Channel War Has Begun

The core of the 2026 AI market is not model performance. It is who can embed AI into more enterprises. The Deployment Company is OpenAI's version of that war. Anthropic, Microsoft, and Google are all running in the same direction. PE networks, existing subscription channels, partnerships — the approaches differ but the goal is the same.

Until now, the enterprise AI market was summarized as "demand outpaces supply." Many companies wanted to adopt AI but did not know where to start. The Deployment Company aims to fill that vacuum. It reaches out first through PE networks and walks alongside the entire adoption process.

From an enterprise perspective, the options have expanded. At the same time, the homework of deciding "which channel fits my situation" has arrived. Existing infrastructure, technical team capability, regulatory environment, adoption speed — use these four criteria to choose a channel. Wait, and someone will come to you with a proposal. For PE portfolio companies, that timing may be sooner than expected.

Frequently Asked Questions

How is The Deployment Company different from OpenAI headquarters?

OpenAI headquarters focuses on model development. The Deployment Company is a joint venture specializing in selling those models to enterprises and supporting adoption. It operates as a separate legal entity while OpenAI retains a majority stake and operational control. It is the first time OpenAI has separated the organization that builds the technology from the organization that sells it. The two organizations operate independently while pointing in the same direction.

Did Brad Lightcap resign as COO?

Based on the official announcement, he moved to lead the JV. Whether he retains the OpenAI COO title is not yet clear. In practice, the structure has him focused on the new role. It is a personnel signal that OpenAI views this JV as its most important revenue growth engine. It is unusual for a COO-level person at a technology company to lead a sales organization.

How does it differ from the Anthropic·Blackstone·Goldman JV?

The Anthropic JV is $1.5B in scale, targeting a PE network specializing in finance and real estate. The OpenAI JV is $4B, targeting 2,000+ portfolio companies across all industries from 19 investors. They differ in scale and industry scope. In large financial sector enterprises, the two JVs directly collide. Validation is needed on which AI is more suitable for financial regulations.

What happens to the existing Azure OpenAI service?

Azure OpenAI remains intact. The Deployment Company is a direct sales channel that bypasses Azure. It is a structure for entering the enterprise market directly, separate from the Microsoft partnership. In the short term, the target customer segments differ, so coexistence holds. Long-term, as mid-market companies grow, there is potential for channel conflict.

Is the consulting industry threatened by this JV?

In the short term it is a coexistence structure. When The Deployment Company wins a contract, implementation goes to partner consulting firms. However, if OpenAI expands to handle implementation directly, it overlaps with the AI business territory of McKinsey and Accenture. Accenture and McKinsey have already responded preemptively through OpenAI partnerships. Even so, the trend of implementation leadership shifting to AI companies is hard to stop.

How much does adoption through The Deployment Company cost?

No official price list has been published. Enterprise contracts are individually negotiated based on volume and industry. It is generally expected to exceed the ChatGPT Enterprise level ($30/user/month). Implementation support fees are likely priced separately. PE portfolio companies may receive different terms through their investors.

Can Korean companies contract through this JV?

Since SoftBank is among the participating investors, access to Asian portfolio companies is expected. Whether a direct Korea office will be established is still undecided. Currently, the realistic path for large Korean enterprises is the Azure OpenAI channel or a direct ChatGPT Enterprise contract. The Deployment Company's Asia expansion plans are expected to take shape after the second half of 2026.

Which is cheaper, OpenAI direct contract or Azure OpenAI?

For small-scale usage, Azure OpenAI is advantageous because existing Azure credits can be applied. For large enterprise volumes, a direct OpenAI contract may be more favorable. Volume discount negotiation is possible and the Azure margin is eliminated. Direct contract evaluation becomes meaningful at a scale of $100K or more per month.

Related Articles

This article was written based on publicly available information as of May 6, 2026. Figures and citations are based on the time of announcement and may change. · GoCodeLab

Share