Anthropic Software / SaaS North America

Stripe

Application Refactoring

Stripe needed a CLI-native coding assistant that met enterprise security requirements and could be safely distributed to engineers without exposing corporate laptops to unapproved JavaScript packages or an unmanaged npm dependency chain.

1,370 engineers using Claude Code
10,000 lines of code migrated in 4 days
A Scala-to-Java migration using Claude models that would have taken an estimated 10 engineering weeks by hand
two to three months of testing and iteration

Reported impact

Business outcome

Stripe deployed Claude Code to 1,370 engineers through a zero-configuration enterprise rollout. One team migrated 10,000 lines of Scala to Java in four days, work estimated at ten engineering weeks by hand, enabling an upgrade to a newer JDK. Engineers reported higher satisfaction with their tooling, and Stripe is exploring agent-based incident detection and resolution.

  • Productivity Improvement
  • Speed to Market

Solution

Stripe's developer infrastructure team chose Claude Code for engineers who prefer a command-line workflow and worked with Anthropic over two to three months to produce a signed enterprise binary. The binary bypasses Claude Code's npm dependency chain, addressing concerns about supply-chain attacks from random JavaScript packages on corporate laptops. Stripe distributes it through its internal mechanism, pre-installed on laptops and development boxes and pre-configured with rules, tokens, and authentication, so engineers can use it without self-service accounts or setup. Engineers supply repository and documentation context; Claude Code understands the codebase, edits files, and runs commands while developers review and adapt outputs. The article reports a concrete Scala-to-Java migration using Claude models and describes training, all-hands, and team-level sharing to improve use. The story does not specify a separate data store or an automated deployment flow.

Data flow

Stripe engineers use pre-installed, pre-configured Claude Code with their codebase and internal documentation as context; Claude Code edits files and runs commands, and engineers review resulting changes. For a Scala-to-Java migration, Claude models converted 10,000 lines and enabled an upgrade to a newer JDK.

Solution architecture

2 components · 1 layer
  1. Uncategorized
    • Claude Code Provides a CLI-native coding assistant that reads Stripe codebases, edits files, and runs commands.
    • Claude models Assist Stripe engineers with code changes, including the reported Scala-to-Java migration.

Architecture clues

  • Anthropic produced a signed enterprise binary that bypassed the npm dependency chain.
  • Claude Code was pre-installed on laptops and development boxes and pre-configured with rules, tokens, and authentication.
  • Stripe reports 5.5 nines of reliability and is exploring agents for incident detection and resolution.

Evidence from the source

Deployed Claude Code to 1,370 engineers with a zero-configuration setup that works immediately on every developer's machine
It's pre-installed on everyone's laptop. It's pre-installed on everyone's development box. It's pre-configured with the rules, the tokens, the authentication.
Migrated 10,000 lines of Scala to Java in four days, a project estimated at ten engineering weeks without AI assistance
Transparency Evidence & methodology 100/100 reference value · 80% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence80%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Anthropic

    Stripe Claude Code case study

    First-party
    https://claude.com/customers/stripe
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture

Date evidence

  • First archived Mar 10, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source