What Orchard actually decouples
Microsoft Research released Orchard on 4 August 2026 as an open-source agentic-modeling framework, describing it in a blog post as a way to separate sandbox lifecycle management from the training pipeline used to build AI agents. The distinction matters because training an agent to code, browse, or use tools well requires running it repeatedly inside something that behaves like its real deployment environment, not a simplified stand-in.
Before Orchard, a team that wanted to train an agent this way typically had to build that sandbox and evaluation layer itself, project by project, or pay a managed provider to do it. Microsoft Research's core sandbox service is designed to be reused across projects instead, which is the part of the release aimed squarely at teams currently duplicating that infrastructure work in-house.
The sandbox bill drops by roughly a factor of ten
Microsoft Research reported that Orchard's core sandbox service runs at roughly a tenth of the cost of managed alternatives such as E2B or Daytona when deployed on spot instances. Sandbox infrastructure, not model training compute, has quietly become one of the larger line items for teams building agents that act in real environments, since every training run and every evaluation pass needs its own isolated, disposable copy of that environment.
A tenfold reduction on that specific cost does not make agent development free, but it does change which projects clear the bar for a team's engineering budget. Work that previously did not justify building or renting dedicated sandbox infrastructure now plausibly does, particularly for narrower, task-specific agents rather than general-purpose ones.
A 3 billion parameter model reaching results usually tied to ten times more
The accompanying technical paper, 'Orchard: An Open-Source Agentic Modeling Framework,' reports that a model trained with it, called Orchard-SWE, reaches 69.7 percent on SWE-bench Verified, and 73 percent with reranking applied, using only around 3 billion active parameters. Those scores are usually associated with models roughly ten times larger, according to the paper, and the claim has been repeated independently by AIBusiness and EdTechInnovationHub.
The parameter count is the operationally interesting number here, more than the benchmark score itself. SWE-bench Verified measures whether a model can resolve real software issues end to end, and a 3 billion active parameter model reaching a score normally reserved for far larger systems suggests that training method and sandbox realism, not raw scale, produced the result.
The real decision facing EU and UK buyers
Every company currently paying per-task API fees to a frontier vendor such as OpenAI or Anthropic for agentic work, or paying for managed sandbox infrastructure from a provider like E2B or Daytona to build an agent in-house, now has a credible, free, self-hostable path to train a narrower, cheaper, purpose-built agent instead. That is a genuine change in the available options, not a marginal one.
It is not, however, a change from paying to not paying. Open source here shifts the cost from a metered line item on a vendor invoice to an engineering and operations burden inside the company, and to whatever cloud the training actually runs on, frequently Microsoft's own Azure, since Microsoft built the framework. The decision a buyer actually faces is a genuine build-versus-rent-versus-relock comparison of total cost and capability, not a reflexive move toward whatever is labelled free.
Why 3 billion active parameters changes the calculus
The operational lesson of the benchmark result is not that Microsoft has the best coding agent available today. It is that a narrow, well-trained agent can match a much larger general-purpose model on a specific task, at a fraction of the active parameters and, per Microsoft Research's cost claim, at a fraction of the sandbox spend needed to train it. That changes the calculus for any team currently defaulting to the largest available frontier model purely out of caution.
Teams that have never trained their own agent because the sandbox and evaluation infrastructure looked too costly to build now have a lower-cost way to test whether a narrower model would do their specific job at a fraction of the ongoing per-task fee. Whether that trade clears depends on engineering time available in-house, not on which option is labelled open source.
Read next: Opus 5 Costs Half of Fable 5, If You Set It Right | The Agent Was Never the Hard Part



