OpenAI Software / SaaS North America

1Password

Application Refactoring · IT Operations Automation · Security and Compliance

1Password needed to compress the time between planning and production, reduce investigation and review overhead, and expand builder capacity without weakening the company's zero-knowledge security posture.

$0.8M estimated annual engineering capacity value from Codex
11% reduction in median pull request cycle time
20.9% productivity improvement
553% estimated ROI from Codex

Reported impact

Business outcome

1Password measured a 20.9% productivity improvement, a 10.9% reduction in median PR cycle time, roughly 90% faster investigation of a multi-service production issue, and a modeled 553% ROI from engineering capacity gains.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

1Password embedded Codex across planning, implementation, review, testing, release readiness, and incident investigation so engineering work can move from user story to production with fewer handoffs. Codex turns requests into specs, dependency checks, and work items; helps engineers navigate Rust and TypeScript code through the CLI; reviews pull requests before humans; runs acceptance criteria and tests in parallel; and investigates live defects by pulling evidence from telemetry, source control, paging, feature flags, and incident systems. The company also wrapped Codex inside its internal AppSec harness and secret-reference model so credentials are resolved only at execution time and never exposed in model context. That combination let 1Password speed up feature delivery, ship internal tools such as Knox and an AI SRE agent, and extend builder workflows into finance and marketing without trading away core security controls.

Data flow

User stories and requests enter Codex, which breaks them into specs, code changes, tests, and review steps. During execution, Codex can query telemetry, paging, feature flags, and source control to investigate problems, while the AppSec harness and secret-reference workflow inject credentials only at the point of action so secure outputs flow back into engineering review.

Solution architecture

4 components · 3 layers
  1. Serving
    • Knox Acts as 1Password's fully agentic frontend design system for building new interfaces.
    • AI site reliability engineering (SRE) agent Supports operational investigation and remediation for production issues.
  2. Orchestration
    • Codex Drives planning, coding, review, testing, and production investigation across the software delivery lifecycle.
  3. Governance
    • AppSec harness Applies 1Password's reusable security skills and policy controls around AI-assisted development.

Architecture clues

  • Codex works across planning, implementation, review, testing, and production investigation
  • Parallel worktrees and CLI workflows help engineers operate across unfamiliar stacks
  • Reusable AppSec skills embed security standards in the development workflow
  • Secret references keep plaintext credentials out of model context

Evidence from the source

"1Password implements that principle by keeping secret references, rather than credentials, in repositories."
"For a defect spanning more than 10 microservices, investigation time fell from about two hours to 5-20 minutes."
"That's been a game changer."
"With Codex, you can actually one-shot, going from an idea to a prototype to a feature that works fully in production."
Transparency Evidence & methodology 100/100 reference value · 89% 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
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/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. OpenAI

    1Password customer story

    First-party
    https://openai.com/index/1password/
    Source type
    Vendor-published customer story
    Published
    Sep 8, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Sep 8, 2026 · OpenAI · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.