Fujitsu brings Claude to 100,000 staff and adds Codex to SI delivery

AI 요약

• What happened: Fujitsu announced collaborations with OpenAI and Anthropic on May 27, 2026.
  • The Anthropic deal includes Claude use by about 100,000 Fujitsu Group employees and a 1,000-person engineering team, while the OpenAI deal brings ChatGPT Enterprise and Codex into FDE, manufacturing, healthcare, and cybersecurity work.
• Why it matters: This is less about choosing one frontier model and more about a large Japanese SI company turning multiple models into a delivery system.
• Builder impact: Enterprise AI adoption is shifting from chatbot seats toward FDE, coding agents, audit logs, permission design, and model-specific operating policy.
• Watch: Fujitsu's announcements describe plans and partnership scope, not customer ROI. Cost, data residency, access control, and failure responsibility still have to be proven in deployments.

Fujitsu announced a strategic partnership with Anthropic on May 27, 2026. On the same day, it also announced a collaboration with OpenAI. Either announcement can be read as a familiar enterprise AI update: one says Fujitsu will use Claude at scale, the other says it will use ChatGPT Enterprise and Codex. Together, they point to something more specific. Fujitsu is putting OpenAI and Anthropic into the same AI services portfolio and using them to reshape its Forward Deployed Engineer model, systems integration work, and industry delivery in Japan.

The numbers in the Anthropic announcement are large. Fujitsu says about 100,000 Fujitsu Group employees will actively use Claude to speed up work and validate safe, transparent, controllable AI use inside the company. Anthropic chief commercial officer Paul Smith also refers to a 1,000-person engineering team that will help customers adopt the technology. The OpenAI announcement says Fujitsu employees will use ChatGPT Enterprise and Codex across development, operations, proposals, and service delivery. In both cases, Fujitsu is treating internal use as something close to a Customer Zero program: prove the operating model inside the company, then turn the lessons into customer-facing methodology.

Source: Fujitsu's May 27, 2026 OpenAI collaboration announcement.

The timing also matters. Two days earlier, on May 25, Fujitsu announced a self-evolving multi-AI-agent technology and a 28-point average accuracy improvement for its Takane model. That earlier announcement described Fujitsu's own LLM and self-improvement loop. The May 27 announcements show which external model companies Fujitsu wants to place around that internal stack. Fujitsu is not abandoning Kozuchi or Takane. It is adding Claude, ChatGPT Enterprise, and Codex as selectable materials for customer-specific AI solution design, integration, and operation.

That is a simple statement, but it changes the business logic for a systems integrator. If a customer buys only a model subscription, Fujitsu's role narrows. If the customer needs model selection, data controls, workflow redesign, software delivery, evaluation, security operations, and internal enablement, Fujitsu can sell the integration and operating layer around the model. The model is no longer just the delivered product. It becomes part of the delivery method.

The two partnerships have different jobs

The Anthropic announcement puts trust and mission-critical systems at the center. Fujitsu explicitly refers to advanced AI use in government, finance, healthcare, defense, and critical infrastructure. Those environments are not normal SaaS rollouts. They require data residency, regulatory compliance, security, performance guarantees, auditability, and clear human responsibility. Fujitsu says it will combine Claude with its own Kozuchi and Takane technologies to provide AI solution selection, design, and integration based on customer requirements.

The OpenAI announcement leans more toward delivery and productivity. Fujitsu says it will add OpenAI technology to its AI service lineup and combine ChatGPT Enterprise and Codex with its FDE model. It also names manufacturing customers and existing FDE experience. The statement that OpenAI tools will be used for development, operations, proposals, and delivery is broader than a normal internal productivity rollout. Sales proposals, requirements work, code changes, operational automation, and customer-system delivery are being pulled into one AI-enabled operating model.

The split is visible. Anthropic is attached to Claude at roughly 100,000 internal users, critical infrastructure, cyber defense, safety, and a 1,000-person engineering team. OpenAI is attached to Codex, ChatGPT Enterprise, manufacturing, healthcare and pharmaceuticals, cybersecurity, proposals, and delivery workflows. For customers, the buying question becomes less "Claude or GPT?" and more "which work should run on which model, under which controls, with which accountable delivery team?"

FDE becomes the wrapper for AI-era SI

