The deployments behind the dataset.
In continuous field deployment since 2014. Over 150,000 operational hours. Three continents. More than 50 systems. The numbers come from the deployments below — each a different feedstock class, climate, and operating model, each one feeding the energy-balance dataset that sizes the next system.
Selected projects, de-identified except where partners and publications are public. Commercial deployments under non-disclosure aren't shown here, but can be referenced in scoping when relevant.
Five figures resolve every "we've done this in the field" claim that the other pages make. The architecture and math behind them live on the data platform and sizing pages, linked below.
Organized by class. Each represents a feedstock the platform has actually processed at field scale, with the system configuration, outcome, and — where applicable — the peer-reviewed reference or named partner that documents it. Project locations are de-identified where the operator has not authorized public disclosure.
The deployments above didn't happen in arbitrary order. The platform's design and the operating envelope it now covers are products of an explicit ten-year arc, starting from a public-health origin that shaped both the engineering posture and the resilience requirements every system inherits.
Publications that document the deployments above, the engineering approach, and the carbon and sustainability evidence that carbon-removal frameworks depend on. Each is publicly accessible. Authors are listed with Biomass Controls authorship in bold.
Commercial deployments under non-disclosure aren't named publicly. The reasons vary — competitive sensitivity for the operator, ongoing regulatory or permitting processes, contractual confidentiality, or the operator's own communication strategy. In a scoping conversation we can speak to relevant deployments in abstract terms — the feedstock class, the climate, the operating scale, the carbon-record posture — without identifying the operator.
The deployments shown in § 02 were selected because the operator authorized public reference, or because the work is documented in a peer-reviewed publication, or both. The full operational record is larger.
Six questions that come up the most about the field record itself.
Send us a feedstock summary and the conditions your project has to meet. If you are scoping a project — a feedstock you want assessed, a site you want sized, a carbon-removal pathway you want documented, or a regulator who wants to see the evidence chain — we will return a scoping response that names the closest field reference and the next step.