NVIDIA Software / SaaS United States

Arcee AI

Arcee AI needed to build an open reasoning model for long-running agents that could rival closed frontier systems, but doing so required frontier-scale training, reinforcement-learning post-training, and low-cost inference for a roughly 400B-parameter sparse MoE architecture.

$0.90 per 1M output tokens
2,048 NVIDIA Blackwell Ultra GPUs
3.37 trillion tokens served in the first two months
55.2 billion tokens generated on Kilo Code

Reported impact

Business outcome

Arcee cut inference pricing to about $0.90 per million output tokens, roughly 20x below leading closed reasoning models, served 3.37 trillion tokens in two months on OpenRouter, and established Trinity-Large-Thinking as a competitive open model for long-horizon agentic workloads.

  • Cost Reduction
  • Revenue Growth
  • Scalability
  • Speed to Market

Solution

Arcee trained and served the Trinity model family on a frontier NVIDIA stack built for large open-weight models. Trinity Large was trained on 2,048 NVIDIA Blackwell Ultra GPUs, using HGX B300 systems with NVLink and NVLink Switch fabric plus NVIDIA Quantum InfiniBand to keep expert-parallel MoE training efficient across thousands of GPUs. For data and post-training, Arcee used NVIDIA NeMo Data Designer for pretraining preparation and NVIDIA NeMo RL for reinforcement-learning stages, then combined NVIDIA Dynamo with vLLM, CUDA optimizations, fused MoE kernels, speculative decoding, and KV-cache-aware routing for production inference. This created a repeatable pipeline that spans pretraining, RL, and API serving for Trinity-Large-Thinking, while keeping token costs low enough for long-horizon agents and tool-using workflows where reasoning depth directly affects total cost.

Data flow

Training data is prepared with NeMo Data Designer, large-scale MoE pretraining runs on Blackwell Ultra HGX clusters over InfiniBand, NeMo RL post-trains Trinity models for agentic reasoning, and Dynamo plus vLLM serve the resulting models through Arcee's API and partner distribution channels.

Solution architecture

8 components · 3 layers
  1. Compute
    • NVIDIA Blackwell Ultra GPUs Provide the GPU scale used to train frontier open-weight MoE models.
    • NVIDIA HGX B300 Supplies the memory bandwidth and NVLink-based scale-up fabric behind Arcee's training cluster.
    • NVIDIA Quantum InfiniBand Connects the Trinity training cluster so MoE communication overhead stays low at scale.
  2. Serving
    • Trinity-Large-Thinking Serves as Arcee's open reasoning model for long-running agent and tool-use workloads.
    • NVIDIA Dynamo Manages the production vLLM serving stack for API inference.
    • vLLM Runs optimized production inference for Trinity-family models.
  3. Orchestration
    • NVIDIA NeMo Data Designer Prepares pretraining data for Arcee's large-model training pipeline.
    • NVIDIA NeMo RL Supports reinforcement-learning post-training for Trinity variants.

Architecture clues

  • Arcee is building a repeatable AI-factory-style pipeline rather than a one-off training run.
  • Production inference uses custom CUDA optimizations, fused MoE kernels, speculative decoding, and KV-cache-aware routing.
  • The model architecture is a sparse MoE system with roughly 400B parameters and about 13B active per token.

Evidence from the source

Arcee combined NVIDIA Blackwell Ultra with NVIDIA Dynamo and vLLM for optimized inference.
Arcee trained Trinity Large on 2,048 NVIDIA Blackwell Ultra GPUs, then post-trained Trinity-Large-Thinking with extended chain-of-thought and agentic reinforcement learning (RL) using NVIDIA NeMo open libraries.
Inference via Arcee's API costs around $0.90 per 1M output tokens, around 20x cheaper than leading closed reasoning models.
NVIDIA Quantum InfiniBand networking was used across the Trinity cluster to keep MoE communication overhead low and maintain training efficiency.
The training pipeline incorporated NVIDIA NeMo™ Data Designer for pretraining data preparation and NVIDIA NeMo RL for RL post-training.
Transparency Evidence & methodology 90/100 reference value · 79% 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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • 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

    Arcee AI customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/arcee-ai/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jul 15, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 2, 2026 · NVIDIA · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.