Fujitsu repeats one term across the announcements: FDE. Forward Deployed Engineer is best known from Palantir's field-heavy engineering model. Engineers work close to the customer, define the problem in the actual operating environment, inspect data and process constraints, and adapt software quickly around the work. Fujitsu's Anthropic announcement refers to practical FDE experience built with advanced technology partners including Palantir. The OpenAI announcement says Fujitsu will strengthen and expand the FDE model.

FDE is returning to the front because enterprise agents are not install-and-forget software. A useful agent has to understand customer documents, permissions, legacy systems, approval paths, security policy, and budget controls. Codex cannot safely change code unless it knows repository access, CI behavior, issue tracking, security scanning, review gates, and deployment authority. Claude cannot help with critical infrastructure work unless the organization defines which data can leave which boundary, where logs are retained, and when a human must approve an action. Selling a model API does not solve those problems.

From Fujitsu's perspective, AI is both a threat to traditional SI and a new reason for SI to exist. If Codex reduces part of the software development workload, headcount-based project estimates come under pressure. At the same time, customers need a partner to design model policies, connect systems, build evaluations, configure permissions, train staff, and operate the resulting workflow. Fujitsu's statement that it wants to transform the system integration business itself should be read through that calculation. AI becomes the way work is delivered, not only the thing being delivered.

Anthropic is gaining Japanese enterprise distribution

Fujitsu's announcement is not an isolated Japanese enterprise event. NEC announced a collaboration with Anthropic on April 23, 2026. NEC said it would combine Claude Opus 4.7, Claude Code, and Claude Cowork with NEC BluStellar Scenario and introduce Claude to about 30,000 NEC Group employees. The target industries include finance, manufacturing, local government, and cybersecurity. Hitachi followed with a strategic partnership around May 18 and 19, saying it would deploy Claude across about 290,000 employees, develop 100,000 AI professional talent, and establish a Frontier AI Deployment Center.

Put the numbers together and a pattern appears. NEC points to 30,000 internal users. Fujitsu points to 100,000. Hitachi points to 290,000. All three tie internal rollout to industry-specific customer solutions. All three emphasize safety, trust, cybersecurity, and mission-critical work. Anthropic is positioning itself not only as a model provider, but as a transformation partner for Japanese systems integrators, manufacturers, and social-infrastructure companies.

OpenAI enters the same customer base through Fujitsu. Fujitsu says the OpenAI collaboration will focus on manufacturing, healthcare and pharmaceuticals, and cybersecurity. That is a different market from the consumer ChatGPT app. Customers in those sectors care about factory knowledge, hospital and pharmaceutical regulation, security operations, data sovereignty, Japanese business documents, and legacy integration. For OpenAI, Fujitsu can translate the technology into the terms large Japanese enterprise buyers actually use.

Multi-model strategy is a defense mechanism

Fujitsu did not pick only OpenAI or only Anthropic. That is one of the more important details. Single-model standardization simplifies procurement and operations, but it also increases lock-in, cost exposure, model-regression risk, and policy risk. AI product teams in 2026 do not suffer from too few model choices. They suffer from changing prices, rate limits, quality profiles, safety policies, and product packaging. A coding model that is attractive this quarter can change its cost structure next quarter. A general chat model can regress on a domain-specific workflow after an update.

A multi-model strategy spreads that risk. Claude can take long-context reasoning and enterprise-trust workloads. Codex can sit closer to development workflows and automation. Takane and Kozuchi can support Japanese-language, industry-specific, and data-sovereignty requirements. The trade-off is integration cost. Prompts, tool schemas, evaluation sets, permission policy, logging formats, retention settings, and cost dashboards can differ by model. A company like Fujitsu can sell the work of absorbing that complexity for customers.

For developers, this is more than writing an API wrapper. A platform that uses OpenAI and Anthropic together needs model routing, fallback rules, evaluation suites, data redaction, usage budgets, and task-specific policy. Giving Codex repository access is a different risk from giving Claude business documents. Treating both as generic "AI use" will fail at audit time. Fujitsu's repeated language around safety, transparency, and controllability can sound abstract, but implementation turns those words into permission tables, audit logs, approval queues, budget limits, incident paths, and rollback procedures.

The 100,000-user rollout is an experiment, not proof of outcome

