Arcee AI has announced a multi-million-dollar strategic partnership with Hugging Face, making the Hub the exclusive home for everything the San Francisco lab builds. That means every open model release, every private training run, every proprietary dataset, and every agent trace now lives on the Hub. It is a rare, all-in commitment from an independent AI lab, and the reasoning behind it says as much about the economics of running a lean AI operation in 2026 as it does about Hugging Face's growing infrastructure ambitions.

A 30-person lab with a big footprint

Arcee is not a large organization. With 14 people on research and 30 across the whole company, the infrastructure holding everything together has to be invisible. Despite that size, the arcee-ai organization is already one of the most active American labs on the platform, with 200+ models and millions of downloads. Their flagship product line is the Trinity family, which spans a range of model sizes built for enterprise and edge deployment alike.

Trinity-Large-Thinking is a 398-billion-parameter sparse Mixture-of-Experts model with approximately 13 billion active parameters per token, post-trained with extended chain-of-thought reasoning and agentic reinforcement learning. Sparse MoE (Mixture-of-Experts) is an architecture where only a small subset of the model's total parameters are activated for any given input, making inference far cheaper than a dense model of equivalent size. On the smaller end, Trinity Nano is a 6B MoE model with just 1B active parameters, designed for enterprise and tinkerers alike.

The infrastructure problem no one talks about

The real story here is not just distribution. It is about what happens between the first line of training code and the final model card. Hugging Face Storage Buckets are the first new repository type on the Hub in four years, designed as mutable, non-versioned object storage for the artifacts ML workflows generate constantly but Git was never built to handle: training checkpoints, optimizer states, processed dataset shards, agent traces, logs, and intermediate pipeline outputs.