Turning computing heat into a practical heating solution for greenhouses.
Updated
January 23, 2026 10:41 AM
Inside of a workstation computer with red lighting. PHOTO: UNSPLASH
Most computing systems have one unavoidable side effect: they get hot. That heat is usually treated as a problem and pushed away using cooling systems. Canaan Inc., a technology company that builds high-performance computing machines, is now showing how that same heat can be reused instead of wasted.
In a pilot project in Manitoba, Canada, Canaan is working with greenhouse operator Bitforest Investment to recover heat generated by its computing systems. Rather than focusing only on computing output, the project looks at a more basic question—what happens to all the heat these machines produce and can it serve a practical purpose?
The idea is simple. Canaan’s computers run continuously and naturally generate heat. Instead of releasing that heat into the environment, the system captures it and uses it to warm water. That warm water is then fed into the greenhouse’s existing heating system. As a result, the greenhouse needs less additional energy to maintain the temperatures required for plant growth.
This is enabled through liquid cooling. Instead of using air to cool the machines, a liquid circulates through the system and absorbs heat more efficiently. Because liquid retains heat better than air, the recovered water reaches temperatures that are suitable for industrial use. In effect, the computing system supports greenhouse heating while continuing to perform its primary computing function.
What makes this approach workable is that it integrates with existing infrastructure. The recovered heat does not replace the greenhouse’s boilers but supplements them. By preheating the water that enters the boiler system, the overall energy demand is reduced. Based on current assumptions, Canaan estimates that a significant portion of the electricity used by the servers can be recovered as usable heat, though actual results will be confirmed once the system is fully operational.
This matters because heating is one of the largest energy expenses for commercial greenhouses, particularly in colder regions like Canada. Many facilities still rely heavily on fossil-fuel-based heating and policies such as carbon pricing are encouraging lower-emission alternatives. Reusing computing heat offers a way to improve efficiency without requiring a complete overhaul of existing systems.
The project is planned to run for an initial two-year period, allowing Canaan to evaluate real-world performance factors such as reliability, system stability and maintenance needs. These findings will help determine whether the model can be replicated in other agricultural or industrial settings.
More broadly, the initiative reflects a shift in how computing infrastructure can be designed. Instead of operating as energy-intensive systems isolated from everyday use, computing equipment can contribute to real-world applications. Canaan’s greenhouse pilot highlights how excess heat—often seen as a by-product—can become part of a more efficient and thoughtful energy loop.
In doing so, the project suggests that improving sustainability in technology is not only about reducing energy consumption, but also about finding smarter ways to reuse the energy already being generated.
Keep Reading
Backed by Menlo Ventures, BrainGrid tackles planning gaps as AI makes software building accessible to more founders.
Updated
April 1, 2026 8:37 AM
A phone screen with app icons. PHOTO: UNPSLASH
As artificial intelligence makes it easier to write code, a different problem is starting to surface. Building software is no longer limited by technical skill alone. Increasingly, the challenge lies in deciding what to build, how to structure it, and how to turn an idea into something that actually works.
That shift sits at the centre of BrainGrid, a startup that has raised $1 million in pre-seed funding led by Menlo Ventures, with participation from Next Tier Ventures and Brainstorm Ventures. The company is building what it describes as an AI-powered planning layer for people who want to create software but may not have a technical background.
The timing reflects a broader change in how products are being built. Tools like Claude Code and Cursor have made it possible to generate working code through simple prompts. For many first-time founders, this has lowered the barrier to entry. But writing code is only one part of the process. Turning that code into a reliable product requires structure, sequencing and clarity—areas where many projects begin to fall apart.
In traditional teams, this responsibility sits with product managers who define what needs to be built and in what order. Without that layer, even well-written code can lead to products that feel disjointed or incomplete. Features may not work together, integrations can break and the final product often does not match the original idea.
BrainGrid is designed to address that gap. Instead of focusing on generating code, it helps users map out the structure of a product before development begins. The aim is to give builders a clearer starting point so that the tools they use—whether human or AI—can produce more consistent results.
The company says more than 500 builders have already used it to create software products across areas like fitness, healthcare and productivity. These range from first-time founders experimenting with new ideas to experienced developers working independently. In many cases, the products are already live and generating revenue, suggesting that the demand is not just for experimentation but for building something that can scale.
For investors, the appeal lies in the evolving role of software development. As AI takes on more of the technical work, the value shifts toward defining the problem and structuring the solution. In that sense, planning becomes less of a background task and more of a core capability.
The US$1 million raise is relatively modest, but it points to a larger trend. As more people gain access to AI tools, the number of potential builders expands. What remains limited is the ability to organise ideas into products that work in the real world. If that shift continues, the next wave of software may not be defined by who can code, but by who can plan.