Fujitsu's planned Claude rollout to about 100,000 employees is a large internal adoption number. It should not be read as customer ROI. The official announcement does not provide productivity-improvement metrics, defect-rate changes, delivery-time reductions, or customer outcomes. The more precise reading is that Fujitsu wants to use internal deployment as an operating experiment. It will test safe and responsible AI adoption with its own employees, then use the resulting insights and standardized approaches with customers.

That approach has a clear benefit. Fujitsu can tell customers that it has run the controls on itself first. Real use across development, proposals, operations, and delivery can reveal which cases waste money, which access boundaries are needed, which prompts fail, and which teams need training. It also has a large operational burden. Once 100,000 people start using AI tools, model cost, sensitive-data entry, output validation, hallucination responsibility, internal support, and performance measurement all become management problems.

The public developer-community reaction appears muted so far. A shared Fujitsu announcement in r/Anthropic produced only a small discussion, including skepticism about Fujitsu's past software quality and the practical effectiveness of large SI rollouts. Broader Reddit discussion around Anthropic's enterprise adoption has focused more on Claude cost control and budget governance. That muted reaction does not make the deal irrelevant. Many enterprise AI changes that matter to model revenue and organizational adoption happen quietly through internal rollouts and systems-integration contracts rather than public developer excitement.

Questions customers should ask before adoption

The fact that Fujitsu has both OpenAI and Anthropic partnerships does not automatically reduce customer risk. It increases choice, but it also complicates responsibility. Customers should require written answers for which data goes to which model, how retention and training-use policies differ by provider, where logs live, who approves Codex-generated code changes, and who is accountable when Claude assists a business decision.

Manufacturing, healthcare, pharmaceuticals, and cybersecurity make those questions sharper. Manufacturing process knowledge and design data are competitive assets. Healthcare and pharmaceutical documents can contain personal information, regulated records, and evidence for audits. Cybersecurity work touches vulnerability details, attacker behavior, and internal exposure. Fujitsu says safety, transparency, and controllability are part of the approach. Customers should look for the concrete artifacts behind those words: data processing terms, access-control design, sample audit logs, incident response procedures, model-fallback criteria, and human approval rules.

AI platform teams can apply the same questions internally. Can Codex and Claude access the same repositories and documents? Where are model-specific spending limits enforced? Do AI-generated proposals, code changes, and document edits remain visible as reviewable diffs? If one model has an outage or quality regression, which workflows move elsewhere and which stop? When internal logs become future prompt or evaluation data, how is sensitive information removed? Without answers, multi-model strategy becomes operational confusion rather than resilience.

What SI companies will compete on next

Fujitsu's May 27 announcements are not a flashy model launch. There is no new benchmark claim and no new model name. The signal is about how enterprise AI gets sold and operated. Large customers do not buy only a model. They buy business analysis, permission design, security operations, staff enablement, performance measurement, legacy-system integration, and accountability. OpenAI and Anthropic provide frontier models and agent products. Fujitsu translates those products into industry language, systems language, and delivery process.

In that market, SI competition will not be settled by headcount alone. A 1,000-person engineering team is useful only if it can evaluate AI-generated changes and control deployment risk. FDE is useful only if field teams can map customer permissions, data boundaries, and operational constraints instead of stopping at a proof of concept. Supporting both Codex and Claude is useful only if model strengths, costs, policies, and failure modes are measured instead of hidden behind a single AI label.

The message from Fujitsu is clear enough: AI-era SI is moving away from simply adding more developers to a project and toward packaging models, tools, workflows, security, and evaluation into one operating system. Whether Fujitsu can execute that shift is not proven by the announcement. The evidence will come from customer cases: time saved in manufacturing processes, error-rate changes in healthcare and pharmaceutical workflows, security detection and response improvements, and transparent reports on data and permission controls.

For developers and AI product teams, the practical conclusion is narrow. Using OpenAI and Anthropic together is not a strategy by itself. Teams need to decide which tasks each model can handle, which data each model may see, which permissions each agent can use, which quality metrics matter, and which cost thresholds stop a workflow. Fujitsu's Claude rollout and Codex adoption are the starting signals. The real test is whether multi-model enterprise AI can survive inside customer legacy systems with defensible cost, security, audit, and responsibility boundaries.