LangChain Software / SaaS United States

Factory

Application Refactoring · IT Operations Automation

Factory needed secure observability and a faster feedback loop for autonomous SDLC agents running inside enterprise environments with strict privacy controls, custom LLM tooling, and limited tolerance for opaque debugging workflows.

2x their iteration speed
a 3x reduction in code churn on code impacted by Droids in the first 90 days
a ~20% reduction in open-to-merge time
over 550,000 hours of development time saved

Reported impact

Business outcome

Factory doubled iteration speed for prompt and agent improvement, reduced open-to-merge time and code churn for customers, and established a secure, enterprise-friendly observability stack for autonomous engineering workflows.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Factory runs AI Droids that automate stages of the software development lifecycle and uses self-hosted LangSmith as the observability backbone inside tightly controlled customer environments. LangSmith traces are exported into AWS CloudWatch so engineers can correlate agent events with infrastructure logs and follow data through each step of a multi-stage LLM pipeline without building a proprietary logging stack. Feedback is attached directly to individual LLM calls through the Feedback API, then exported into datasets for analysis. Factory’s engineers use custom LangChain tooling to compare good and bad code-review comments, hypothesize why prompts failed, re-prompt the model, and improve accuracy. This closed-loop design lets the team keep enterprise data private while continuously tuning Code Droid and related Droids from production evidence rather than ad hoc manual review.

Data flow

Droids execute SDLC tasks, Self-hosted LangSmith records each LLM step and exports traces to AWS CloudWatch, engineers attach workflow feedback through the Feedback API, and custom LangChain tooling turns those labeled examples into prompt updates and new runs that can be evaluated again.

Solution architecture

5 components · 4 layers
  1. Storage
    • AWS CloudWatch Stores exported traces alongside other operational logs for end-to-end debugging.
  2. Serving
    • Code Droid Automates complex software-development tasks and generates outputs that engineers review.
  3. Orchestration
    • LangChain tooling Analyzes feedback patterns and helps engineers re-prompt models to improve performance.
  4. Governance
    • Self-hosted LangSmith Provides the observability and experiment infrastructure inside locked-down customer environments.
    • Feedback API Records positive and negative feedback at different workflow stages for downstream analysis.

Architecture clues

  • Factory links LangSmith events and CloudWatch logs to keep a single source of truth for pipeline state.
  • Feedback is appended at multiple stages and exported to datasets for pattern analysis.
  • LangSmith is deployed inside customer environments where tight data controls would block most observability products.

Evidence from the source

Factory integrated LangSmith to export traces to AWS CloudWatch logs
Factory was able to 2x their iteration speed.
With feedback available next to every LLM call
a 3x reduction in code churn on code impacted by Droids in the first 90 days
a ~20% reduction in open-to-merge time
Transparency Evidence & methodology 100/100 reference value · 94% confidence · 2 sources

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 confidence94%
  • 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 evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references 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. LangChain

    Factory customer story

    First-party
    https://blog.langchain.dev/customers-factory
    Source type
    Vendor-published customer story
    Published
    Jun 19, 2024
    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
  2. aVenture

    Factory - aVenture Company Research

    Independent secondary
    https://aventure.vc/companies/factory-san-francisco-ca-us

    The company profile states 'Operating headquarters' in 'San Francisco, CA, US' and 'Factory has 29 employees as of Feb 4, 2024'.

    Source type
    Structured company profile
    Supports
    • Company size
    • Region

Date evidence

  • Published on source page Jun 19, 2024 · LangChain · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.