NVIDIA Agriculture United States

Aigen

Aigen needed to train field-robot perception and control systems for highly variable agricultural environments, but collecting and labeling enough real-world crop and weed data was too slow, seasonal, and expensive to scale autonomous chemical-free weeding.

99% synthetic data and 1% real-world data
Compute utilization reduced from roughly 100% to about 30%
Normally takes three to four years ... model turnaround is hours instead of seasons
One million hours of action-video data in months

Reported impact

Business outcome

Aigen trained production weed-control models with 99 percent synthetic data, reduced onboard compute utilization to about 30 percent, shrank onboard hardware from five compute devices to three Jetson modules, and compressed model turnaround from seasons to hours so new crops can be deployed in the same season.

  • Cost Reduction
  • Scalability
  • Speed to Market

Solution

Aigen built Alchemy as an outdoor world model on NVIDIA Cosmos to replace slow field-data collection with synthetic training generation for agricultural robotics. The company post-trained NVIDIA Cosmos 3, and earlier Cosmos Transfer 2.5, on fleet-captured RGB and depth clips so the model could generate realistic variations in crops, weeds, soil, lighting, and depth for perception training. That synthetic-data pipeline lets Aigen train field-weeding models with only 1 percent real-world data while expanding coverage to scenarios the team has not physically collected. On the robots themselves, Aigen uses three NVIDIA Jetson Orin NX modules for perception, navigation, and mechanical control, reducing onboard compute utilization from roughly 100 percent to about 30 percent and staying within a solar-power budget. This pairing of synthetic-data generation and efficient edge AI gives Aigen a path to scale autonomous, herbicide-free weed control across more crops and field conditions.

Data flow

Fleet-captured RGB and depth clips seed Alchemy and Cosmos training, the world model generates labeled synthetic crop and weed scenarios, perception models are trained from that data, and Jetson Orin NX modules run the resulting perception and control stack onboard Aigen's solar-powered field robots.

Solution architecture

4 components · 1 layer
  1. Compute
    • Alchemy Generates the outdoor synthetic training data Aigen uses to expand crop and weed perception coverage.
    • NVIDIA Cosmos 3 Provides the base world model Aigen post-trains for agricultural environment generation.
    • Cosmos Transfer 2.5 Supports earlier post-training and action-conditioned data generation for synthetic agricultural scenarios.
    • NVIDIA Jetson Orin NX Runs perception, navigation, and mechanical control directly on the solar-powered robots.

Architecture clues

  • Alchemy uses post-trained world models rather than manual annotation to create labeled agricultural data.
  • The robots keep full perception, navigation, and control on-device to stay inside a solar-power budget.
  • The same edge-compute platform is intended to support capabilities beyond weeding as the fleet expands.

Evidence from the source

"Normally that takes three to four years of collecting data, labeling it, and training models ... model turnaround is hours instead of seasons."
Aigen built Alchemy, an outdoor world model that generates realistic synthetic variations in crops, weeds, soil, lighting, and depth.
Aigen's newest robots use three NVIDIA Jetson Orin NX modules for energy-efficient perception, navigation, and mechanical control.
During development testing, Aigen reports that the Jetson-based architecture operated at approximately 30% compute utilization.
Using synthetic training data from Alchemy, Aigen achieved autonomous field weeding with a perception model trained on 1% real-world data and 99% synthetic data.
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
    2 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
    5 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. NVIDIA

    Aigen customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/aigen/
    Source type
    Vendor-published customer story
    Published
    Sep 4, 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 4, 2026 · NVIDIA · 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.